Base URLs
- Admin API (REST):
https://api.metabind.ai/app/v1 - Client API (REST):
https://api.metabind.ai/api/v1 - GraphQL API:
https://api.metabind.ai/graphql - CDN:
https://cdn.metabind.ai
URL Structure
REST API Path Pattern
All REST API endpoints follow this pattern:| Resource | Path |
|---|---|
| List components | /app/v1/organizations/org123/projects/proj456/components |
| Get content | /app/v1/organizations/org123/projects/proj456/content/cont789 |
| Upload asset | /app/v1/organizations/org123/projects/proj456/assets |
| Create package | /app/v1/organizations/org123/projects/proj456/packages |
CDN Asset URLs
Assets are served from the CDN with this pattern:API Versioning
The API uses semantic versioning in the URL path (e.g.,/app/v1/).
| Version | Status | Description |
|---|---|---|
v1 | Current | Initial release with core functionality |
Versioning Policy
- Breaking changes are introduced in new major versions (
v2,v3, etc.) - Backward-compatible changes may be added to existing versions
- Deprecated features will be announced with a migration timeline
- Old versions will be supported for at least 12 months after a new major version
Response Format
All successful responses follow a consistent format:Paginated Responses
List endpoints use one of two pagination styles:Cursor-Based Pagination
Used by content-heavy endpoints (content, components, assets, packages):| Parameter | Type | Default | Description |
|---|---|---|---|
limit | number | 10 | Items per page (max: 100) |
lastKey | string | - | Cursor from previous response for next page |
Offset-Based Pagination
Used by organizational endpoints (tags, api-keys):| Parameter | Type | Default | Description |
|---|---|---|---|
page | number | 1 | Page number (1-indexed) |
limit | number | 20 | Items per page (max: 100) |
Request Headers
Required Headers
Admin API (/app/v1/...):
/api/v1/...):
Optional Headers
| Header | Description |
|---|---|
Accept-Language | Preferred response language |
X-Request-ID | Custom request identifier for tracing |