API Reference Overview

cabfare connect uses three separate api specifications that together define the complete integration understanding the relationship between these three apis and the direction of communication is essential before implementing individual endpoints the three apis cabfare connect api the central api hosted by cabfare both the taxi meter partner and the payment terminal partner call these endpoints to send events to cabfare connect, initiate actions, and request subsidy calculations this is the outbound communication path from your system to cabfare connect taxi meter api the endpoints your system must implement and host if you are a taxi meter partner cabfare connect calls these endpoints to deliver inbound event notifications to your taxi meter system — for example link requests, mptp member data, and payment confirmations payment terminal api the endpoints your system must implement and host if you are a payment terminal partner cabfare connect calls these endpoints to deliver inbound event notifications to your payment terminal system — for example card read requests, payment instructions, and driver logout notifications communication direction summary api hosted by called by direction cabfare connect api cabfare taxi meter and payment terminal partners outbound — your system calls cabfare taxi meter api taxi meter partner cabfare connect inbound — cabfare calls your system payment terminal api payment terminal partner cabfare connect inbound — cabfare calls your system which apis apply to you if you are a taxi meter partner you must call the cabfare connect api endpoints relevant to your persona implement and host the taxi meter api endpoints if you are a payment terminal partner you must call the cabfare connect api endpoints relevant to your persona implement and host the payment terminal api endpoints api versioning and base urls the current api version is v0 5 0 base urls are provided per environment and per location refer to the relevant location section for the base url applicable to your integration authentication all api calls in both directions use the same x api key and x api secret headers refer to the authentication and security page in core concepts for full details