The Metabind REST API provides programmatic access to everything App Studio exposes — components and packages, content types and entries, assets, organizations and projects, roles and tokens. Use it to integrate Metabind into your workflows, automate content operations, or build custom tooling around the platform. If you’re new, start with the REST API quickstart — it gets you to your first call in five minutes.Documentation Index
Fetch the complete documentation index at: https://docs.metabind.ai/llms.txt
Use this file to discover all available pages before exploring further.
API capabilities
- Component management for view and layout components
- Package versioning and dependency management
- Content type definition with template support
- Content creation and management
- Asset management with CDN integration for both content and components
- Role-based access control and user management
- Multi-platform content delivery
Base URL
All API requests use this base URL:| Route Prefix | Authentication | Use Case |
|---|---|---|
/api/v1/... | x-api-key header | Client API (read-only, published content) |
/app/v1/... | Authorization: Bearer JWT | Admin API (full CRUD operations) |
Authentication
API requests require authentication. The method depends on the route: Client API (/api/v1/...) - for consuming published content:
/app/v1/...) - for content management:
Making requests
Example request
Example response
Where to go next
REST API quickstart
Five-minute path to your first authenticated call.
Authentication
JWTs, API keys, scopes, and rotation.
Errors
Status codes and recovery patterns.
Core concepts
The resource model — components, packages, content.