Get an API key
Sign up in the Across integrator portal, create a key, and make your first call.
Every Across API call needs an API key. You create keys yourself in the Across integrator portal, in a few minutes, and come back here to integrate.
Sign up
Go to integrator.portal.across.to and choose Sign up.
Create your organization and first integration
The portal asks for two names:
- Organization name: your business or team.
- Integration name: the app you are building, for example "Wallet App". Everything requested with an integration's keys is attributed to that integration. You can add more integrations later, one per app.
Create a key
Open API keys and choose New key. Add an optional label, pick an expiration, and choose Create key.
Copy the key now. It is shown once and cannot be retrieved later. Store it in your secrets manager and only use it server-side.
Make your first call
Send the key as a Bearer token on every request:
Authorization: Bearer YOUR_API_KEYGET /v1/capabilities is the quickest way to check it works:
curl -H "Authorization: Bearer $ACROSS_API_KEY" \
"https://api.across.to/v1/capabilities?originChainId=42161&destinationChainId=8453&include=tokens"A 401 means the key is missing, wrong, revoked or expired.
Then continue with the Quickstart.
What your key can do
| Feature | How to get it |
|---|---|
| Quotes, executions and transfer tracking | Included with every key |
| Webhooks | Set them up yourself in the portal, under Webhooks |
| App fees | Contact Across to activate them. The portal's App fees tab then shows your maximum |
| Minimum-input quotes | Contact Across to activate them |
Managing keys
- Rotate issues a new secret for the key. The old secret stops working immediately.
- Revoke stops the key immediately. This cannot be undone.
- Expiration is fixed when you create the key. The portal flags keys that expire within 7 days.
- Keys belong to one integration. Use separate keys per service or environment, so you can rotate one without touching the others.
- Invite teammates under Members.
Keys from the portal work against production, https://api.across.to.
The Deprecated APIs identify you with an integrator ID
instead, issued through the registration form.