Base URL
All REST API requests are made to:Authentication
Royaltyport supports two authentication methods:- OAuth 2.1 (recommended) — MCP clients, the CLI, and third-party apps authenticate via a browser-based consent flow. No tokens to manage.
- API tokens — static credentials for server-side integrations, CI/CD pipelines, and headless environments.
Response Format
All successful responses return a JSON object with adata key:
error key:
Rate Limiting
API requests are rate-limited per token. Every response includes rate limit headers:| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum requests allowed per window |
X-RateLimit-Remaining | Requests remaining in the current window |
X-RateLimit-Reset | Unix timestamp when the window resets |
429 status with an error message.
HTTP Status Codes
| Code | Meaning |
|---|---|
200 | Success |
400 | Bad request — invalid or missing parameters |
401 | Unauthorized — missing, invalid, or expired token |
403 | Forbidden — token does not have access to the requested project |
404 | Not found — the requested resource does not exist |
429 | Rate limit exceeded |
500 | Internal server error |
Available Resources
Authentication
OAuth 2.1, API tokens, and token management.
REST API
Projects, contracts, entities, artists, writers, and sandboxes.
MCP Server
Model Context Protocol integration for AI agents.
CLI
Command-line interface for authentication, project browsing, and sandbox access.