Appearance
Changelog
Every change to the CabFare Connect APIs is listed here, newest first. See the Versioning Policy for what each type of change means for your integration.
Each entry uses these labels:
- Added: new endpoints, fields or values. Safe to ignore until you need them.
- Changed: behaviour or rules that changed without breaking existing integrations.
- Deprecated: still works, but will be removed in a future major version.
- Removed: no longer available.
- Breaking: requires changes to your integration.
- Documentation: fixes or improvements to the docs only. No API change.
Documentation update: 28 Sep 2026
No API change.
- Documentation moved from Archbee to this site. Page addresses are unchanged, and the old endpoint pages redirect to the new API reference pages.
- Error
detailexamples now display as formatted code. - Each endpoint group now has a short description.
0.5.0 update: 7 May 2026 (current)
An update to the 0.5.0 specification. The version number was not changed.
Added
- Payment Terminal API: optional
additionalDataon all six endpoints. - Payment Terminal API:
isSubsidyonPOST /payment/request. - Payment Terminal API:
paidAtandtransactionIdonPOST /print/receipt. - Payment Terminal API:
X-API-KEY-IDheader added to the security options.
Breaking
- CabFare Connect API:
vehiclePlateis now required onPOST /terminal/link/request.
Removed
- CabFare Connect API:
GET /v1/pingremoved. Use/v0.5.0/ping. - CabFare Connect API:
X-API-KEY-IDheader removed. UseX-API-KEYandX-API-SECRET.
Documentation
- Descriptions reformatted and personal contact details removed from the specification.
0.5.0: 16 Jul 2025
First published version of the CabFare Connect integration. It has three APIs:
| API | Hosted by | Endpoints |
|---|---|---|
| CabFare Connect API | CabFare | Taxi Meter, Payment Terminal and Testing endpoint groups |
| Payment Terminal API | Payment Terminal partner | 6 |
| Taxi Meter API | Taxi Meter partner | 4 |

