Error Codes and Meanings

View as Markdown

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

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