5 Simple Steps

How PostquedWorks

From scoped API access to durable multi-platform delivery. Here's the safe workflow for apps and agents.

Workflow
5 steps
Access
Scoped
Delivery
Durable
The workflow

From workspace to published post.

01

Choose your workspace

Create an organization-bound API key, then resolve the workspace you want your app or agent to use. Machine requests always stay inside that explicit scope.

GET /v2/mcp/context
Authorization: Bearer pq_...
02

Connect your social accounts

Connect the channels you manage from the Postqued dashboard. OAuth stays interactive, while your API or agent can safely use the connected accounts afterward.

Dashboard → Accounts → Connect account
03

Upload your content

Start an upload session, upload your video or images, then confirm completion. Your content is securely stored and ready to publish.

POST /v2/content/upload
PUT {presignedUploadUrl}
POST /v2/content/upload/complete
04

Validate, then publish

Dry-run the exact multi-platform request first. When it is valid, send the same request with dryRun set to false and a unique Idempotency-Key header.

POST /v2/publish
{
  "workspaceId": "workspace_uuid",
  "contentIds": ["content_uuid"],
  "targets": [{
    "platform": "instagram",
    "accountId": "account_uuid",
    "intent": "publish",
    "caption": "Posted via API!"
  }],
  "dryRun": true
}
05

Track status

Poll the durable publish record until every target reaches a terminal state. Postgres remains the source of truth even while delivery retries are running.

GET /v2/publish/:publishId?workspaceId=workspace_uuid
// pending, processing, completed, partial_failed, failed, canceled
Using an AI Agent?

Skip the manual integration.

Install Postqued as an OpenClaw skill and let your AI agent handle everything.

$npx clawhub install postqued-api
Next steps

Keep exploring Postqued.

Ready to run the workflow?