Environments overview
| Region | API base URL | Dashboard URL | Chains | SLA | Webhook origin IP |
|---|---|---|---|---|---|
| Default - Europe | api.dfns.io | app.dfns.io | Mainnet Testnet | Yes | 35.181.116.68 |
| UAE | api.uae.dfns.io | app.uae.dfns.io | Mainnet Testnet | Yes | 40.172.249.100 |
| Deprecated Staging | api.dfns.ninja | app.dfns.ninja | Mainnet Testnet | No | 52.47.197.63 |
Regional hosting - Data residency
Dfns regions are segregated environments enabling you to choose where your data is processed.An organization and its wallets, keys, users, etc. live in a specific region. They cannot be accessed from another region or transferred to another region.
dfns.io) is hosted across multiple European AWS regions. When you use this region, your data are processed in Europe.
An alternative environment hosted in the UAE is available (uae.dfns.io). When you use this region, your data are processed exclusively in the UAE.
On-chain activity cannot be tied to a region as blockchains are decentralized by definition. When transactions data are broadcasted to a network they may be processed anywhere in the world, this is totally out of Dfns control.
Building API endpoint URLs
Throughout our documentation, assume that you should prepend the environment base URL in front of the API paths given. For example:GET /wallets/ should be interpreted as: GET https://api.dfns.io/wallets/
Whitelisting webhooks origin IPs
Our webhooks will always be originated from the same IP address (see table above). You can therefore use these if you want to whitelist Dfns IPs for filtering webhook delivery. Make sure you also verify that webhooks are properly signed by checking theDfns-Signature header as explained in the webhooks documentation.