Activity log
Every post, refusal and failure, with the key that caused it. When a customer asks what happened, you can answer in a minute.
- Who posted, what, where and when
- Refused and failed posts, with the reason
- Filter by key, account or platform
- Agent run IDs kept with each post
1// What did this agent do last night?2const events = await pk.logs.list({ key: "agent_scheduler" });3 4// Same thing over REST:5// GET /v1/logs?key=agent_scheduler200 · 4 events
What comes back
[
{
"at": "2026-11-17T03:12:04Z",
"key": "agent_scheduler",
"event": "post.blocked",
"platform": "x",
"reason": "duplicate_blocked"
},
{
"at": "2026-11-17T03:08:51Z",
"key": "agent_scheduler",
"event": "post.published",
"platform": "x"
},
{
"at": "2026-11-16T22:30:00Z",
"key": "agent_scheduler",
"event": "post.scheduled",
"platform": "linkedin"
},
{
"at": "2026-11-16T21:02:17Z",
"key": "agent_scheduler",
"event": "post.published",
"platform": "instagram"
}
]How it works
Every outcome
Posted, scheduled, refused, failed. Not only the successes.
Under the right name
Each line carries the key that did it, so a support question becomes a filter, not an investigation.
Agent runs
Pass a run ID with a post and it's kept in the log, so you can trace one agent run end to end.
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.
What's in the log?
Each post attempt with its key, accounts, platforms, result and reason, plus key changes like limits or disabling.
Can I see it outside the dashboard?
Yes, through the API, filtered by key, account or time.
Does it log post content?
It logs what was sent so you can check it later.
Give everyone who posts their own key.
Get a key, connect an account, send your first request.
Free to start. Read the docs