MCP & API · Available now

API keys

Workspace API keys for MCP clients, automations and your own code.

API keys let tools outside Postsiva act on your workspace. Use them to connect MCP clients, ChatGPT, or your own scripts to the Postsiva API. Keys are stored encrypted, and you can remove any key at any time.

Start freeHelp article

What you can do

  • Create named keys per workspace
  • Limit a key to certain platforms or give it full access
  • Reveal a key again later if you lose it
  • Delete a key to cut off access instantly
  • Use the same key for MCP servers and the REST API

How it works

  1. 01

    Open API keys

    In Postsiva, go to Integrations → API keys.

  2. 02

    Create a key

    Give it a name you'll recognize, choose its scope and copy the secret.

  3. 03

    Use it

    Send it in the X-API-Key header, or add ?api-key= to the URL for clients that need it.

Questions

How are keys stored?

Secrets are encrypted at rest. Workspace members can reveal a key again from the API keys page.

What if a key leaks?

Delete it on the API keys page. Anything using it stops working right away, then create a new one.

Are API keys on every plan?

API keys come with plans that include them. Check your plan on the billing page.

More in MCP & API

← All integrations