Post with Zapier
Webhooks by Zapier can call the same publish API as curl. Prefer a proper JSON body (profile + text) over comma-separated platform strings so addressing matches the docs.
Get started free →Free tier. No card · one API for every network · full MCP access
The rest of your stack is in Zapier and you need multi-network publish without a custom Zapier app.
Same setup the docs quickstart uses. Do this once:
my-brand) and connect at least one account. Bluesky is the fastest first channel: no app review. Instagram/TikTok/Facebook need each platform's review before API posting.sk_live_…). It shows once; treat it like a password.Configure once, then reuse on every run. Same request body as the docs, this is just how Zapier sends it.
https://api.postlake.dev/v1/posts.Authorization = Bearer sk_live_…, Content-Type = application/json, optional Idempotency-Key.{"text":"{{trigger text}}","profile":"my-brand"}. To filter networks, add "platforms":["bluesky","linkedin"] as a JSON array, not a comma-separated string.text. Test the step and open the response to confirm each targets[] entry.scheduledAt as UTC (trailing Z) or a naive local time plus timezone.You get one Post with an overall state and a targets[] array. One entry per account. Always check each target; partial success is normal.
{
"id": "post_a1b2c3",
"state": "partial",
"targets": [
{ "platform": "bluesky", "state": "published", "url": "https://bsky.app/…" },
{ "platform": "linkedin", "state": "failed",
"error": { "type": "invalid_request", "message": "…", "retryable": false } }
]
}published: every target succeeded. partial: some published, some failed. failed: none published. processing: still going (async networks like TikTok).Idempotency-Key header on writes so a retry never double-posts.Same rules as the docs. Pick one addressing style:
"profile": "my-brand" posts to every account under that profile (the name on Channels)."platforms": ["bluesky", "linkedin"] narrows that set. It is a filter, not a selector: if you have two Pinterest boards, both match pinterest."accounts": ["acc_…"] for exact channels (copy an id on Channels, or GET /v1/social-accounts).profile? PostLake uses that profile. Multiple profiles and you omit it? You'll get an error that names them.See Publishing: where to post.
scheduledAt as UTC (trailing Z), or a naive local time plus timezone (IANA, e.g. Europe/London). Credits charge when it fires. Scheduling docs · scheduling guide.POST /v1/media, then pass the med_… id in media. Media docs.textOverrides (e.g. shorter text for X). Per-network options: platformOptions (Pinterest boardId, TikTok privacy, …). Live option lists: GET /v1/platforms/{platform}.POST /v1/posts/validate runs the same checks without publishing (free).platforms strings are wrong. The API expects a JSON array of platform ids.partial; add a Filter or Code step if you need all targets published.Prefer an assistant over Zapier code? Point it at MCP (https://api.postlake.dev/mcp). Prefer the dashboard? Use Quickstart → No code.
Webhooks by Zapier POST to https://api.postlake.dev/v1/posts with Authorization: Bearer and JSON { text, profile }. PostLake publishes to connected accounts on that profile.
No. Webhooks by Zapier is enough. One REST endpoint covers every network you have connected.
Yes, include scheduledAt (UTC, or a naive local time plus timezone) in the webhook JSON. Credits charge when it fires. See docs → Scheduling.
These guides stay short on purpose. Canonical behaviour lives here:
Also: Media · Errors · MCP · Analytics
All guides · Full docs · llms.txt · Markdown
Stuck? The docs are the source of truth, start at Publishing.
Open the dashboard →