Skip to main content

API Keys

The API Keys section lets you securely manage your API access, enabling you to generate, edit, and control up to 5 API keys.


API Keys page for managing, generating, and editing API keys securely

Key Features

  • Manage Multiple Keys: Generate and manage up to 5 API keys.
  • Assign Descriptive Names: Assign meaningful names to your API keys to easily distinguish their purposes, such as testing or production environments.
  • Manage Key Status:
    • Active: Keys currently in use and functional. Newly generated keys are active by default.
    • Blocked: Keys that have been disabled for security or organizational reasons.
  • Edit Keys: Quickly edit key details.

How to Use

1️⃣ Generate New Keys: Click the New API Key button to create a new key (if fewer than 5 keys exist), or use the one automatically generated upon registration.

2️⃣ Copy Key: Click the Copy icon next to a key to quickly copy it to your clipboard.

Details view of an API key, showing its name, status, copy and edit button

3️⃣ Use the Key: Use your API key to authorize your requests.

4️⃣ Edit Existing Keys: Use the Edit button to rename or block a key as needed.

Edit button to rename or block an API key

Modal window for editing an API key, including renaming or blocking options

Security Notes
  • Keep your API keys secure – avoid sharing them publicly or exposing them in client-side code.
  • Blocking is permanent – once an API key is blocked, it cannot be unblocked through the dashboard. Create a new key or contact support to restore access.

Webhook Signature

Below the API keys table you'll find the Webhook Signature section. This secret is used to sign every webhook request from the /async endpoint, so you can verify the callback genuinely came from PDFBolt.

  • Click the eye icon to show or hide the secret.
  • Click the copy icon to copy it to your clipboard.

Webhook Signature section showing the secret key with show/hide and copy options

For details on how to verify webhook signatures in your code, see Webhook Signature Verification.