AMDBS.

The Basics

Build with AMDBS

Use Aurora identities to connect your application to the catalog.

One catalog, a shared identity

The AMDBS API provides normalized media records with Aurora-owned identifiers. Store the Aurora ID when linking an application to a movie, show, or person. Provider identifiers are external references.

Search, then retrieve a record

The current version prefix is /api/v1. Search returns grouped summaries. Retrieve an entity’s detail endpoint using its Aurora ID.

  • GET /api/v1/search?q=matrix
  • GET /api/v1/movies/{aurora_id}
  • GET /api/v1/series/{aurora_id}
  • GET /api/v1/people/{aurora_id}

Keep the API location configurable

The production API is hosted at api.amdbs.net. Use a configurable base URL in your application so development and production can use different environments.

Access limits, metadata availability, and supported fields are controlled by the API. Administrative ingestion operations are separate from public discovery.

Developer documentation is growing

This page is an introduction to the existing API, not a complete contract. Public access terms, versioning commitments, and support arrangements have not been published here yet.