Overview

The Basker Partners API is the authenticated REST surface for syncing content with external systems, powering mobile apps, and integrating Basker with the rest of your stack. Every collection in your site — pages, events, performances, people, venues, blogs, posts, media, and custom data — is reachable here.

This section covers everything you need to integrate against the Partners API.

What's covered

• Authentication — API keys and request headers.
• Multi-tenancy — how requests are scoped to a tenant.
• Versioning — date-based path versions and how to migrate.
• Rate limits — limits per API key and how to back off cleanly.
• Querying — pagination, filtering, field selection, and the full query parameters reference.
• Response format and error envelope.
• Status codes — every HTTP code the API returns.
• Reference — per-resource endpoint documentation generated from the OpenAPI spec.

Conventions used in this section

• All examples use the live host https://api.basker.app. The path shape is /partners/{version}/{tenant}/....
• Tenant slugs in examples use a placeholder like royal-opera-house. Replace with your own.
• API versions are date-based (2026-02, 2025-07); see Versioning.
• cURL is the canonical example syntax. For other languages, see Client libraries.

What's not here

• GraphQL. The Partners GraphQL surface will be documented in a dedicated section. While that's in progress, contact sales for early-access docs.
• Theme-facing read APIs. Public read-only JSON served from your own Basker site ({your-domain}/api/...) is documented under FrontStage API inside the Themes section. Use it for browser-side widgets in a theme.
• Admin and editor APIs. The /api/... paths used by the Basker admin to author content aren't part of the Partners API and aren't supported for external use.
• Webhooks. Webhook configuration ships with apps and is documented per-app; cross-cutting webhook documentation is a follow-up.