Skip to content
Posting API

Social Media Posting API

Post to X, Instagram, Facebook, TikTok, LinkedIn, YouTube, Pinterest and Google Business with one call. Every customer or AI agent gets its own key, limits and log.

  • One endpoint for every platform and format
  • Media checked against each platform's rules first
  • A result per platform, with a plain reason on failure
  • A separate key, cap and log per customer or agent
post.tsnode
const pk = new Postkey(process.env.POSTKEY_KEY);

await pk.posts.create({
  content: "We just shipped dark mode",
  accounts: [
    "acc_ig_123",
    "acc_li_456",
    "acc_x_789"
  ],
  media: [
    {
      type: "image",
      url: "https://cdn.example.com/dark-mode.png"
    }
  ]
});
  • Instagrampublished
  • LinkedInpublished
  • Xpublished

3 platforms · 1 call · key customer_42

Three steps to your first post

  1. 1

    Connect accounts

    Your customer signs in with each network's own login. You get an account ID per profile, Page or channel.

  2. 2

    Make a key

    Create a key for that customer or agent. Choose which accounts it can post to and how much.

  3. 3

    Post

    Send content and media to /v1/posts with that key. Each platform's result comes back in the response and by webhook.

One request, one clear response

List the accounts, add text and media. The response has one result per platform, so nothing gets blended into a single vague status.

RequestREST
1POST https://api.postkey.dev/v1/posts2Authorization: Bearer pk_cust_42_…3Content-Type: application/json4 5{6  "content": "We just shipped dark mode",7  "accounts": [8    "acc_ig_123",9    "acc_li_456",10    "acc_x_789"11  ],12  "media": [13    {14      "type": "image",15      "url": "https://cdn.example.com/dark-mode.png"16    }17  ]18}
Response

200 · published to 3 accounts

Counted against customer_42 only.

{
  "id": "post_8f21c",
  "status": "published",
  "results": [
    {
      "account": "acc_ig_123",
      "platform": "instagram",
      "status": "published",
      "url": "https://www.instagram.com/p/…"
    },
    {
      "account": "acc_li_456",
      "platform": "linkedin",
      "status": "published",
      "url": "https://www.linkedin.com/feed/update/…"
    },
    {
      "account": "acc_x_789",
      "platform": "x",
      "status": "published",
      "url": "https://x.com/acme/status/…"
    }
  ]
}

What the posting API handles for you

  • Every format, one shape

    Feed posts, Reels, Stories, threads, documents, Shorts and Pins all use the same request. Platform options sit under the platform's name.

  • Media handled

    Send a URL or a file. Postkey runs each platform's upload flow, including chunked and resumable video uploads.

  • Checked before it's sent

    Length, media and account type are checked against each platform's published rules, so you get a clear error, not a failed post.

  • A result per platform

    One post to four networks gives four results. One failure never hides the others.

  • Processing tracked

    Video takes time on most networks. You get a webhook when it's live, or the reason it isn't.

  • Keys that can't overreach

    Each key only sees the accounts you gave it, within the limits you set. Turn one off without touching the rest.

Works with your stack

  • Your code

    Node and Python SDKs with the same calls, or plain REST from anything that speaks HTTP.

    • Node
    • Python
    • {}REST
    Read the docs
  • No-code tools

    Call the REST API from an HTTP step in n8n, Make or Zapier. Give each workflow its own key.

    • n8n
    • Make
    • Zapier
    Postkey with n8n
  • AI agents & MCP

    The MCP server lets Claude, Cursor and other agent tools post through their own key, with caps they can't change.

    • MCP server
    About the MCP server

Posting API questions

Something not here? Email hello@postkey.dev.

Which platforms can I post to?

X, Instagram, Facebook, TikTok, LinkedIn, YouTube, YouTube Shorts, Pinterest and Google Business. Each has its own page with the formats and rules.

Do my customers need developer accounts?

No. They connect through each network's normal login screen. Postkey holds the platform apps.

How is this different from other posting APIs?

The posting part is similar. The difference is the key: each customer or agent gets its own, with caps, duplicate blocking, a log and an off switch.

What happens when a post fails on one platform?

The others still go out. The failed one gets its own result and webhook with a plain reason and whether a retry can help.

Is there an SDK?

Node and Python SDKs, plus plain REST. There's also an MCP server for AI agents.

What does it cost?

Free to start. Paid plans charge by posts sent, with unlimited connected accounts. See the pricing page.

Post everywhere, one key at a time.

Get a key, connect an account, send your first request.