Make your first request
Ask your Amber system administrator for an API key and your brand slug. SetAMBER_API_KEY and AMBER_BRAND in your server environment, then run:
id for brand relationships and document subjects; use slug
in request paths. Then read /brands/{brand}/products?limit=25. Collections
return items, nextCursor, and totalItems, with a Link header when there
is another page. The base URL is
https://app.amber.ai/api/public/v1. The OpenAPI specification
is the source for the API Reference tab and client generation.
The brand is the slug from your Amber URL, for example acme in /b/acme.
Use the key’s authorized brand. A successful first request returns HTTP 200;
this check does not need any existing products or orders.
If you receive 401, check the key and brand with your administrator. See
Authentication for access and rate limits.
Build an integration
Choose a tutorial based on the result you need. Each includes runnable Node.js examples and explains how to retrieve records beyond the first page.Find the data you need
Start with Product graphs, Entity relationships,
and Pagination and errors. Every collection’s filters and exact
response fields appear in the API Reference tab.
For AI assistants and automation platforms that speak MCP, see
Model Context Protocol (MCP). API-key MCP is available on the
deployed API; browser OAuth connectors are documented there when they ship.
Find known records with business identifier lookups,
then use direct Quote navigation or
productGraph() to retrieve their related data.