Skip to content
GenPageHelp center

Personal API keys

Create, copy and revoke the secret keys that let your own tools, scripts and MCP clients call the GenPage API on a workspace's behalf.

· For owners, admins and members

On this page

A personal API key lets your own tools, scripts and integrations call the GenPage API on behalf of one workspace, and lets an MCP client that cannot sign in with OAuth connect to GenPage. You manage your keys on Account → API Keys in Settings.

Before you start

  • The workspace's plan must include API keys. If it does not, the page shows API Keys require Scale plan instead of the key list, and the workspace owner gets an Upgrade Plan button there.
  • Every role can create keys. A key acts as you and only works on the workspace you create it in.
  • The list shows only the keys you created yourself; other members manage their own.

Create a key

  1. Click the gear icon at the bottom of the sidebar to open Settings, then choose Account → API Keys. The Secret keys section lists your keys. Click Create Key.

    The API Keys page with no keys yet and the Create Key button highlighted

  2. In Create new secret key, type a Name that tells you where the key will be used, then click Create Secret Key.

    The Create new secret key dialog with a name filled in and the Create Secret Key button highlighted

  3. Save your key shows the key once. Click Copy and store it somewhere safe, such as a password manager. You cannot view the key again later; if you lose it, create a new one. Under Permissions the key is listed as Read and write API resources.

    The Save your key dialog with the key hidden and the Copy button highlighted

  4. Click Done. The key appears in the list as Active, with its Created date, Last used (Never until the first request) and Created by.

    The API Keys list showing the new key as Active

Use the key

Your tool or script sends the key with each request; the View API docs link at the top of the page opens the API reference. The API covers workspaces and variables, leads, audiences, campaigns and their analytics, page generation and publishing, templates, form submissions and credits. Keys do not expire; they stop working only when you delete them. Last used updates whenever the key is used.

For MCP clients without OAuth, the MCP page under Configure in Settings explains how to send the key instead; admins and owners can open it.

Revoke a key

  1. Click the trash icon at the end of the key's row.

    The key's row with the delete icon highlighted

  2. In Delete API key, click Confirm.

    The Delete API key dialog asking to confirm

The key disappears from the list and stops working immediately. This cannot be undone; create a new key if a tool still needs one.

Was this article helpful?

Related articles