Update saved prompt metadata or access

PATCH/v1/prompts/{promptId}

An owner change in metadata creates a pending resource invitation and must be submitted separately from other edits. Ownership remains unchanged until recipient acceptance.

How to call this endpoint

Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.

Path, query, and header parameters

These parameters control which ACP object the endpoint acts on and how the request is processed.

Path parameters
NameLocationTypeRequiredDescription
promptIdpathstringYes—
Query parameters
None.

Body schema

Content type: application/json · Required

FieldTypeRequiredDescription
namestringNoHuman-readable name.
descriptionstringNoHuman-readable description.
metadataobjectNoFree-form metadata object.
permissionSetobjectNo—

What the API returns

Each response code below includes the documented payload shape for the ACP API.

200Prompt updated or ownership offeredapplication/json
FieldTypeRequiredDescription
promptobjectNo—
invitationobjectNo—
invitation.idstringYesUnique identifier.
invitation.organizationIdstringYes—
invitation.kindshare | ownershipYes—
invitation.resourceTypestringYes—
invitation.resourceIdstringYes—
invitation.resourceNamestringYes—
invitation.recipientUserIdstringYes—
invitation.invitedByUserIdstringYes—
invitation.accessLeveluse | edit | manageYes—
invitation.statuspending | accepted | declined | revoked | expiredYesCurrent lifecycle status.
invitation.expiresAtstringYes—
invitation.decidedAtstringYes—
invitation.createdAtstringYesISO 8601 timestamp.
invitation.updatedAtstringYesISO 8601 timestamp.
400Invalid recipient or combined ownership and configuration edits
None.
403Current owner authorization required
None.
409Another ownership offer is pending
None.
503Resource invitations require PostgreSQL
None.
Update saved prompt metadata or access
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow