Skip to main content
This page gets you to a working REST call in five minutes. We’ll list a project’s content with the admin API, using a JWT bearer token.

​
What you’ll need

  • A Metabind organization and project. Don’t have one? See Create an account.
  • A JWT for the admin API, or an API key for the client API.
  • curl, or any HTTP client.

​
1. Pick the right base URL and route prefix

The REST API lives at:
Two route prefixes: Most read-only client integrations use the client API. Workflow tooling, automation, and editor backends use the admin API. This quickstart uses the admin API.

​
2. Get a JWT

  1. Sign in to App Studio.
  2. Open your browser’s developer tools and select a request to api.metabind.ai.
  3. Copy the token from the request’s Authorization: Bearer ... header.
This is a short-lived token tied to your login. Don’t use it for automation.

​
3. Make your first call

List published content in a project:
Replace {org} and {project} with your IDs (shown as Organization ID and Project ID in the project’s Settings → General page). A successful response:

​
4. Try a few common patterns

Get a single entry by ID:
Search by content type:
Create a content entry (draft):
The response includes the new entry’s id and a draft status. Publish via POST .../content/{contentId}/publish.

​
5. Pagination

The content list returns up to 20 items per page by default. Use pagination.lastKey to fetch the next page:
When lastKey is absent in the response, you’ve reached the end.

​
6. Error responses

Errors come back as JSON with an HTTP status code:
Common codes: For the full error reference, see Errors.

​
7. Rate limits

Default limits, per project and caller:
  • 300 write requests per minute: every request other than a read, including POST searches, except publish and tool execution
  • 20 publish requests per 5 minutes, including package creation
Above the limit, you’ll see 429 Too Many Requests with a Retry-After header. Back off and retry. For higher limits, see Rate limiting.

Authentication

JWTs, API keys, scopes, rotation.

Core concepts

Resource model and data shapes.

Content

The most common resource — read, create, update content.

Errors

Status codes and recovery patterns.