The publishing layer
for your AI stack.
REST API, OAuth 2.0, and API keys - built for developers, automation workflows, and AI agents that need controlled access to social publishing.
API access is available on paid plans. OAuth 2.0 is available for third-party apps.
One API call.
Scheduled across accounts.
Octopost's REST API lets you create, schedule, update, and publish posts programmatically. Connect it to n8n, Make, Zapier, LangChain, or your own service so generated content can move into a controlled publishing workflow.
Built for integration,
not just access.
PKCE-based OAuth 2.0 authorization is built in. Register your app as an OAuth client and request only the scopes your agent needs. Users stay in control of access, and tokens can be refreshed or revoked.
Core publishing workflows,
available via API.
Create posts, attach media, set publish times, target connected accounts, and read analytics from API endpoints. Your agent gets the publishing surface it needs without pretending every UI workflow is programmable.
REST API
Programmatic access to core posts, media, accounts, analytics, and workspace context.
OAuth 2.0 + PKCE
Authorization code flow with PKCE. Granular scopes. Register your app as an OAuth client.
Connected accounts
Create posts for connected accounts across supported platforms from one API.
Reliable scheduling
Schedule supported post formats for immediate publishing or a future time.
Two methods: (1) API key - generate a op_live_* key from Settings > API Keys and pass it as a Bearer token. Best for server-side agents and personal automations. (2) OAuth 2.0 Bearer token - for third-party apps where your app acts on behalf of users. PKCE-based authorization code flow, registered OAuth clients, and granular scopes.
Both. Pass a scheduled_at ISO 8601 timestamp to schedule for a future time, or use the publish-now endpoint for immediate publishing. The API covers the core publishing workflow: posts, media, accounts, and analytics.
60 requests per minute per API key. Rate limit headers are returned on every response so your agent can monitor remaining capacity. If you need higher limits for a high-volume workflow, contact us to discuss enterprise options.
Yes. Register your application as an OAuth client in Settings > App Clients. You'll receive a client ID and secret. Your app then initiates the standard OAuth 2.0 PKCE authorization code flow. Users authorize your app with specific scopes (e.g. posts:write, analytics:read). The well-known endpoint is available at /oauth/.well-known/oauth-authorization-server for discovery.
Your AI agent can write the content. Octopost publishes it.
API keys on plans with API access. OAuth 2.0 for third-party integrations. Start building today.