Skip to content
SocialApp
Log in Create account

API, MCP and extension

Create and manage API keys

Generate the workspace API key in Settings, Security, copy it once, regenerate or delete it, the scopes a key carries and why keys never go in a link.

Last updated 2 min read

On this page
  1. Generate a key
  2. Regenerate or delete
  3. What a key can do
  4. Keep keys out of links

API keys let programs act in your workspace. The workspace Owner manages the main key in Settings, Security, on the API Key card.

Generate a key

  1. Choose Generate API Key.
  2. Copy the key at once. It is shown only once; afterwards only its beginning is shown, followed by "(hidden)".
  3. Store it in a password manager or your server's secret store.

Keys are stored by SocialApp in a form that cannot be turned back into the key, so a lost key cannot be shown again: regenerate it instead.

Regenerate or delete

  • Regenerate creates a new key and ends the old one at once. Update your programs with the new key.
  • Delete ends the key without a replacement.

What a key can do

A key acts as the person who created it, with their role and account access, in the key's workspace. If that person is removed or deactivated, the key stops working. The Owner's key carries every scope: reading accounts, reading and writing posts, uploading media, tags, queue times and analytics. Keys created before the social scopes existed must be regenerated to get them.

Always send a key in the Authorization header. A key in a web address ends up in logs and browser history, so SocialApp never accepts one there.

The REST API needs the Ultimate plan; the same key also works with the MCP server on every plan.