Skip to content

V1 error codes in V2

V1 returned 200 OK even for application errors: you had to read <Result> and, on failure, <ResultError>. In V2, check the HTTP status first. If the response includes errorCode, use it to distinguish the specific cause: it is a string that may contain a number or a text identifier, and it varies by endpoint. This table covers common migration cases, not an automatic code-by-code conversion; also consult each endpoint’s errors.

V1 ResultErrorMeaningAPI V2
Result=1Processed successfully200 / 201
100000, 100001, 100003, 100004Parameter unexpected, missing, required or invalidUsually 400. Field validation may return invalid-request-data with field; an unprocessable body returns invalid-request-content. Other endpoints use their own codes.
100018Incorrect login/passwordOn POST /getapikey: 403 “Invalid credentials…”. On any other call: 401 “Invalid or missing API key.”, or “Credentials have changed…” when the user’s password changed
100021The call exceeded the maximum execution time502 / 503. Read 4.6 before retrying anything that creates
100022Item not found404, or 400 with the endpoint’s own errorCode — 169 in budgets, 238 in orders, 717 in tickets
100023, 100024Could not connect to flowww502 / 503 — see 4.6
108000, 108001Duplicate login or email409 {"message":"A client with those details already exists.","errorCode":"409"} — only when you send ClientForceEmail: 0 (see command 08)
108002, 108003Could not create the client / limit exceeded400 with the endpoint’s own errorCode (381 limit reached)
119000Could not create the ticket400 on POST /invoice: 495 invalid ClientID, 502 client missing required fields, 50 / 142 cash desk (see command 19)
119001Payments do not add up to the invoice total409 49 when closing the ticket (PATCH /invoice/{id}), not when adding the payment lines
166, 169, 618, 619, 620Invalid budget data / product off tariff / budget, client or clinic id not found400 166 or 169 in the budget calls (see command 40)
108004Order not accepted, or not enough stockNot checked on accept. On ship, 400 no-stock only when nothing can be shipped
108010, 108012Order already shipped / too many unitsV2 does not check this: read the order before accepting or shipping (command 102 and command 103)
108011Page out of rangeNo longer applies: GET /order is not paged

V2 failures without a single V1 equivalent

Section titled “V2 failures without a single V1 equivalent”

These cases may be new in V2 or may have been handled differently by each V1 command. Do not assume they had no ResultError: check your integration’s behavior and the V2 endpoint response.

SituationAPI V2
Client not found — including when it was merged into another one404 {"errorCode":"404"}. See 4.7
The user lacks the endpoint’s permission400 {"errorCode":"15"} — not a 403. (436, also a 400, means the clinic is suspended)
The clinic does not exist, or clinicID is not numeric400 {"errorCode":"714"} / 400 invalid-clinicid
Wrong system key403 “Invalid systemkey…” at /getapikey — the system key is bound to the API key from then on
Too many concurrent requests429. Retry after Retry-After
Monthly quota exhausted429. Do not retry until the monthly reset — see 4.8
Temporary problem502 / 503. See 4.6 before retrying a call that creates something