Manage API keys

API keys let you authenticate with Parseur and connect third-party tools.

What are API keys used for?

Direct API access – call Parseur’s REST API from your code, scripts, or CLI. See Authentication.

Automation platforms – connect Parseur to Zapier, Make, Power Automate, n8n, etc.

Open the API keys page

In the app: Account → API keys (direct link)

Permissions: on multi-user accounts, Admins and Editors can open this page.

Create a new key

Go to Account → API keys or open https://app.parseur.com/account/api-keys

Click Create new API key

Enter a Key name (e.g., “Zapier integration”). (You can rename later via Edit.)

Set Expiration in months. (Optional — cannot be changed later.)

Click Create

You’ll then see the secret key.

Important: This is the only time the full secret key is shown. Click Copy and store it securely (password manager/secret vault). If lost, create a new key.

Key expiration

If you set an expiration, you will receive an email 7 days before the key expires.

Keys are not auto-rotated. Create a new key and update integrations before the old one expires.

After expiry, requests using that key will fail.

Manage an existing key

Rename: Click Edit to change the key’s name (the secret is never shown again).

Disable / Enable: Temporarily block or restore usage.

Revoke (delete): Permanently invalidate the key (confirmation by typing the key name).

Who can create API keys?

Admins or single-user accounts: full access. Can create, rename, disable, and revoke keys.

Editors: can view legacy keys only; cannot create, view new keys, or revoke.

Restricted users and Viewers: no access.

If you need a key and aren’t an Admin, contact your account administrator.

Lost your API key?

Keys are not recoverable. Parseur stores only a hash (like passwords), so support cannot reveal the original value. Create a new key and update your integrations.

Legacy API keys

Accounts created before 2025-08-18 have a legacy key created at signup:

Legacy keys appear on the page in full and are labeled Legacy.

We’re not deprecating them, but they’re not recommended for new integrations.

For better security, create a new key and update your integrations. New keys are shown once at creation, reducing exposure risk.

Accounts created on or after 2025-08-18 do not get a key by default.

Best practices

Use one key per integration and name it clearly.

Store keys in a secret manager; never in client-side code or URLs.

Rotate keys if exposed; revoke keys you no longer use.

Always use HTTPS and avoid logging secrets.

What are API keys used for?#

Open the API keys page#

Create a new key#

Key expiration#

Manage an existing key#

Who can create API keys?#

Lost your API key?#

Legacy API keys#

Best practices#

What are API keys used for?

Open the API keys page

Create a new key

Key expiration

Manage an existing key

Who can create API keys?

Lost your API key?

Legacy API keys

Best practices