Frequently Asked Questions

Frequently Asked Questions

1. How does my workflow change if I use the VAN API Proxy?
   Answer: All you have to do is swap the host name and add the X-MIGVID request header to your VAN API
   requests. Note that the Proxy applies a rate limit of 100 requests per minute per credential. 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.
2. What will be different in my experience using the VAN API Proxy?
   Answer: We check that your request carries a Basic Authorization header and a valid X-MIGVID header, and return an error before the request reaches VAN if either is missing or malformed. We do not validate the body of your request. Please contact us if you have any questions!
3. Is the VAN API Proxy 1:1 with the VAN API?
   Answer: Every VAN /v4 endpoint is available through the Proxy, and responses are passed through with minimal changes. Two exceptions: a bulk-import request may be accepted for deferred forwarding and answered with 204 and an X-MIG-BulkImport: Saved header, and Location response headers are rewritten to point at the Proxy.
4. Can I use the VAN API Proxy when setting up my VAN integration with a Sandbox key?
   Answer: Yes, the VAN Proxy can be used as part of the testing process when setting up a new integration to VAN. You can use the Proxy's url and then follow VAN's setup process as normal.
5. How will I know if there’s downtime with the VAN API Proxy?
   Answer: We have a status page!
6. How can I get support for the VAN API Proxy?
   Answer: Please contact at DDx API Support at: [email protected].