The Dataset Exchange API uses conventional HTTP response codes to indicate the success or failure of an API request.

Some 4xx errors from retrieval endpoints may indicate a dataset has not yet been processed. These requests should be tried again. 2xx responses indicate a successful request.

200: Success
202: Async load jobs 400: Invalid request body (e.g., missing Workspace Key) 401: Missing authentication, Invalid authentication, dataset not found try again 403: User’s permissions do not include the necessary claim 500: An error from the MIG API server

Error Examples

All error responses will have: type title status errors source and traceId. detail is not always returned (see examples below).

{
    "type": "https://tools.ietf.org/html/rfc9110#section-15.5.2",
    "title": "Missing Authorization Header and cookie",
    "status": 401,
    "detail": "Requests to this API must have a valid Authorization header OR cookie. The provided request was missing both.",
    "errors": {},
    "source": "web",
    "traceId": "00-59aa9881da835860bae81a9ac8ba0f0e-bf7dfa562c57ba6e-00"
}

400 Bad Request: Validation Errors forPOST /datasets will have a slightly different shape. These errors will not return details and will includetraceId

{
    "type": "https://tools.ietf.org/html/rfc9110#section-15.5.1",
    "title": "One or more validation errors occurred.",
    "status": 400,
    "errors": {
        "Schema.PrimaryKey": [
            "Schema Primary Key must be in schema properties"
        ]
    },
    "traceId": "00-59aa9881da835860bae81a9ac8ba0f0e-bf7dfa562c57ba6e-00",
    "source": "web"
}

Status Page

To find the operational status of the Dataset Exchange API, please check out our Movement Infrastructure Group Status Page.