Skip to main content
Where: Settings, Developers
Availability: Postiz Cloud, Standard plan and above. Self-hosted installs have it on every install.
This tab is the entry point to everything programmatic. The reference documentation lives in its own tabs; this page is about the controls in the UI.

​
Access

​
Your API key

Rotating is the fix if a key leaks, and the only fix: keys do not expire on their own.

​
MCP client configuration

Postiz generates the configuration block for connecting an AI client through MCP. Pick your client and whether you are using a local CLI or a remote client, then copy the block.

​
CLI and skills

The same section offers the setup for the CLI, for local use or for CI.

​
Apps

This is where you register an OAuth application, for building something other Postiz users will authorise, rather than something that acts as you.
1

Create OAuth App

Name and redirect URL are required. Description and icon are optional, and both are shown to users on the consent screen, so they are worth filling in.
2

Copy the credentials

You get a client ID and a client secret.
3

Implement the flow

See OAuth2 for developers.
Rotating the client secret invalidates the old one immediately. Every token exchange using the old secret starts failing, so deploy the new secret first.

​
API key or OAuth app?

If you are automating your own posting, use the API key. Build an OAuth app only when other people’s accounts are involved.

​
Where to go next

Public API

Endpoints, payloads and per-platform settings.

CLI

Post from your terminal or from CI.

MCP

Connect Claude, Cursor or ChatGPT to Postiz.