Public API keys let approved integrations authenticate when they retrieve data from Unison. Create a separate key for each integration so you can rotate or revoke access without affecting other systems.
Create a Public API key
-
Open Settings > Data Configuration > API Keys.
-
Select Add API Key.
- Enter a Name and an optional Description.
- Set an Expiration, or select Never Expires when the credential should remain active until you revoke it.
- Select Create API Key.
- Copy the complete credential to your secure secret manager.
Use the credential
Send the complete credential as a bearer token in every API request.
Authorization: Bearer <public_api_credential>
Use the base URL for your Unison region:
- United States:
https://public-api.us.unison.totango.com - Europe:
https://public-api.unison.totango.com
Review existing credentials
Return to Settings > Data Configuration > API Keys to review the credentials created for your organization. The secret value is not displayed again.
Rotate a credential
- Create a new credential for the same integration.
- Update the integration to use the new value.
- Confirm that API requests succeed with the new credential.
- Revoke the old credential.
Revoke access
Revoke a credential when an integration is retired, a secret may have been exposed, or the owner no longer needs access. Requests that use the revoked credential will stop working.
FAQs
Can I view a secret again after I create it?
No. Create a replacement credential if the secret was not stored.
Should several integrations share one credential?
Use a separate credential for each integration. This gives you a clear owner and lets you rotate access independently.