Beállítások

Fejlesztői beállítások

API-kulcs, MCP-kulcs, kész kliensbeállítások és az engedélyezett alkalmazások visszavonása.

Where to find it

The bottom-left profile button → Settings → Developers tab. This tab is available on the Pro plan or higher. It does not appear on lower-tier plans because they do not include programmatic interfaces.

The two types of keys

Key	Prefix	What it's for
API key	`psty_…`	For the public REST API and command-line tool. The key is the entire Authorization header value, without a Bearer prefix.
MCP key	`psty_mcp_…`	For connecting chat clients to the MCP server.

The two are not interchangeable

The MCP server deliberately rejects REST keys that start with psty_ and explains why. If a chat client cannot connect, this is the most common reason: you pasted the wrong type of key.

There is a third credential: an OAuth access token that starts with pos_. You do not create it here. An app receives it from your users. See the OAuth apps page.

Creating a key

1
Open the Developers tab
Under Settings.
2
Create a key
There are separate buttons for API keys and MCP keys.
3
Save it immediately
The key is shown only once, when you create it. You cannot retrieve it later.

Where to put the key

Put it in an environment variable or a secret manager, not in the code. The command-line tool reads the POSTY_API_KEY variable, or use the posty auth:login command, which stores the credential on your machine so it doesn't end up in your scripts.

Key rotation

The Rotate Key button issues a new key and invalidates the old one. Use this if the key ended up somewhere it shouldn't: a log, a screenshot, a public repository.

Rotation is immediate. Anything still using the old key will get a 401 on its next call, so update the configuration everywhere the key is used when you rotate it.

What the key can do

The key has the same access as its owner. If the user is demoted or removed from the workspace, the key's access changes immediately to match.
You can restrict a key's permissions and channels. An agent that creates drafts does not need publishing rights.
If the key belongs to more than one workspace, the showorg header selects which one the call applies to.

You'll find the full list of permissions on the Authentication page.

Ready-to-use client configurations

At the bottom of the tab, you will find configuration blocks for the most common AI clients. Use the button to copy a block, then paste it into the client's settings. The key is already included.

The per-client steps are on the MCP client setup page.

Is something missing from this page? Email [email protected] or use the form on the Help page.