MCP and API keys

Create and manage API keys

Make a personal key for a client that can't sign in with OAuth, and revoke it when you're done.

Most assistants connect by signing in, and never need a key. Create one when your client only accepts a static token.

Keys are personal. A key carries your access, so anything holding it can do what you can do, up to the access you gave it.

Create a key

  1. Open Settings and pick API Keys

    API Keys sits under General.

  2. Select Create API key

    Name it after the client, so you can tell your keys apart later. The field suggests Claude Desktop.

  3. Pick the access

    Read reads your Koast data. Write changes it. Publish pushes campaigns live to the ad platform. New keys are Read only until you add more. Pick the least this client needs.

  4. Set an expiry

    No expiry, 30 days, 90 days or 1 year.

  5. Set a publish limit, if you picked Publish

    Publish limit is the most this key may ever put live, in total. Publishing is refused without one.

  6. Copy the key

    Copy your API key shows the key once. Paste it into your client now.

The key is shown once

Koast never shows it again. If you lose it, revoke the key and create another.

What the list tells you

The Your keys table shows Name, Access, Publish limit, Created, Expires, Last used and Status. Last used is the fastest way to spot a key nothing is using any more.

Revoke a key

Revoke one the moment you stop using it. Anything still using that key stops working straight away, and it can't be undone.

On this page