VAN API Proxy Overview

The VAN API Proxy logs transaction details made to the VAN API and serves as an entry into DDx API infrastructure by facilitating the transfer of data through the proxy into VAN. We’ve made using the VAN Proxy as easy as possible – all you have to do is swap the host name and add the X-MIGVID request header to your VAN API requests.

👍

The VAN API Proxy supports all VAN API /v4 routes, and passes responses through with minimal changes. Bulk-import requests are the exception: the Proxy may accept one for deferred forwarding and answer 204 with an X-MIG-BulkImport: Saved header rather than returning VAN's response.

If the specific endpoint you’re sending data to in VAN already has webhook notifications configured, you will continue to receive those notifications from VAN.

To get set up you’ll need:

1. The X-MIGVID provided during in your onboarding email. Do you need an X-MIGVID? Reach out to us at [email protected].
2. Access to your application’s hostname configuration.
3. Your existing VAN API credential, sent as a Basic Authorization header. The Proxy requires Basic authentication — Bearer tokens are not accepted in production.