Migrate to the EU console
Atmosvere now runs on EU infrastructure. New accounts and dashboards live in the
Developer Console (console.atmosvere.eu), with
API traffic going to https://api.atmosvere.eu and hosted challenge / blocked
pages on https://pages.atmosvere.eu.
If you still use the legacy Trusted Accounts setup (api.trustedaccounts.org,
DigitalOcean Spaces challenge/blocked pages, and the older admin dashboard), you
can move to the EU console in one of two ways. The legacy path
remains available only until 31 October 2026; after that date, legacy
endpoints and hosting for non-migrated projects will be shut down. Updated
sub-processor details are in our DPA and
Privacy Policy.
Option 1: Keep your account (ask us to migrate)
Write to support and ask us to migrate your account and data to the new console.
Email contact@trustedaccounts.org and include:
- The email address of your existing account
- That you want your account and data migrated to
console.atmosvere.eu
After migration, point your integration at the EU API, frontend SDK, and hosted pages (see below) and use the Developer Console going forward.
Option 2: Start fresh
You can also create a new project in the Developer Console, copy new API keys, and switch your integration without a data migration.
This is often simplest if you do not need historical dashboard data.
After your new setup is live and working, cancel your old subscription on the legacy dashboard so you are not billed twice. Keep the old subscription active only until you have confirmed EU API requests are succeeding (see below).
Update your integration URLs
In either case, update the server API, and (if you use them) the frontend SDK and hosted challenge / blocked pages:
| Before | After | |
|---|---|---|
| API | https://api.trustedaccounts.org | https://api.atmosvere.eu |
| Frontend SDK | https://api.trustedaccounts.org/js-sdk.js | https://sdk.atmosvere.eu/js-sdk.js |
| Challenge page | https://challenge-page.fra1.digitaloceanspaces.com/challenge.html | https://pages.atmosvere.eu/challenge.html |
| Blocked page | https://blocked-page.fra1.digitaloceanspaces.com/blocked.html | https://pages.atmosvere.eu/blocked.html |
Server-side API
For example, the check-request endpoint becomes:
https://api.atmosvere.eu/api/v1/check-request
Frontend SDK
If you load the browser SDK, update the script src:
<script
async
src="https://sdk.atmosvere.eu/js-sdk.js"
onload="new TrustedTraffic({publishableKey:'YOUR_PUBLISHABLE_KEY'}).init()">
</script>
Challenge and blocked pages
If your integration redirects visitors on challenge or block decisions, update the hosted page base URLs:
https://pages.atmosvere.eu/challenge.html
https://pages.atmosvere.eu/blocked.html
Keep the same query params as today (trusted_id, publishable_key,
redirect_url). See Protection integration
for the full redirect example.
If you override these URLs per project in the dashboard, update them there as well (or clear the override so the EU defaults apply).
Then deploy the change and confirm your requests are working: check that your
server calls to https://api.atmosvere.eu succeed (HTTP 2xx and a decision in the
response), and that a challenge / block redirect lands on
pages.atmosvere.eu (not the old DigitalOcean Spaces URLs).
Aggregated dashboards (for example Bot Protection metrics) can take up to 24 hours to populate — do not wait on those to decide whether the switch worked.
If anything is unclear during the switch, see Get help or
email contact@trustedaccounts.org.