Request parameters

Request headers

Response 204 No Content

Delete successful

Response 401 Unauthorized

This response indicates that request lacks valid authentication credentials. Access token might not been provided, issued by the wrong issuer, does not have required scopes or request headers were malformed.

{
    "error": {
        "code": "HeaderNotFound",
        "message": "Header Authorization was not found in the request. Access denied."
    }
}

Response 404 Not Found

Requested export is not available.

{
    "error": {
        "code": "ExportNotFound",
        "message": "Requested export is not available."
    }
}

Response 422 Unprocessable Entity

Invalid or inexistent Id. Also occurs on exports that are in progress.

{
    "error": {
        "code": "InvalidMeshExportRequest",
        "message": "Cannot delete exported job.",
        "details": [{
            "code": "InvalidParameter",
            "message": "id is invalid.",
            "target": "id"
        }]
    }
}

Response 429 Too many requests

This response indicates that the user has sent too many requests in a given amount of time.

{
    "error": {
        "code": "TooManyRequests",
        "message": "More requests were received than the subscription rate-limit allows."
    }
}

Error

Contains error information and an optional array of more specific errors.

Error Details

Contains error information.

Error Response

Gives details for an error that occurred while handling the request. Note that clients MUST NOT assume that every failed request will produce an object of this schema, or that all of the properties in the response will be non-null, as the error may have prevented this response from being constructed.