Errors & Troubleshooting

The MIG API v1 emits two types of errors: proxied VAN errors, and MIG API Proxy errors. Errors from MIG 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. MIG performs light validation on request properties to ensure we only send requests that can succeed. If the Proxy is unable to deliver a request to the VAN API you will receive an error message. You can find examples of MIG error messages below.

Error Examples

Invalid Authentication Header

{
"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"
}

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"
}