Skip to main content
This document covers how to invoke and use the Artemis REST APIs for authentication, request format, error handling, pagination, and more.

Prerequisites

Before calling any API endpoint, ensure the following are in place:
  • An Artemis account with access to the relevant workspace.
  • A project created within that workspace.
  • Generated API credentials (Platform Key).
  • Confirmed scopes and permissions assigned to the credentials for the endpoints that you intend to use.

Authentication

A platform key is a long-lived bearer credential scoped to a tenant, a project, and a set of scopes. Its format is abl_<48 hex characters>, for example abl_3f7a1c9e42b8dxxxxa1e8c7b4d29f0a3e5c8b1d7f2a4exxxx. The headers are in the format X-API-Key: <platform key>.

Create a platform key

Navigation: Project → Settings → API Keys → Platform Keys → New Key.

Scopes and permissions

Scopes determine which resources and actions a given set of credentials can access. Requests made with credentials that lack the required scope for an endpoint fail during authorization, even if authentication succeeds. Every API request must include the API key in the X-API-Key header. Keys are tied to explicit scopes (for example, execute chat) assigned at creation. Note that access is scope-based, not origin-based.

Base URL

All API requests target your platform instance base URL of the format https://example.com/api/public. For URL of your instance, see the list of region-specific platform URLs.

Common request parameters

Pagination

List endpoints use offset-based pagination: Example
Paginated responses include a pagination object.

HTTP error codes