July Release Notes
This page highlights changes released in July 2026. For earlier release notes, see Archive.
Fourthline API v2 is now available
New
We've released Fourthline API v2, available starting August 3, 2026. API v2 replaces product-specific integrations with a unified framework for workflows, webhooks, statuses, and reporting across supported Fourthline products.
Action required
Legacy API endpoints will be retired in Q2 2027 (no later than May 3, 2027). Please confirm your migration timeline with your customer success manager before that date.
After your migration deadline, legacy API endpoints will no longer process requests. Refer to the Migration FAQ and the Migration Guide to start planning your migration.
Key milestones
| Milestone | Timing |
|---|---|
| API v2 becomes available | August 3, 2026 |
New capabilities are built for API v2 and may not be supported by legacy integrations | November 1, 2026 |
| Legacy API endpoints are retired | Q2 2027 (no later than May 3, 2027) |
For implementation guidance and answers to common questions, refer to the Migration FAQ.
Three key benefits
API v2 introduces a single, standardized framework for all current and future Fourthline products. This allows us to deliver new capabilities faster, reduce integration complexity, and provide a more consistent experience across the Fourthline platform.
Unified integration pattern
API v2 provides a single integration pattern across supported Fourthline products. Instead of maintaining separate APIs for each product, you use one framework to:
Modular workflows
Create workflows that combine products and capabilities for different customer journeys, risk profiles, and compliance requirements without building separate integrations.
Note
All Fourthline products are supported by API v2, except AML Screening and AML Monitoring, which use a separate API.
New capabilities
API v2 is the foundation for future platform enhancements, including:
- Self-service workflow configuration: Configure, test, and deploy workflows through Hub.
- Granular SDK journey controls: Customize verification journeys with field - and screen - level controls.
Migration plan
Migrating to API v2 consists of four phases:
| Phase | Description |
|---|---|
| Preparation | Review the API Reference and the Migration Guide, define and agree on the migration timeline. |
| Sandbox testing | Validate your API v2 integration in the Sandbox environment. |
| Production readiness | Deploy your validated API v2 integration to Production. |
| Go-live | Validate the production integration and migrate traffic to API v2. |
Note
Based on previous migrations, the engineering implementation effort typically takes about one week. Overall migration timelines vary depending on the complexity of your integration and project planning.
What you need to do
To complete your migration before the deadline:
- Review the Migration FAQ and assess your integration scope.
- Confirm your migration timeline with your Fourthline customer success manager.
- Schedule Sandbox validation with Fourthline.
- Complete implementation, testing, and go-live.
Throughout the process, Fourthline will prepare your Sandbox environment, support implementation and testing, replicate validated configurations to Production, and coordinate your production rollout.