TEASEDocs
API ReferenceVault

Per-content PPV send analytics

For one vault media, aggregates your PPV sends joined to purchase status: sent, opened, purchased, revenue, and the deduped list of buyers. Renders zeros honestly when there are no sends. Requires a read-scoped key.

Authorization

bearerAuth
AuthorizationBearer <token>

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

In: header

Path Parameters

media_id*string

Vault media id.

Response Body

application/json

application/json

application/json

GET
/api/admin/content/{media_id}/sends
curl -X GET "https://example.com/api/admin/content/string/sends"
{  "media_id": "501",  "sent": 120,  "opened": 88,  "purchased": 31,  "revenue_cents": 77500,  "buyers": [    {      "fan_id": "287413092",      "username": "john_d"    }  ]}
{  "detail": "Not authenticated"}
{  "detail": {    "code": "engine_not_connected",    "message": "Connect your engine to access this data."  }}

Suggested PPV price

Returns a suggested PPV price and a verdict (raise/lower/ok/insufficient_data); insufficient_data when there is too little sales history. All money in integer cents. Requires a read-scoped key.

Add a manual tag

Adds a normalized manual tag to a vault media item. Namespaced facets (cat:* / mood:* / len:* / kink:*) and plain tags are allowed. Idempotent: re-adding an existing tag is a no-op. Requires a write-scoped key.