Publishing to six networks from one endpoint

Every social network has its own API, its own OAuth flow, its own media rules and its own rate limits. Integrate all of them yourself and you get six SDKs to maintain, six failure modes to handle, and one very long support queue.

The Content Posting API exists to make that someone else's problem.

One request

curl -X POST https://api.agentiq.social/v1/publish \
  -H "Authorization: Bearer ag_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "platforms": ["x", "linkedin", "threads", "tiktok", "instagram", "youtube"],
    "text": "One request. Every network.",
    "media": ["https://cdn.example.com/slide-1.png"]
  }'

One request fans out to every network. Each network reports its own status: published, scheduled, retrying, failed — with a machine-readable error code when something goes wrong.

Per-network statuses, not all-or-nothing

The important detail: publishing is per-network. If LinkedIn rejects your media while X succeeds, X stays live and LinkedIn reports invalid_media with a code your system can act on. No rollbacks, no false negatives.

Media conversion is included

Upload once. We convert images and video to each network's spec — MP4/H.264 for video, per-network dimensions, EXIF stripped — and attach them where they belong. The media handling you'd otherwise spend weeks on is a solved problem.

Retries and webhooks

Transient failures (rate limits, network blips) retry automatically with backoff. State changes are pushed to your webhook endpoint, signed with an HMAC secret so you can verify them.

Boring is the feature

The best integration is the one you forget about. One endpoint, one key, six networks — that's the whole pitch.