Authenticate, handle errors, and find the analytics collection and product API contracts.
The Embrasure REST API covers workspaces, the managed warehouse, sources, the catalog, context, and analytics. This reference covers authentication, errors, versioning, and analytics collection; the OpenAPI specification documents every public product operation.
| Base | Purpose |
|---|---|
https://api.embrasure.ai/v1 | Product API |
https://api.embrasure.ai/collect | Analytics event collection |
https://api.embrasure.ai/scim/v2 | SCIM provisioning for identity providers |
All routes use HTTPS. Product API routes use bearer authentication with a session, an agent session, or a personal access token. Most product routes take an explicit workspace_id. Analytics collection uses a public project key and an optional server key; see the collection reference.
| Area | Paths | Guide |
|---|---|---|
| Identity and tokens | /v1/auth/*, /v1/workspaces | Authentication |
| Warehouse databases, tables, and SQL | /v1/workspaces/{workspace_id}/warehouse/* | Warehouse, SQL |
| Sources and syncs | /v1/connectors/*, /v1/workspaces/{workspace_id}/warehouse/ingestion-connections/* | Sources |
| Catalog | /v1/catalog/*, /v1/schema-changes/* | Catalog |
| Context and memories | /v1/context/*, /v1/memories/*, /v1/semantic-models/* | MCP |
| Product analytics | /v1/workspaces/{workspace_id}/analytics/*, /v1/workspaces/{workspace_id}/product-analytics/* | Analytics |
| Usage and limits | /v1/workspace-usage/* | Limits |
npm install @embrasure/api-client.The collection OpenAPI schema contains the native analytics contract; the product OpenAPI specification does not include collection routes.