At Safe, our users’ security and reliability are our highest priorities. Our mission has always been to provide the most trusted infrastructure for digital assets, which means protecting not only funds but also the way applications connect and interact with Safe smart accounts.
To uphold this standard, we will be retiring the public APIs on October 27, 2025. After this date, only access through authenticated endpoints will be supported. It will require an API Key that can be obtained via the Safe Dashboard.
Why this change matters for you
1. Keeping our users safe
Unauthenticated APIs allow open access to Safe services. This increases the risk of misuse, scraping, and unreliable service. By requiring authentication, we ensure that only verified developers and applications can access user-related data — enhancing security and reliability.
2. A safer ecosystem for everyone
Safe powers billions in value. Moving away from public endpoints reduces the attack surface and ensures stronger safeguards for the entire ecosystem. Security is not just a feature — it’s the foundation we all build on.
3. Reliability you can count on
With authenticated APIs, we can enforce fair usage, provide consistent throughput, and offer stronger monitoring. This means your applications — and your end-users — benefit from faster, more reliable performance.
Next steps for developers
Sign up on the Safe Dashboard to generate your API keys.
Review the guide to get setup with authenticated access.
Complete migration before October 27, 2025 to avoid any disruption.
We understand that changes like this can require effort on your side. Our team is here to support you every step of the way — if you have questions or need help migrating, please reach out via support@safe.global.