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.