Summarize this article with
Over the past few years, Fingerprint’s device intelligence has evolved rapidly — we’ve added new signals and given our customers more ways to detect and prevent fraud. As our platform has expanded, so has our API to support more endpoints, payloads, and configurations.
That flexibility has supported our growth, but it also made integrations more complex. Now, we are taking the opportunity to simplify, make formats more consistent, and remove legacy fields that are no longer needed.
As a result, we are excited to announce the launch of API v4. It unifies data formats across all core components, including the Server API, Webhooks, Sealed Client Results, and JavaScript Agent, so everything now speaks the same language, creating a simpler, faster, and more predictable developer experience.
What’s new in API v4
We’ve rebuilt the Server API with a focus on simplicity and consistency. The API consists of:
-
Just two core endpoints, designed for faster, simpler integrations.
/v4/events/:event_id— fetch or update a single event/v4/events— search, filter, and analyze fraud
-
Unified formats across Server API, Webhooks, and Sealed Client Results. Same structure everywhere, easier to read, and faster to implement.
-
Lighter, faster payloads. We removed duplicated and outdated fields, cutting down payload size.
-
Modern authentication. A single, standard
Authorization: Bearerscheme for all requests. -
Clearer errors and responses. Get full, user-friendly messages that make troubleshooting faster.
JavaScript Agent v4 enhancements
Released alongside API v4, the updated JavaScript Agent brings major improvements:
- Suspect Score in get() responses. Quickly access Suspect Score for testing or demonstrating the power of Smart Signals.
- Built-in Visitor ID caching. Supports the most common client-side patterns out of the box.
- Unified proxy and subdomain configuration. Simplified setup for proxy integrations and custom domains.
- Removal of outdated options. Deprecated parameters and legacy behaviors have been cleaned up for a streamlined API.
Why this matters for you
API v4 is designed to make your work easier from day one. Integrations are faster, with a simplified structure that means less time reading through documentation and more time building what matters. Because the format is consistent across the platform, adopting new features in the future won’t require major rework.
The new structure also reduces long-term maintenance. By streamlining fields and removing outdated quirks, you’ll spend less time troubleshooting edge cases or maintaining special configurations. And most importantly, API v4 sets you up for what’s next. The new foundation is built to support faster innovation, so you can more easily take advantage of new Fingerprint features the moment they’re released.
Migration timeline
- Available now: API v4 is live in production and applies to the Server API and JavaScript Agent. Mobile SDKs (iOS and Android) are not impacted at this time and continue to operate as usual.
- Migration period: The deprecation period will begin once all proxy and library integrations (both backend and frontend) are released. Full support will be provided for 12 months from that effective date.
- Recommendation: Plan your migration to take advantage of new features and maintain maximum accuracy.
- Libraries and SDKs: Support for API v4 in our server-side and client-side libraries is in progress, with releases planned for the first quarter of 2026.
Ready to migrate?
API v4 is available now for production use with the Server API and JavaScript Agent.
If you do not rely on our language-specific libraries or mobile SDKs, everything you need is already in place and you can start your migration today. Migrating early helps you take advantage of new features and enhancements as they are released, without being limited by legacy APIs.
We recommend beginning your migration as soon as your team is able to reduce long-term maintenance and maintain maximum accuracy.
