API Keys

Why You Would Use This

API keys authenticate requests to the HookBridge API. You can issue separate keys for different services so rotation and revocation are low-risk.

Console Workflow

1. Open API Keys.
2. Click Create API Key and add a label.
3. Copy the key immediately and store it in your secret manager.
4. Review key usage metadata in the list.
5. Delete keys that are no longer required.

API Workflow

# List API keys
curl https://api.hookbridge.io/v1/api-keys \
  -H "Authorization: Bearer YOUR_API_KEY"

# Create API key
curl -X POST https://api.hookbridge.io/v1/api-keys \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"label":"worker-service"}'

# Delete API key
curl -X DELETE https://api.hookbridge.io/v1/api-keys/YOUR_KEY_ID \
  -H "Authorization: Bearer YOUR_API_KEY"

Safe Handling

• Treat keys like passwords.
• Never store keys in source control or client-side code.
• Use one key per service so compromised keys can be revoked without broad impact.