Error handling for the Invoca APIs

Understand the JSON error responses returned by the Invoca APIs, including 404 not found, 403 validation failures, and 500 service errors with unique handles.

Common RingPool errors:

Not found – 404:

https://invoca.net/api/2014­-01-­01/<network_id>/advertisers/1/advertiser_campaigns/100/ring_pools/123.json

{
  "errors": {
    "invalid_data": "Could not find RingPool 123 for advertiser campaign 100 and advertiser 1",
    "class": "RecordNotFound"
  }
}

Validation failed – 403 – Body contains a json with validation errors for each field:

{
  "errors": {
    "pool_type": [
      "can't be blank"
    ],
    "destination_type": [
      "can't be blank"
    ],
    "name": [
      "can't be blank"
    ]
  }
}

Service error – 500 – Body contains a json Error with a unique handle (to use as a cross‐reference with Invoca):

{
  "errors": {
    "invalid_data": "refer to error handle 1228118400",
    "class": "InternalServiceError"
  }
}