Postnavo REST API & webhooks
Everything in Postnavo is available through a REST API, with webhooks for publish events. Use it to build custom agents, connect internal tools, or automate posting from your product.
curl https://api.postnavo.com/v1/posts \
-H "Authorization: Bearer $POSTNAVO_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"channels": ["x", "linkedin"],
"text": "Hello from the API",
"scheduledAt": "2026-11-03T09:00Z"
}'Illustrative — final endpoints and commands are published at launch.
What your agent can do
- List connected channels
- Create, schedule and update posts
- Upload images
- Read the calendar and queue
- Fetch post analytics
- Require human approval before publishing
- Webhooks for published, failed and approved events
Works with
Anything that can call a REST API:
- n8n
- Make
- Zapier
- Your own code
Building on the API and webhooks
When the API is the right route
The MCP server and the CLI are for agents. The REST API is for everything else: your own product, an internal tool, or an automation platform. Postnavo is launching with all three on every plan.
Reading the request in the card
The request at the top of this page is illustrative. It shows the shape Postnavo is launching with: one HTTPS call, a bearer token in the Authorization header, and a JSON body.
The body names the channels, the text and the time. The time in the example ends in Z, which means UTC. Treat the field names as placeholders until the reference is published at launch.
Calling it from n8n
n8n’s HTTP Request node makes HTTP requests “to query data from any app or service with a REST API”. You can configure the node’s parameters yourself or import a curl command.[1]
So a curl request like the one in the card can become an n8n node, once Postnavo is launching and the final endpoint is published.
For the other direction n8n has the Webhook node, which can “receive data from apps and services when an event occurs” and start a workflow. It has a test URL and a production URL, and n8n registers the production one when you publish the workflow.[2]
Calling it from Make
Make’s HTTP app has a “Make a request” module, which makes an HTTP request to any server. It supports API key, Basic Auth and OAuth 2.0 authentication.[3]
Make’s advice is to define the key in the dedicated Credentials field rather than passing it through headers or query parameters. Make also allows only secure HTTPS.[3]
Postnavo is launching with an HTTPS API and bearer tokens, which is the case that module is for.
Webhooks: published, failed and approved
Postnavo is launching with webhooks for three events: a post was published, a post failed, and a post was approved. Each is a request Postnavo sends to an address you choose.
The failed event is the one to wire up first, because a scheduled post that does not go out should reach a person. In n8n that address would be a Webhook node’s production URL.[2]
Keep the token out of your code
A bearer token works like a password for your account. GitHub’s docs show where one belongs in a pipeline: a repository secret, created in Settings under “Secrets and variables”, Actions.[4]
Postnavo is launching with rate limits designed for normal agent and automation use. The numbers are documented at launch.
Frequently asked questions
Is the API included in every plan?
Yes. Postnavo is launching with the REST API and webhooks included in every plan.
Are there rate limits?
Yes. Limits will be documented at launch and are designed for normal agent and automation use.
Can I call the Postnavo API from n8n or Make?
Anything that can send an HTTPS request with a header can call it. n8n has an HTTP Request node and Make has an HTTP app for that. The API is launching with Postnavo.
What do Postnavo webhooks tell me?
Postnavo is launching with webhooks for published, failed and approved events, sent to an address you choose. The payload reference is published at launch.
Should I use the API or the MCP server?
Use the MCP server when an AI agent does the work, and the API when your own code or an automation tool does. Both are launching with Postnavo.
Sources, checked 2026-10-12
From the blog
- Platforms
Bluesky Link Preview Not Showing? Causes and Fixes
On Bluesky, the app that creates a post attaches the link preview. Why yours shows a bare URL or plain text, and how to check each cause, with sources.
- Guides
Scheduled Social Media Posts Not Publishing? How to Fix It
Why scheduled social media posts fail to publish: eight checks, cheapest first, with each network's documented token lifetimes, caps and error messages.
- AI agents
What Is an Agentic Social Media Scheduler?
An agentic social media scheduler lets an AI assistant plan and schedule posts through MCP, a CLI or an API. The terms, a comparison table and who approves.
Get your weekends back. Let AI handle your social.
Join the waitlist and lock in 30% off for life.
- Founding price for life
- No credit card
- Unsubscribe anytime