The Connect API uses conventional HTTP response codes to indicate the success or failure of an API request. In general, codes in the 2xx range indicate success, codes in the 4xx range indicate an error that failed given the information provided (e.g., a required parameter was omitted, user's credentials are invalid, etc.), and codes in the 5xx range indicate an error with the Connect API's servers (these are rare).

In addition to returning an appropriate HTTP code the body will also include a JSON formatted error object that provides more details about the specifics of the error. The error object will return the error as an array to indicate multiple errors (where present).

Attributes

correlationId

a unique identifier for this particular occurrence of the problem.

code

an application-specific error code, expressed as a string value.

title

a short, human-readable summary of the problem.

detail

a human-readable explanation specific to this occurrence of the problem.

source

an object containing references to the source of the error, optionally including any of the following members:

  • pointer the location to the object or attribute that the error relates to

  • parameter a string indicating which URI query parameter caused the error.

HTTP/1.1 400 Bad Request
Content-Type: application/json

{
  "type": "list",
  "correlationId": "bd1183d9-c9d8-11e7-909a-6789bfc80ac5",
  "data": [
    {
      "type": "error",
      "code": "parameter-not-supplied",
      "title": "Required parameter not supplied",
      "detail": "Institution ID  parameter is required.",
      "source": {
        "pointer": "connection/institution/id",
        "parameter": "id"
      }
    }
  ]
}

What’s Next

Get a breakdown of all the error codes that can be returned

Did this page help you?