Getting Started

The Raster REST API gives you read and write access to your libraries through plain, resource-oriented HTTP endpoints — easy to call with curl, any HTTP client, or a no-code tool. It mirrors the GraphQL API over the same data and the same API keys.

The endpoint

All REST resources live under a single base URL:

https://api.raster.app/organizations

Requests must be made over HTTPS and must include both an API key and an Api-Version header. Plain HTTP, unauthenticated, and unversioned requests are rejected. See Authentication for the full header contract.

Required headers

Every REST request carries exactly two required headers:

Every response carries Vary: Api-Version so HTTP caches key bodies per version — your CDN or browser will never serve a body shaped for a different version of the API.

Response envelope

Every response is one of two shapes:

// Success
{ "data": <result> }

// Failure
{ "error": { "code": "ERROR_CODE", "message": "Human-readable message." } }

The shape is stable across endpoints, so a generic client can dispatch on "data" in response without parsing per-endpoint payloads. See Errors for the full code reference.

Quickstart

The fastest way to confirm your key works is to list the libraries your key can reach.

curl --request GET \
  --header 'Authorization: Bearer <API_KEY>' \
  --header 'Api-Version: 2026-05-20' \
  --url 'https://api.raster.app/organizations/monogram-labs/libraries'

curl --request GET \
  --header 'Authorization: Bearer <API_KEY>' \
  --header 'Api-Version: 2026-05-20' \
  --url 'https://api.raster.app/organizations/monogram-labs/libraries/barcelona/assets?page=1&pageSize=20'

Where to go next

• Authentication — API keys, the Api-Version header, and the access-level rules every request is checked against.
• Endpoints — every route, the parameters it takes, and a runnable curl example.
• Errors — the error envelope, every code, and the HTTP status each one maps to.
• Changelog — every notable change, by version.