Welcome · Postnavo API

WelcomeWhat the Postnavo API is, what you can build with it, and how to make your first call.The Postnavo API lets your own scripts and apps read your workspaces and channels, upload media, make and manage posts, and read analytics. Webhooks tell your server as things happen. Every answer is JSON.These guides explain how it works. The reference lists every call, with what it takes and what it answers.What you can build

Schedule posts from your own app

Make posts with Create a post: as a draft, for a time, in each channel’s queue, now, or sent for approval. One call can post to many channels, each with its own text and settings. See Posting.

Fill the Library with media

Add images, videos and PDFs to a workspace’s Library with Upload a file, or have Postnavo fetch them with Add a file from a link. Then use them in posts by their IDs. See Media.

Hear what happens with webhooks

A webhook sends a message to your server as things happen: a post goes out or fails, needs approval or is approved, or a channel needs reconnecting. Add one in Account settings → API, or with Add a webhook. See Webhooks.

Automate with Zapier, Make and n8n

Use Postnavo from Zapier, Make and n8n, with their own tools for calling an API and catching webhooks. See Zapier, Make and n8n.

Read analytics

Read a channel’s daily numbers and totals over a period with Channel analytics, and a post’s numbers so far with Post analytics. Both come from what Postnavo has already fetched from the networks.

Quick start

In Postnavo, open Account settings → API and make a key. Only the account’s Owner and Admins can make keys.

Copy the key’s secret. It starts with pn_live_ and is shown only once, so keep it somewhere safe. If you lose it, delete the key and make a new one.

Send the key in the Authorization header of every call, as a Bearer token. Ask who the key is:

curl https://api.postnavo.com/v1/me \ -H "Authorization: Bearer pn_live_…" \ -H "Accept: application/json"The answer names the key, its account, the person who made it and the IDs of the workspaces it can reach:{ "key": { "id": "01k9zq5d6e7f8g9h0j1k2m3n4p", "name": "Our website", "access": "write", "all_workspaces": true, "created_at": "2026-11-05T09:30:00Z" }, "account": { "id": "01k9zq1a2b3c4d5e6f7g8h9j0k", "name": "Acme", "plan": "agency", "read_only": false }, "maker": { "id": "01k9zq6e7f8g9h0j1k2m3n4p5q", "name": "Sara Khan", "email": "sara@example.com" }, "workspace_ids": ["01k9zq2b3c4d5e6f7g8h9j0k1m"] }

Keys only ever go in the header, never in the address.

Where to go nextHow to useThe base URL, and the basics every call shares.AuthenticationWhat a key may do, and when it stops.PostingMaking, changing and sending posts, and each network’s settings.MediaAdding images, videos and PDFs to a workspace’s Library.WebhooksMessages to your server as things happen.ErrorsThe error codes, and what each one means.Rate limitsHow many calls and new posts a key may make in a minute.PagingGetting a list a page at a time.Retrying safelyRepeating a request safely.Zapier, Make and n8nUsing the API and webhooks from them.ChangelogWhat changed, and when.