Skip to main content
The Sapt API is the programmable surface of the Sapt platform. Everything the dashboard does, it does through these endpoints.

Social publishing

Schedule and publish organic posts to Instagram, Facebook, TikTok, YouTube and Google Business Profile.

Quickstart

Publish your first post in four calls.

Authentication

API keys, OAuth access tokens, and session cookies.

API reference

Every endpoint, generated from the live OpenAPI document.

​
Base URL

The OpenAPI document that generates this reference is served live at https://api.sapt.ai/openapi.json. It is the contract — if an endpoint is not in that document, it is not public, no matter what else is reachable over HTTP.

​
Projects

Almost every resource belongs to a project (a workspace). The project id is a UUID and appears as a path parameter:
An API key is already scoped to the projects it can reach, so passing a projectId your key cannot see returns 403, not 404.

​
Conventions

​
Backward compatibility

The OpenAPI contract is load-bearing. Fields are not removed from responses without a version bump — a retired field returns null or its empty shape rather than disappearing, so destructuring clients keep working. Request fields that are retired stay accepted and are ignored server-side.