Request IDs

Every answer of the API, errors included, carries a Request-Id header: req_ followed by 26 characters. An error also gives it in its body, as request_id:

{
  "error": {
    "type": "invalid_request_error",
    "code": "resource_missing",
    "message": "No such event: 'EVT-5a1f0c2e-3b7d-4e91-9c2a-1d6e8f4b7a30'.",
    "param": "id",
    "doc_url": "https://developer.masterconf.com/errors/codes#resource_missing",
    "request_id": "req_01JAZ5Q3X8M4K2N7P9R6T0V1W3"
  }
}

Log it

Keep the Request-Id in your logs with each call, at least for the calls that fail. It is the fastest way to find a request on the platform’s side.

Quote it to support

When you contact support about a call, give:

• its Request-Id;
• the time of the call;
• the id of the key you used. GET/v1/account gives it as api_key.id.

Never send the key itself: support never needs it.

When there is none

A 429 answered by the gateway’s rate limit has a request_id of null: the request never reached the API. See Rate limits.