Open API keys
Sign in as an Admin and open Platform → API keys. This page shows your Account ID and the account's keys, with their names, Key IDs and creation dates.
Use a separate, clearly named key for each integration so you can identify and replace its credentials without changing unrelated integrations.
Create a key
Select New key.
Enter a Name that identifies the integration, such as “Network inventory sync”.
Select Create key.
In Your API key is ready, copy the Key ID and Secret to your integration's secure configuration or password manager.
Select Done after you have stored the secret.
The secret is shown only when a key is created or regenerated. You cannot retrieve it later from the key list. If you lose it, regenerate the secret and update the integration.
Connect the integration
Copy the Account ID from the bar above the key list. Depending on the integration's setup, you will need the Account ID, Key ID and Secret. These are different values: the key's name is only a label.
Use the page's API documentation link for API authentication instructions and request examples. Store the secret in the integration's credential settings, not in documents, screenshots, chat messages or source control.
After configuration, test the integration's authentication and intended operation. If your account uses IP restrictions, its outbound address must also be allowed.
Find, copy and rename a key
Use Search keys to filter by name or Key ID.
Use the copy control beside a Key ID to copy its full value; the table may show a shortened version.
Select a key's name to rename it. Press Enter or move focus away to save, or Escape to cancel.
Renaming changes the label. It does not generate a new Key ID or reveal the secret. Administrators can manage the account's keys, but saved secrets are not available for later viewing.
Regenerate a secret
Find the key and choose Regenerate secret from its actions.
Read the confirmation and confirm regeneration when you are ready to update the integration.
Copy the replacement secret from Your API key is ready before closing it.
Replace the old secret everywhere that key is used, then test the integration again.
The Key ID stays the same. The old secret is replaced and can no longer be used for new authentication. Coordinate the change with whoever operates the integration so it is not left using the old value.
If you need to prepare a replacement before switching an integration, create a separate key, configure and test it, then remove the old key once it is no longer in use.
Delete a key
Choose Delete key from the key's actions and confirm only when it is no longer needed. Deletion cannot be undone. Integrations still using that key will no longer be able to authenticate with it.
If a key or secret was exposed, replace the affected credentials promptly and update every integration that used them.
Troubleshoot authentication
Check that you copied the correct Account ID, full Key ID, and current Secret, without extra spaces. A renamed key still uses its existing credentials; a regenerated key requires its new secret.
If those values are correct, check the integration's account access and your account's IP restrictions. Use the API documentation for the authentication flow rather than placing the secret directly into an arbitrary request header.