Browse the docs
Start
API reference
MCP
Webhooks
Platforms
Guides
Developers
One key. REST, MCP, webhooks.
Schedule posts to your connected channels with one request, give your assistant the same key through the MCP server, and be told when a post lands. Eleven channels are wired; each platform page says whether it delivers for customers today. Base URL https://api.overads.io/public/v1, MCP at https://api.overads.io/public/v1/mcp.
Start
A key, a first post, the rules every call follows.
- Getting startedCreate a key, schedule a post with one request, then plug the same key into your AI assistant.
- AuthenticationBearer keys, the eight scopes, expiry, and the status codes a bad credential produces.
- Rate limitsPer-workspace ceilings by plan, the headers that report them, and what a 429 looks like.
- ErrorsThe one error shape, every code in the catalogue, and what to do about each.
- IdempotencyThe Idempotency-Key header: replay, conflict and in-flight semantics on every write.
API reference
Every route under /public/v1, with fields and one curl each.
- ConnectionsList the social accounts a workspace connected, with token health and the last delivery outcome.
- PostsCreate, list, edit, cancel and publish posts, and read the per-account delivery log.
- MediaTwo ways to attach media: public URLs the server downloads, or presigned uploads for large files.
- Best timesSuggested slots to schedule into, from the workspace's own publish history.
- Webhooks APIRegister endpoints, rotate secrets, read the delivery log, redeliver and test.
- AnalyticsAd accounts, spend and results by day, and the landing-page crawl, every response with provenance.
- WorkspacesCreate client workspaces, mint keys for them, and issue hosted connect links, for agencies and B2B.
MCP
The server, client setup, and every tool.
Webhooks
Events, signatures, retries.
Platforms
Limits, settings and review status per channel.
- InstagramInstagram over the overads API: status, connection, limits, media rules and platformSettings keys.
- FacebookFacebook over the overads API: status, connection, limits, media rules and platformSettings keys.
- LinkedInLinkedIn over the overads API: status, connection, limits, media rules and platformSettings keys.
- XX over the overads API: status, connection, limits, media rules and platformSettings keys.
- BlueskyBluesky over the overads API: status, connection, limits, media rules and platformSettings keys.
- MastodonMastodon over the overads API: status, connection, limits, media rules and platformSettings keys.
- ThreadsThreads over the overads API: status, connection, limits, media rules and platformSettings keys.
- YouTubeYouTube over the overads API: status, connection, limits, media rules and platformSettings keys.
- TikTokTikTok over the overads API: status, connection, limits, media rules and platformSettings keys.
- PinterestPinterest over the overads API: status, connection, limits, media rules and platformSettings keys.
Guides
Recipes for the things people build first.
- Cross-platform postingOne request, several channels: shared copy, per-platform variants, per-platform settings, per-account results.
- Scheduling and approvalsHow scheduledAt is interpreted, what pending means, and how a post gets through approval.
- Media by URL and presigned uploadsWhen to pass a URL, when to upload, and the exact three-call upload sequence.
- n8nHTTP Request node recipes for posting, a Webhook node for events, and the MCP Client Tool for agents.
- MakeHTTP module recipes for posting from a Make scenario and a Custom Webhook for events.
- ZapierWebhooks by Zapier recipes for posting, Catch Hook for events, and the MCP server for Zapier Agents.
- Workflows over the APIList, run and poll the workspace's automations from a script or an agent.
- Managed workspacesFor agencies and B2B: create a workspace per client, let the client connect channels on a hosted page, then post for them.
Something the docs do not settle? Write to us. The full text of every page is also at /llms-full.txt for agents.
