univoozAPI
Errors

branch_not_connected

The branch has no primary connection to a fleet zone.

HTTP 422invalid_request_error

Univooz found the branch. The branch has no destination.

Why it happens

A connection to a zone is not sufficient. One connection must be the primary connection. A branch with two connections and no primary is in this condition.

If you deactivate the primary connection, Univooz does not select a new one. The branch has no destination until a person selects a new primary.

Why. Your orders must never move to a fleet that you did not select.

How to fix it

Open the branch in the dashboard and set a primary connection. Then check the result:

curl https://api.univooz.com/v1/branches \
  -H "Authorization: Bearer uv_live_YOUR_KEY"

routesTo shows the destination. routesTo: null means the error continues. connectedZones shows the zones you can select.

For one order only, you can also send zoneCode.

Example response

{
  "error": {
    "type": "invalid_request_error",
    "code": "branch_not_connected",
    "message": "Branch 'noerrebro' has no active connection to a fleet zone.",
    "param": "branch",
    "doc_url": "https://docs.univooz.com/errors/branch_not_connected",
    "request_id": "req_01KZCCF8ZH4M7XQ2VB9RSTNPKD"
  }
}

On this page