Migrate from V1
A guide to help you migrate from V1 to V2 of the Verify API.
The V2 Prelude Verify API has a few key differences from the V1 API. This guide will help you understand the changes and update your integration accordingly.
Key Differences
- The
POST /v2/verification/checkendpoint doesn’t require a Verification ID. As a result you don’t need to keep track of the verification ID returned by thePOST /v2/verification/createendpoint reducing the overall complexity. - The
POST /v1/authentication/feedbackendpoint has now been moved to the Watch API. - Authentication is now done via an
Authorizationheader and a Bearer token instead of anX-API-Keyheader, and you no longer need to provide aCUSTOMER_UUIDheader field.
How to Migrate
Use the V2 quickstart guide to learn how to generate a V2 API key and migrate your integration to the V2 API. Your requests to Prelude will gracefully move to the new API and will normally appear on your dashboard without any further steps on your part.
If you need to do more complex things, you can refer to the V2 API reference for more details.
For better performance, reliability and fraud prevention, we also recommend to integrate our Frontend SDKs.
Contact Us
If you have any questions or need assistance, please contact us.
Migrate from V1
A guide to help you migrate from V1 to V2 of the Verify API.
The V2 Prelude Verify API has a few key differences from the V1 API. This guide will help you understand the changes and update your integration accordingly.
Key Differences
- The
POST /v2/verification/checkendpoint doesn’t require a Verification ID. As a result you don’t need to keep track of the verification ID returned by thePOST /v2/verification/createendpoint reducing the overall complexity. - The
POST /v1/authentication/feedbackendpoint has now been moved to the Watch API. - Authentication is now done via an
Authorizationheader and a Bearer token instead of anX-API-Keyheader, and you no longer need to provide aCUSTOMER_UUIDheader field.
How to Migrate
Use the V2 quickstart guide to learn how to generate a V2 API key and migrate your integration to the V2 API. Your requests to Prelude will gracefully move to the new API and will normally appear on your dashboard without any further steps on your part.
If you need to do more complex things, you can refer to the V2 API reference for more details.
For better performance, reliability and fraud prevention, we also recommend to integrate our Frontend SDKs.
Contact Us
If you have any questions or need assistance, please contact us.