API v2 Migration FAQ

This page answers the most common questions about migrating from legacy Fourthline API integrations to API v2.

If you're getting started, read the July Release Notes first. For implementation details, refer to the API Reference and the Migration Guide.

If you cannot find the answer you're looking for, contact your Fourthline customer success manager.

General FAQ

Do I need to migrate if my current integration is working?

Yes. 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.

What happens if we miss our migration deadline?

After your migration deadline, requests sent through legacy API endpoints will no longer be processed.

Migration is required to avoid service interruptions.

Why is Fourthline introducing API v2?

API v2 replaces product-specific integrations with a single integration model across supported Fourthline products.

This simplifies implementation, makes it easier to adopt additional products, and enables future platform enhancements to be delivered through a consistent framework.

What changes after migrating to API v2?

Migration changes how you integrate with the Fourthline platform, and does not change how verification checks are performed.

Migration FAQ

What are the prerequisites before starting migration?

Before starting migration:

Review the migration documentation.
Confirm your migration timeline with Fourthline.
Ensure you have a test environment available to validate API responses. Fourthline will configure your API v2 workflows in the Sandbox environment for testing.

Can we test API v2 before going live?

Yes. You can test API v2 in two ways:

Hub test workflow: Create a test case in Hub using the preconfigured API v2 workflows, then retrieve the results using the Status and Reports endpoints.
Direct API testing: Fourthline can replicate your existing workflow configuration in API v2, allowing you to validate your end-to-end integration in Sandbox using the API Reference.

Can API v1 and API v2 run in parallel?

Yes. API v1 and API v2 can coexist until your communicated migration deadline. You can continue using some workflows on API v1 while migrating others to API v2 without requiring an immediate cutover.

What happens to my existing workflows and configurations?

Your existing integrations and workflow configurations continue to operate until your as per your migration deadline.

After your migration deadline, you can no longer create new clients or verifications through legacy API endpoints.

What happens to historical data and reports?

Migration is backwards compatible.

Existing dashboards and reports continue to be available.
Clients and verifications processed through legacy integrations remain accessible in the Case Review Portal and Hub for auditing purposes.

What does the migration process look like?

Migration consists of four phases:

Preparation
Sandbox testing
Production readiness
Go-live

Fourthline supports you throughout each phase.

How much engineering effort should be expected?

Based on previous migrations, the engineering implementation effort typically takes about one week.

Overall project timelines vary depending on planning, testing, and internal change management.

What technical changes are typically required?

Depending on your current implementation, migration may require:

Updating API endpoints
Updating webhook handling
Updating status retrieval
Updating reporting endpoints
Configuring workflows

Will there be downtime during migration?

You validate your API v2 integration in Sandbox before deploying to Production. Production traffic is migrated only after successful validation, which should lead to no downtime.

Are webhook notifications changing?

Yes. API v2 introduces a unified webhook model.

Instead of configuring separate callback URLs for different products, all webhook notifications for the same workflow are sent to a single callback URL.

By the end of Q3 2026, you'll also be able to manage webhook callback URLs directly in Hub.

Commercial FAQ

Will Fourthline help us migrate?

Yes. Fourthline supports migration planning, Sandbox setup, implementation guidance, production readiness, and go-live coordination throughout the migration.

Are there any compliance or security implications?

No. API v2 does not introduce breaking compliance or security changes.

GDPR, personal data handling, data retention, and anonymization policies remain unchanged, where applicable.

Integration FAQ

Will verification outcomes remain consistent?

Yes. API v2 changes the integration model, not the underlying verification logic.

Will the customer experience change?

No. API v2 does not change the customer experience.

Will our downstream integrations be affected?

You need to update downstream integrations that consume:

Webhook notifications: Configure a new API v2 webhook callback URL.
Status and Reports endpoints: Update your integration to support the API v2 response format.

Workflow status names and status codes remain unchanged.

Documentation FAQ

I'm using API v1. Is there a migration guide?

A dedicated migration guide is available for migrating from API v1 to API v2.

I'm using another legacy integration. What should I do?

Contact your Fourthline customer success manager. We'll help determine the appropriate migration approach.

Who can help us get started?

Your Fourthline customer success manager can help you:

Scope your migration.
Estimate implementation effort.
Answer technical questions.
Plan and coordinate migration.