Introduction
API keys act as secure credentials that let your external apps (CRMs, forms, back-office tools) talk to RecordsKeeper.AI. Each key is isolated, so you can enable, pause, or revoke access without affecting other integrations. This guide walks you through the API Keys area and the full creation flow.
Main body
Accessing the API Keys area
In the left navigation, open Widgets & Integration.
Choose API & Webhook Integration and switch to the API Keys tab.
You’ll land on a clean list of keys with columns for Name, masked API Key, Last Used, Created On, Last Updated On, and Actions. Use the Search bar to find keys quickly, sort by any column, and view more records via pagination.
Creating a new API key
Click Create API Key (top-right).
In the Create API Key modal, fill in:
API key name - Choose a precise label like “HubSpot Sync – Prod”.
Description - Add context so teammates know what this key powers.
Expire Date (Optional) - Set an end date if access is temporary.
Select Create API Key.
Saving the secret (shown once)
After creation, an API Key Created Successfully dialog appears with the secret value. This is the only time the full secret is visible. Use Copy Secret Key or Download Key and store it in a secure vault (e.g., a secrets manager).
If you misplace it later, create a new key, update your app, and then disable or delete the old one.
Managing existing keys
From the keys list, you can:
Enable/Disable a key using the toggle in Actions to instantly allow or block access.
Delete a key using the trash icon when an integration is retired.
Monitor Last Used to confirm activity and identify stale credentials.
Review Last Updated On for quick auditing of recent changes.
This lets you rotate credentials safely, isolate environments (dev/stage/prod), and keep integrations running without disruption.
Things to remember
Create one key per integration (and per environment) to isolate risk.
Rotate keys on a schedule: add a new key, update your app, then disable/delete the old one.
Always store secrets securely (vaults or environment variables - not in code, emails, or chat).
Use Expire Date for contractors, pilots, or short-term projects.
Conclusion
API keys give you a simple, controlled way to connect third-party tools to RecordsKeeper.AI. Generate a clearly named key, save the secret securely when it’s shown, and rely on the list view to monitor usage, toggle access, and retire keys as your integrations evolve.