Make your first API call

Authenticate, set your tenant, and fetch your first records from the Partners API

Use an API key and tenant slug to fetch live content from your site.

Partners API access must be enabled on your plan. A Basker administrator issues and manages API keys. The standard account screen does not generate keys.

Get an API key

Ask your Basker contact or an authorized platform administrator to issue a Partners API key. Store the key in a secrets manager or environment variable. Do not put the key in browser code. Do not commit the key to source control.

Your key looks like a1b2c3d4-e5f6-7890-abcd-ef1234567890.

For the full authentication reference, see Authentication.

Confirm your tenant slug

Every request resolves a single tenant, your site. The tenant slug is the short identifier in the request path, for example remarkable-theatre. Your Basker contact can confirm it.

If you manage more than one site, see Multi-tenancy for how tenant context works.

Make the request

Fetch the first page of pages for your site. Replace the key and tenant slug with your own:

curl -s \
  -H "Authorization: users API-Key a1b2c3d4-e5f6-7890-abcd-ef1234567890" \
  "https://api.basker.app/partners/2026-02/remarkable-theatre/pages"

The path is /partners/{version}/{tenant}/{resource}. Here the version is 2026-02, the tenant is remarkable-theatre, and the resource is pages.

Read the response

A successful request returns 200 with a paginated envelope: a docs array of records plus pagination metadata.

{
  "docs": [
    { "id": "000000000000000000000001", "title": "Home", "slug": "home" }
  ],
  "totalDocs": 12,
  "limit": 10,
  "page": 1,
  "totalPages": 2,
  "hasNextPage": true,
  "hasPrevPage": false
}

If you get a 401, recheck the Authorization header. The scheme must be exactly users API-Key, not Bearer. See Status codes for the full list.

Next steps

Pagination: page through large result sets and sort them.
Filtering: narrow results to what you need.
Field selection: trim responses to specific fields.
Reference: every resource and endpoint, with request and response detail.