Managing API Keys
The API Keys page lets you create, configure, and manage the keys your applications use to access the FourA API.
Viewing Your Keys
The API Keys page shows all keys you have access to:
- Personal keys you created directly.
- Organization keys if you're an org owner or admin.
- Team keys shared with you through team membership.
Each key displays its name, status (active/inactive), creation date, and the key prefix (first 12 characters).
Creating a Key
Click Create Key and fill in:
| Field | Required | Description |
|---|---|---|
| Name | Yes | A descriptive label (e.g., "production-scraper" or "staging-test") |
| Description | No | Notes about what this key is used for |
| Rate Limit | No | Per-key request limit |
| Organization | No | Assign the key to an org instead of your personal account |
The full API key is displayed only once after creation. Copy it immediately. Keys use the pk_live_ prefix and look like: pk_live_a1b2c3d4e5f6...
You'll receive an email confirmation when a new key is created.
Editing a Key
Click on a key to update its settings:
| Setting | Description |
|---|---|
| Name | Change the display name |
| Description | Add or update notes |
| Active/Inactive | Toggle the key on or off without deleting it |
| Rate Limit | Set a per-key request limit |
| IP Allowlist | Restrict the key to specific IP addresses |
| Expiry Date | Set an automatic expiration date |
Deactivating a key blocks all API requests that use it. Reactivate it at any time.
Regenerating a Key
If you suspect a key has been compromised, click Regenerate. This creates a new secret for the same key ID. The old secret stops working immediately. All other settings (name, permissions, org assignment) stay the same.
The new key is shown only once. Copy it before closing the dialog.
Deleting a Key
Click Delete to remove a key. By default, deletion deactivates the key (soft delete). You can permanently remove it from the confirmation dialog.
You'll receive an email notification when a key is deleted.
Organization Keys
Keys created under an organization are shared with org members based on their role:
- Owners and admins see and edit all org keys.
- Members see only keys assigned to teams they belong to.
Org keys are automatically added to the organization's default team on creation.
Key Permissions Through Teams
Teams control who can access which keys. Each team-key assignment has a permission level:
| Permission | View key | Edit key settings |
|---|---|---|
| read | Yes | No |
| write | Yes | Yes |
| admin | Yes | Yes |
Related
- Authentication: How API keys work with the API
- Organizations and Teams: Setting up shared access
- Dashboard Overview: All dashboard sections