API Documentation

The Postfeeds API is a resource-oriented REST API. All requests and responses are JSON.

Every request needs an API key sent as a Bearer token. Create one at Dashboard → API Keys — the full key is shown once (only a hash is stored) and can be revoked instantly.

curl https://postfeeds.com/api/v1/accounts \
  -H "Authorization: Bearer pf_live_..."

Keys carry scopes (all granted by default): read for GETs, posts:write to create/cancel posts, profiles:write to create profiles.

1. Create an API key at Dashboard → API Keys.
2. Connect a TikTok account at Dashboard → Connections (one-time, in the browser — the OAuth flow needs a signed-in session, so accounts can't be connected via the API).
3. GET /accounts → copy the account id.
4. POST /posts with publishNow: true.
5. Poll GET /posts/{id} for delivery status.

# 1. Which accounts can I post to?
curl https://postfeeds.com/api/v1/accounts \
  -H "Authorization: Bearer $PF_API_KEY"

# 2. Publish a video to one of them
curl -X POST https://postfeeds.com/api/v1/posts \
  -H "Authorization: Bearer $PF_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "New drop",
    "media": ["https://cdn.example.com/clip.mp4"],
    "platforms": [{ "platform": "tiktok", "accountId": "<account id>" }],
    "publishNow": true
  }'

Post modes

Post lifecycle

draft → scheduled → uploading → processing → failed | canceled. processingmeans the content was handed to the platform — for TikTok it's now in the user's TikTok app inbox (drafts), where they finish publishing. Failed posts carry an error message.

Media is passed by URL— the server downloads it. URLs must be public http(s). If your files aren't hosted anywhere, upload them first with POST /media/presign and use the returned publicUrl. Per post, exactly one of:

Photos are auto-resized to TikTok's 1080×1920 canvas, re-encoded as JPEG and rehosted on Postfeeds' TikTok-verified storage — your image host does not need TikTok URL verification.

Every error has the same envelope and a meaningful HTTP status:

{ "error": { "code": "invalid_request", "message": "media must be an array of URLs" } }

Default: 60 requests/minute per key. Every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset; exceeding the limit returns 429 with Retry-After: 60.

POST /posts accepts an Idempotency-Key header (any unique string). Replays return the original response with Idempotency-Replayed: true — safe retries, no double-posting.

The API currently delivers to TikTok and LinkedIn. Other platforms return 422 unsupported and are coming as their backends ship.

• TikTok— video posts use the inbox/draft flow: the video lands in the connected user's TikTok app inbox and they tap to finish publishing — the right flow while a TikTok app's Content Posting audit is pending. Photos land as drafts via MEDIA_UPLOAD. Media is always required.
• LinkedIn— posts publish straight to the member's feed (status published, post URN in publishId). Text-only or 1–35 images; video not yet supported. Tokens last ~60 days without refresh — expired accounts show expired and need a reconnect.
• Accounts are connected in the dashboard (Dashboard → Connections), not via the API — the OAuth flow requires a signed-in browser session.

If your client currently targets Zernio's API:

Zernio account/profile IDs are meaningless here — re-fetch them from GET /accounts and GET /profiles after connecting your accounts.