TEASEDocs
API ReferenceVault

Respond to a content request

Records the model's action on a request: start, fulfill (with media), or decline (with a reason). Returns 404 on a missing request or invalid transition. Requires a write-scoped key.

Authorization

bearerAuth
AuthorizationBearer <token>

Your al_live_<prefix>_<secret> API key. Mint and manage keys in the dashboard.

In: header

Path Parameters

request_id*integer

Request id.

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

POST
/api/admin/requests/{request_id}/respond
curl -X POST "https://example.com/api/admin/requests/0/respond" \  -H "Content-Type: application/json" \  -d '{    "action": "fulfill",    "media_ids": [      "501",      "502"    ],    "reason": ""  }'
{  "id": 5012,  "status": "fulfilled",  "media_ids": [    "501",    "502"  ]}
{  "detail": "Not authenticated"}
{  "detail": "request not found or invalid transition"}

Create a content request

Creates a proof or custom content request (chatter to model). Returns the new request id and its initial status. Requires a write-scoped key.

Mark a request delivered

Marks a fulfilled request as delivered after its proof was sent to the fan. Returns 409 if the request is not in the fulfilled state. Requires a write-scoped key.