API & integrations
Open by design. REST across every resource, an events API your downstream systems can subscribe to over Socket.IO, and open standards in and out. Anything Greenbay shows you, you can pull back through the same API.
16:00. Your planning team publishes tomorrow's schedule. The depot needs it now.
Today, someone exports a spreadsheet, emails it across, and the controller re-keys it. If the schedule changes at 18:00, the depot finds out in the morning. And when finance asks for the same data three months later, someone exports it again, by hand, from a different tool.
Greenbay's API picks up the change, validates it against vehicles, allocations, and chargers, and pushes the update to every connected client over Socket.IO. Three months later, the same data is one REST call away, in JSON, CSV, or GTFS. The data is yours, and it stays that way.
Open standards in, open standards out. The data is yours.The data is yours
Every resource Greenbay shows you in the UI is readable through the same REST API: schedules, allocations, telemetry, charging sessions, plan-vs-actual analytics, audit history. Export to JSON, CSV, GTFS, or GTFS-RT on demand, scoped to your tenant. No extraction fees, no portal-only data, no proprietary formats holding it hostage. If you ever leave us, you leave with everything.
REST across every resource
Schedules, blocks, allocations, vehicles, depots, chargers, telemetry, operations, comparison, reports, history, plan, timetables, custom fields. Every resource the orchestration layer touches has a documented REST surface, with public OpenAPI specifications covering the partner-facing ingest endpoints.
Open standards in, open standards out
GTFS, GTFS-RT, TransXChange, VDV, SIRI, ITxPT, OCPP 1.6 / 2.0.1, REST, CSV. The standards your scheduling team already publishes are first-class on the way in, and first-class on the way out: republish a GTFS-RT feed from live state, hand a downstream maintenance system a CSV of the day's allocations, or feed a passenger app from the same API your dispatchers see.
Events API for downstream systems
Subscribe over Socket.IO and Greenbay streams typed events as state changes: schedule updates, allocation changes, battery state of charge, charger status, operational issues, optimisation progress. Scoped to your tenant, authenticated, ready to drive your maintenance, finance, or passenger-facing systems. Inbound, the same architecture absorbs telematics from any provider and OCPP charger events through API-key authenticated webhooks at hundreds of messages per second.
Audited, versioned, exportable
Every import, every API call, every schedule change is logged with the user or service identity behind it. Roll back to a prior schedule version, diff any two imports side by side, and export the full audit trail whenever compliance, finance, or legal asks. Your history is yours, too.
Where this fits
Feeds schedule data into the timeline, vehicle data into live operations, and charger protocols into charging intelligence. The data backbone of the orchestration layer.
Explore more
Every capability connects into one operational view.
Ready to see it in action?
Book a 30-minute walkthrough tailored to your depot setup. We'll show you how Greenbay connects your entire operation.
Request a demo