Connect the systems you already run.

Every integration uses the same authentication, idempotency, workspace scoping, and retry contract.

Integration patterns

n8n

Use an HTTP Request node with bearer authentication, JSON body mode, and an idempotency expression.

Make

Use HTTP → Make a request, map fields from the trigger, and store the returned post ID.

Zapier

Use Webhooks by Zapier → Custom Request for direct API calls and paths that preserve response data.

Custom services

Call the REST API from a trusted backend and subscribe to webhooks for asynchronous status changes.

AI agents

Use MCP for tool discovery and governed actions, or REST for deterministic orchestration.

CI/CD

Create release announcements or changelog drafts from deployment events while retaining approval gates.

HTTP request template

RequestCopy and customize

POST https://app.postzivo.com/api/public/v1/posts
Authorization: Bearer YOUR_API_KEY
Idempotency-Key: {{unique_run_id}}
x-postzivo-workspace-id: {{workspace_id}}
Content-Type: application/json

Production checklist

Keep API keys in the integration platform’s encrypted credential store.
Use a stable event or run identifier as the idempotency key.
Set explicit timeouts and handle 429 and 5xx responses.
Store returned resource IDs for later status checks.
Use webhooks when a publish or approval result is asynchronous.

READY TO BUILD?

Connect your workflow.

Request access, create an API key, and start with one test workspace.

Get started ↗