Taxi Meter API

overview the taxi meter api defines the endpoints that the taxi meter partner must implement and host cabfare connect calls these endpoints to deliver real time inbound event notifications to the taxi meter system this api is the inbound communication path — cabfare connect calls your system implementation requirements your system must expose these endpoints to receive events from cabfare connect when your system receives an inbound request from cabfare connect it must return an immediate 200 ok or 204 no content response before processing the event validate that the x api key header in the inbound request matches your issued key handle the event and update your ui or internal state accordingly where possible response codes should be implemented as documented error response bodies are optional but recommended during development as they assist with troubleshooting endpoints method endpoint summary post /link/request receive a link mode request from cabfare connect post /mptp/member receive subsidy card read notification and member data from cabfare connect post /payment/complete receive payment outcome notification from cabfare connect post /driver/logout receive driver logout notification from cabfare connect endpoint details post /link/request — link mode request cabfare connect calls this endpoint to forward a link mode request to the taxi meter after receiving a link request from the payment terminal required fields taximeterid , driverid optional fields vehicleplate , paymentterminalconfiguration , clientids responses code meaning 200 ok link request accepted — return link success details 400 bad request malformed request 401 unauthorized invalid credentials 404 not found taxi meter or driver not found in current context the taxi meter must return a success or error response cabfare connect uses this response to determine what to send back to the payment terminal via /link/response post /mptp/member — subsidy card read notification cabfare connect calls this endpoint to deliver subsidy card validation results to the taxi meter following a card read or validation request required fields taximeterid , driverid , mptpmemberdata optional fields clientids , terminalfailure responses code meaning 204 no content notification received successfully 400 bad request malformed request 401 unauthorized invalid credentials 404 not found taxi meter or driver not found in current context the terminalfailure field indicates whether the notification is being sent because the payment terminal failed to read the card post /payment/complete — payment complete notification cabfare connect calls this endpoint to notify the taxi meter of the outcome of a card payment processed on the payment terminal required fields taximeterid , driverid , tripid , transactionid , paymentstatus , paymentdetails optional fields clientids responses code meaning 204 no content notification received successfully 400 bad request malformed request 401 unauthorized invalid credentials 404 not found taxi meter or driver not found in current context post /driver/logout — driver logout notification cabfare connect calls this endpoint to notify the taxi meter that the driver has logged out of the linked payment terminal the taxi meter must determine whether to also log the driver out or continue in unlinked mode required fields taximeterid , driverid , status optional fields clientids responses code meaning 204 no content notification received successfully 400 bad request malformed request 401 unauthorized invalid credentials 404 not found taxi meter or driver not found in current context important notes full endpoint schemas, request and response bodies, and error details are available in the interactive api reference imported from the openapi specification the base url for these endpoints is your own hosted url — cabfare connect will be provided your base url during the integration onboarding process