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.
EDIT: Unauthenticated APIs support will stay for a limit of 2rps.
While it was originally planned to retire all unauthenticated traffic, many of our users reached out to us expressing their genuine need to sign mission critical transactions with their bespoke setups for privacy reasons, and we want to support them, for this reason we set the limit to unauthenticated to 2rps. Organizations, corporations and businesses that build apps and require higher limits, have to migrate to authenticated APIs.
To uphold these standards, we will be significantly throttling the public APIs today October 27, 2025 i.e., 2 RPS. After today, only authenticated endpoints via the Safe Dashboard will be supported with a higher rate limit of upto 5 RPS per chain.
For teams that require a higher rate limits, we encourage you to get in touch with the Safe support team through intercom chat found at the bottom right of this page.
Why this change matters for you
1. Keeping our users safe
Unauthenticated, open APIs allow unrestricted 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 — protecting our users and their trust.
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. Together, we’ll make sure you & your users stay safe. — if you have questions or need help migrating, please reach out via support@safe.global.