Scoped API keys
Make a key for each customer or AI agent. It can post only to the accounts you give it, and everything it does is counted and logged under its name.
- One key per customer, workflow or agent
- Each key sees only the accounts you allow
- Usage and logs split by key
- Rotate or turn off one key without touching the rest
1// A customer signs up. Give them their own key.2const key = await pk.keys.create({3 name: "customer_42",4 accounts: [5 "acc_ig_123",6 "acc_li_456"7 ],8 dailyPostLimit: 20,9 monthlySpendLimit: 1510});11 12// Their key can't see anyone else's accounts.13const customer = new Postkey(key.secret);14await customer.posts.create({15 content: "Hello from customer 42",16 accounts: [17 "acc_x_789"18 ]19});403 · blocked: account not on this key
What comes back
{
"status": "blocked",
"reason": "account_not_allowed",
"message": "acc_x_789 isn't one of customer_42's accounts."
}How it works
One key, one owner
Name keys after the customer or agent that uses them. Every number on your dashboard is split the same way.
Accounts are the boundary
A key can only post to the accounts listed on it. A bug in one customer's flow can't reach another's accounts.
Rotate without downtime
Issue a new secret for a key and retire the old one. The key's name, limits and history stay.
The rest of Keys & control
Each of these works per key, so one customer or agent never affects another.
Works on every platform
The same keys, limits and log apply wherever the post goes.
- X Posting APIText · Image · Video · Thread
- Instagram Posting APIFeed post · Reel · Story · Carousel
- Facebook Posting APIText · Photo · Video
- TikTok Posting APIVideo · Photo
- LinkedIn Posting APIText · Image · Document
- YouTube Posting APIVideo
- YouTube Shorts Posting APIShort
- Pinterest Posting APIPin
- Google Business Posting APIUpdate post · Offer · Event
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
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
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
Questions
Something not here? Email hello@postkey.dev.
How many keys can I make?
As many as you have customers or agents. Keys are how Postkey is meant to be used.
Can two keys share an account?
Yes. For example, a customer's key and your support agent's key can both post to the same Page, each with its own limits and log.
What happens to a key's history if I delete it?
Its log stays, so you can still see what it posted and when.
Give everyone who posts their own key.
Get a key, connect an account, send your first request.
Free to start. Read the docs