Error Codes and Meanings

standard http response codes cabfare connect uses standard http status codes to indicate the outcome of every request the table below defines each code, its meaning in the context of cabfare connect, and the most common causes code meaning common causes 200 ok request successful, response body contains data ping responses, subsidy card validation, trip end with subsidy processing 202 accepted request accepted with a notable condition trip start where driver subsidy scheme status is not valid; logout processed with issues 204 no content request accepted successfully, no response body driver logout success, link request accepted, trip end without subsidy processing 400 bad request malformed or invalid request payload missing required fields, invalid enum values, incorrect data types 401 unauthorized missing or invalid credentials missing or incorrect x api key or x api secret ; using sandbox credentials against production or vice versa 403 forbidden authenticated but operation not permitted driver or vehicle not authorised for subsidy scheme trips; subsidy scheme function attempted when driver status disallows it 404 not found referenced resource not found unknown device id in current context; driver not currently logged in when calling session dependent endpoints 409 conflict active session already exists duplicate tripid submitted to /meter/trip/start ; existing active trip for vehicle 410 gone resource no longer available payment cancellation attempted on a transaction that has already been completed 500 server error internal cabfare connect error contact support\@cabfare com mailto\ support\@cabfare com error response format for 4xx responses cabfare connect returns a structured error body inspect the detail array for specific field level errors { "status" 400, "error" "bad request", "detail" \[ { "field" "driverid", "message" "must not be blank" } ] } subsidy scheme specific status codes in addition to standard http codes, cabfare connect returns subsidy scheme specific status values within response bodies status value context meaning mptp driver invalid driver login response driver is not registered or not currently permitted to provide subsidy scheme trips iseligible true subsidy card validation response member card is valid and has a positive balance iseligible false subsidy card validation response member card is invalid, expired, or has no remaining balance issubsidycalculationmatching false trip end response cabfare connect subsidy calculation does not match the taxi meter's submitted calculation — use cabfare connect returned values as source of truth link success link response device link established successfully link failure link response device link failed — devices continue in unlinked mode