Skip to main content

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:
Example paths:
ResourcePath
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/).
VersionStatusDescription
v1CurrentInitial 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):
ParameterTypeDefaultDescription
limitnumber10Items per page (max: 100)
lastKeystring-Cursor from previous response for next page

Offset-Based Pagination

Used by organizational endpoints (tags, api-keys):
ParameterTypeDefaultDescription
pagenumber1Page number (1-indexed)
limitnumber20Items per page (max: 100)

Request Headers

Required Headers

Admin API (/app/v1/...):
Client API (/api/v1/...):

Optional Headers

HeaderDescription
Accept-LanguagePreferred response language
X-Request-IDCustom request identifier for tracing

Configuring Your Application

Environment Variables

JavaScript Example

Health Check

Response: