logo
Schedulin

Using the Schedulin API

The API lets you build custom workflows that Zapier can't cover. It exposes most of the surfaces you see in the UI — channels, posts, media, analytics, and client profiles.

Getting an API key

  1. Go to Settings → API & Apps.
  2. Click Create key.
  3. Name the key (e.g. "Content automation") and copy the secret. You won't see it again.

API keys are workspace-scoped — they can only access the workspace they were created in.

Authentication

Send the key in the x-api-key header:

x-api-key: sk_live_...

Apps that act on behalf of other Schedulin users use OAuth instead and send the access token as Authorization: Bearer ....

Common endpoints

All endpoints live under https://api.schedulin.app/v0.

  • GET /v0/workspace — your workspace, its plan, and usage against plan limits.
  • GET /v0/social-accounts — list connected channels.
  • POST /v0/posts — create a post: publish now, schedule, add to the queue, or save as a draft.
  • POST /v0/post-groups — create posts for several channels in one request (1–50 posts, each with the same body as POST /v0/posts). It's all-or-nothing: if any post is invalid, none are created.
  • GET /v0/posts — list posts.
  • GET/POST /v0/ideas, PATCH/DELETE /v0/ideas/{id} — read and manage your Ideas board.
  • GET /v0/posts/{id}/analytics — pull a post's metrics.
  • GET/PUT /v0/social-accounts/{id}/queue-schedule — read or replace a channel's weekly queue schedule.
  • GET /v0/analytics/overview, /v0/analytics/platforms, /v0/analytics/top-posts — workspace-wide totals, a per-platform breakdown, and your best posts for a date range.

Full reference at developers.schedulin.app.

Client profiles and connect links

Client profiles are the API side of Clients. Use them to group channels per client, or per user of your own app, and to let those users connect their own social accounts.

  • GET /v0/profiles — list profiles, each with its connected social accounts.
  • POST /v0/profiles — create a profile with a name and an optional externalId (your own ID for the client or user, unique in your workspace).
  • GET /v0/profiles/{id}, PATCH /v0/profiles/{id}, DELETE /v0/profiles/{id} — get, rename, or delete a profile. {id} can be the profile ID or your externalId. Deleting a profile keeps its accounts connected; they're just no longer grouped under it.
  • POST /v0/profiles/{id}/connect-link — create a hosted link to send the account owner. Returns { url, expiresAt }.
  • GET /v0/social-accounts?profileId=... — list only the accounts in one profile.
  • PUT /v0/social-accounts/{id} with profileId — move an account into a profile, or set profileId to null to remove it from its profile.

Connect link options (all optional):

  • platforms — limit the link to specific platform slugs, e.g. ["instagram", "tiktok"]. Omit to offer every supported platform.
  • expiresInHours — how long the link works. Defaults to 72 hours, maximum 168 (7 days).
  • redirectUrl — shows a Done button on the connect page that takes the user back to this URL, e.g. your app's settings page.
curl -X POST https://api.schedulin.app/v0/profiles/user_42/connect-link \
  -H "x-api-key: $SCHEDULIN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "platforms": ["instagram", "tiktok"], "redirectUrl": "https://yourapp.com/settings/social" }'

The user opens the link and signs in to their social platforms. They don't need a Schedulin account. The accounts connect to your workspace under the profile and count toward your plan's channel limit. Client profiles need an active paid plan.

A link stops working when it expires, when the profile is deleted, when the user who owns the API key or OAuth token that created it leaves the workspace, or when the workspace no longer has an active plan. Create a new link at any time.

To find out when someone finishes connecting, subscribe a webhook to social_account.connected. It fires once per connected account and includes the account's profileId.

Rate limits

  • 300 requests per minute per API key, across all endpoints. Going over returns 429 with a Retry-After header.
  • Each network's own posting limits also apply — see Daily posting limits.

Webhooks

Subscribe to events from your code instead of polling:

  • post.published
  • post.failed
  • generation.completed
  • generation.failed
  • social_account.connected

Configure under Settings → Webhooks.

See also