Read a resource offer as its recipient or sender

GET/v1/resource-invitations/{invitationId}

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
invitationIdpathstringYes
Query parameters
None.
Header parameters
NameLocationTypeRequiredDescription
X-Computer-Agents-OrganizationheaderstringYesOrganization that issued this recipient-bound offer

Body schema

This endpoint does not require a request body.

None.

What the API returns

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

200Invitationapplication/json
FieldTypeRequiredDescription
invitationobjectYes
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.
400Missing invitation organization
None.
401Authentication required
None.
403Account is not authorized for this offer
None.
404Offer unavailable to this account
None.
503PostgreSQL invitation service unavailable
None.
Read a resource offer as its recipient or sender
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow