Errors & Troubleshooting

The VAN API Proxy emits two types of errors: proxied VAN errors, and API Proxy errors. Errors from DDx API code follow the proposed problem details standard, with an additional “source” property to help identify the component.

VAN errors follow the scheme outlined in the VAN API error documentation. The Proxy checks that your request carries a Basic Authorization header and a valid X-MIGVID header, and rejects it before it reaches VAN if either is missing or malformed. It does not validate the body of your request. If the Proxy is unable to deliver a request to the VAN API you will receive an error message. You can find examples of DDx API error messages below.

In production, a request with no Authorization header at all may be rejected at the load balancer with a bare 403 and no response body, before it reaches the Proxy and the 401 below.

Error Examples

Missing or Invalid Authorization Header

A non-Basic scheme — a Bearer token, for example — produces this same error.

{
"type": "https://tools.ietf.org/html/rfc9110#section-15.5.2",
"title": "Missing Authorization Header",
"status": 401,
"detail": "Requests to this API must have a valid Authorization header",
"errors": {},
"source": "proxy"
}

Missing X-MIGVID Header

{
"type": "https://tools.ietf.org/html/rfc9110#section-15.5.1",
"title": "Missing X-MIGVID Header",
"status": 400,
"detail": "Requests to this API must have a valid X-MIGVID header",
"errors": {},
"source": "proxy"
}

Invalid Header

{
"type": "https://tools.ietf.org/html/rfc9110#section-15.5.1",
"title": "Invalid X-MIGVID Header",
"status": 400,
"detail": "Requests to this API must have a valid X-MIGVID header",
"errors": {},
"source": "proxy"
}