v1 API for AI overviews, link building data, and integrations usage.
The API reference in this section is generated from one OpenAPI file.
Base URL
Use the production API base URL for external integrations:Authentication
Every external API request must include an API key in thex-api-key header.
Workspace selection
If the API key owner belongs to more than one workspace, include thex-workspace-id header.
Project-scoped endpoints
Most AI overviews and link building data endpoints accept aproject query parameter.
When a route accepts project, you can pass the project ID, slug, or name within the selected
workspace. If the identifier is ambiguous inside that workspace, use the project slug or project
ID.
Project-scoped public API routes also require globally unique project names across workspaces. If
another workspace uses the same project name, the public API blocks those routes until the naming
collision is resolved.
Error format
Beeze returns structured problem details for common API errors, including:- missing or invalid API keys
- missing workspace context for users with multiple workspaces
- missing feature access on the current workspace plan
- ambiguous or missing project identifiers
- missing resources
What is included today
The current public API reference covers:- AI overviews results, visibility, sources, competitors, prompts, and tags
- link building summary stats, recent backlinks, team contributions, trends, backlink portfolio, and backlink market analytics
- integrations usage
api/openapi.yaml.