Skip to main content
Use the uatu console to manage your organization’s API keys and members from one place.

Open the console

Go to console.uatu.dev

​
Create an API key

1

Sign in

Open console.uatu.dev and sign in to your organization.
2

Open API keys

The API keys page lists your organization’s keys, including their status, creator, creation date, and last-used time.
3

Create a key

Give the key a descriptive name, such as checkout-production or quotes-staging. You can also set an optional expiration date; a key without one does not expire automatically.
4

Copy and store it

Keys start with uatu_live_. Copy the new key directly into your secret manager or deployment environment.
The complete key is shown only once. The console stores a hash and cannot reveal the value later. If you lose it, revoke the key and create a new one.

​
Authenticate a request

Load the key from an environment variable instead of placing it directly in source code:
Send it as a bearer token when requesting a quote:

​
Which endpoints need a key?

Creating an executable quote requires an API key. The catalogue is public. Public catalogue requests let you discover chains, tokens, DEXes, and pools before signing up.

​
Rotate or revoke a key

Rotate a key without interrupting traffic:
1

Create a replacement

Give the replacement a name that identifies the same service and environment.
2

Deploy the replacement

Update your secret manager or deployment environment and verify that requests are using the new key.
3

Check the old key

Wait until the old key’s Last used value shows that traffic has moved. Allow at least one minute for reporting to catch up.
4

Revoke the old key

Revocation takes effect immediately. A revoked key remains in the console for audit history but can no longer authenticate requests.

​
Keep keys safe

  • Keep keys in server-side secret storage. Anything in a browser bundle or mobile application can be extracted.
  • Use a separate key for each service and environment to limit the impact of a leak and make rotation or revocation more precise.
  • Set an expiration date when a key is only needed temporarily.
  • Revoke keys you no longer recognize or use.
  • Never commit a key to version control or include it in logs and error messages.