API setup

Use your signed-in workspace to preview content and manage posts with code.

1
Open your workspace
Sign in to Postii, open your dashboard, and open the browser’s developer console.
2
Run your first request
The guided setup gives you a read-only request to see the available platform capabilities.
3
Check your destinations
Review connected publications and their permissions before creating or scheduling a post.

Set up with your AI assistant

Paste this prompt into an assistant with browser site-tool support.

Help me use Postii’s workspace API with my signed-in account.
The Analytics page is a sample-data frontend preview only; there is no live analytics API.
Independent hosting uses Google or Apple OAuth and server-verified Postii sessions after operator configuration. Email sign-in uses a 6-digit code only after the operator configures Resend and a verified sender. Never ask for a sign-in code. New users enter their first and last name and optional company, then choose a Stripe test-mode trial. Connections are in Settings; invitations require an active Team or Max trial or subscription. Explicitly configured hosted previews use isolated demo sessions, not verified live accounts. Checkout and invitations require operator configuration; live billing is not enabled. Email signup creates a password followed by email verification. Never handle card details yourself. Never treat a button click or redirect as proof of successful authentication. Never ask for passwords, provider secrets or session cookies in chat.
Read the current API guide and OpenAPI schema first. Currently this is a same-origin browser API, not an external API-key or server-to-server service. Use my signed-in dashboard if your tools support it. If you cannot access the private guide or browser session, tell me what access is missing and ask for the guide text; do not invent credentials or endpoints.
Start with read-only capability and beehiiv connection checks. Explain which destinations are actually connected and which actions are supported. Social scheduling is currently a sandbox; beehiiv has separate real delivery endpoints. If setup is needed, Connect a platform opens the platform modal without leaving my draft; let me enter secrets there. Workspace menu → Settings → API & MCP contains → Explore the API; open the navigation menu first on mobile. Sidebar Updates are product news, not account or delivery status.
Do not create drafts, publish, schedule, send messages, replace keys, or disconnect accounts during setup. Before any later write, get my approval for the exact content, destination/publication, audience and time. For beehiiv, verify Send API eligibility; a connected key alone does not establish it. Keep the same operation ID and input on retries and inspect each delivery result; accepted is not published.
Social Connect buttons currently report an unavailable connection, not a successful authorization. Do not treat clicking Connect as evidence that an account is connected.
Finish with a short ready/not-ready summary and any next step I must take.

What’s available today

Requests run in your signed-in Postii browser tab. External API keys and server-to-server access are not available yet. Live publishing is available through connected beehiiv publications with Send API access. Social publishing is currently a sandbox.

API referenceFull documentation, examples, and troubleshooting

Open your workspace

Run your first request

Check your destinations

Set up with your AI assistant

What’s available today

A little less busywork.A little more you.

A little less busywork.
A little more you.