Resources

Known limitations

What the API does, it does for real. But some things aren't built yet — here they are in plain sight, each with a workaround, so nothing surprises you in production.

API surface

LimitationTodayWorkaround
Connecting accountsThe API is read-only for accounts — no POST /accounts.Connect from the dashboard; list over the API.
Per-network statusThe post object exposes aggregate status, not per-network delivery.Use account health and the dashboard; retry per network.
RescheduleNo in-place reschedule endpoint.Cancel and re-create at the new time.
IdempotencyNo idempotency keys — repeated POSTs publish again.Track sent ids on your side before retrying.
API-call limitUsage is metered against your allowance, not hard-blocked with a 429.Watch usage on /me and upgrade ahead of the ceiling.

Publishing & media

LimitationTodayWorkaround
Media hostingNo managed uploads — media must be a public URL you host.Host on your CDN and pass the URL. See Media.
Multiple mediaOne media URL per post; no carousels via the API.Send a single image or video per post.
Async confirmationTikTok / YouTube handoffs aren't polled to a final status.Treat published as “handed off”; confirm in-app for now.
AnalyticsOnly an account-level summary — no per-post analytics endpoint.Use Get analytics for totals.

Connections & tokens

LimitationTodayWorkaround
Hosted OAuthOAuth networks need a pasted access token; no hosted callback yet.Supply a token when connecting. See connecting accounts.
Token refreshNo automated refresh of long-lived tokens.Reconnect when health flips to attention.
Review & tiersSome networks gate public posting behind review or a paid tier.Each platform guide names the gate (e.g. X paid tier, TikTok audit).

Everything else is real

These are the edges — not the whole picture. The core loop (connect, publish, schedule, measure) works end to end against real network APIs. See the roadmap for when these edges close.