Yapper Developer API
Team-scoped API for Yapper generation, assets, credits, and MCP clients.
The Yapper Public API lets you drive Yapper's media generation from your own code. API keys are scoped to a team and spend that team's workspace credits — the same balance the team uses inside the Yapper app.
Status: live.
What's live today
| Endpoint | Purpose |
|---|---|
POST /api/v1/processes | Start a media generation process |
GET /api/v1/processes | List team processes |
GET /api/v1/processes/{processId} | Poll a process |
GET /api/v1/assets | List normalized team assets |
GET /api/v1/assets/{assetId} | Fetch one asset |
POST /api/v1/assets/import | Import an external image or video URL |
GET /api/v1/models | List public-safe model metadata |
GET /api/v1/credits | Read shared team credits |
GET /api/v1/usage | Read team and acting-member usage state |
MCP
| Hosted connector | https://yapper.so/mcp/connector |
Base URL and auth
GET https://yapper.so/api/v1/credits
Authorization: Bearer yap_live_...Create keys at Account → Developer. The full secret is shown once at creation time.
Machine-readable docs
- OpenAPI 3.1:
/api/v1/openapi.json - AI index:
/api/v1/llms.txt - Full AI context:
/api/v1/llms-full.txt
Error shape
Every error uses the same envelope:
{
"error": {
"code": "insufficient_credits",
"message": "This team does not have enough credits to start the process.",
"requestId": "req_..."
}
}