bitlync Docs

Concepts

Errors

Branch on the stable code.

Mechanism

The codes on this page are the codes that exist: 401 auth, 403 tenant, 404 unknown tenant, 409 routing_msp_owned, 422 validation (and request_invalid on a bad sandbox reset), 429 plus Retry-After, 501 unsupported, 500 internal_error.

What the caller sees

The body is code, message, and doc_url. details is optional.

error body
HTTP 422
{
  "code": "validation",
  "message": "The request did not validate.",
  "doc_url": "https://docs.bitlync.com/concepts/errors/"
}

500 is internal_error. 501 is unsupported.

409 routing_msp_owned. The message is "The MSP sets alert routing for this tenant in Connect. Nothing was saved."

Billing catalog checks return 422 request_invalid. The sandbox messages are "How often you report must be Daily or Monthly.", "How you bill must be Latest count, Count on a set day, Peak this month, or Average.", and "Two billing services use the key 'same-id'." for a repeated key.

Alert CSV import with no name column: "The CSV needs a name column." An Alerts or Billing upload is at most 2 MB. An alert write that is refused returns "Reload the page and try again."

MSP configure uses "Reload the page and try again." and "Too many saves. Wait a minute and try again." When the stack mandates Subtype, the message is "ConnectWise requires Subtype on {board}."

On the API, a repeated billing service key is "Two billing services use the key 'same-id'." In the console Add as service flow, a duplicate report id says "Two billing services use the report id {id}." report_id is not a public API field.

Health, incidents, and audit are listed reads on Reference, not a new UI.