Introduction

What the PostFlow API does, where it lives, its conventions, and what you need before the first call.

The PostFlow API lets your code do what the app does: read the connected accounts, bring in photos and videos, draft, check, schedule and publish posts, answer comments and direct messages, and read analytics. Webhooks tell your server when something happens. AI assistants use the same features through the MCP server.

Base URL

https://postflow.biz.id/api/v1

Every endpoint sits under /v1. The OpenAPI 3.1 document describes all of them; import it into Postman, Insomnia, Bruno or a client generator.

What you need

A PostFlow workspace with an active subscription or trial. Reading works whatever the subscription status; creating and publishing need it active.
An API key from Settings → Integrations → API & MCP (workspace owners), sent as Authorization: Bearer pf_…. See Authentication.

Conventions


Format	JSON in and out (`Content-Type: application/json`), UTF-8. File uploads send raw bytes.
Ids	Opaque strings. Don’t parse them.
Times	ISO 8601 with an offset or `Z` in requests, e.g. `2026-11-03T09:00:00+07:00`. Responses use UTC (`…Z`).
Time zone	Each workspace has one (default `Asia/Jakarta`), returned by `GET /me`. Calendar days, queue slots and analytics days use it.
Errors	`{ "error": { "code", "message", "details" } }` with a matching HTTP status. See Errors.
Pages	Cursors and `before` timestamps. See Pagination.
Limits	120 requests a minute per key. See Rate limits.