Export and consolidate pay-station (kiosk/meter) transaction data across vendors using Flowbird WebOffice HUB
domain: doc-weboffice.eu.flowbird.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Request a Flowbird API certificate (access is certificate-gated, not open self-serve) scoped to the data you need from WebOffice HUB
Use the Export tab / Live Data Import & Export API to pull pay-station purchase transactions into WebOffice for unified cross-vendor analysis
Alternatively, use the Live Data Import service to push a third-party vendor's purchases into WebOffice as an XML-based purchase blob so they appear in WebOffice's own Analysis tools
Use the separate Public Purchase Prerequisite API (Swagger spec provided by Flowbird on request) to update meter tariffs in real time without pushing a full config file
Treat this as a distinct product surface from Flowbird's mobile pay-by-plate app integration, since this one addresses the physical pay-station/kiosk side and cross-vendor data consolidation
Known gotchas
PAYMENT- and GOVERNMENT-ADJACENT: pay stations are typically municipal on-street/off-street meter infrastructure, so exported data likely includes regulated public payment data
Access is via a Flowbird-issued certificate with scoped permissions, and the Swagger/API spec is only handed out on request - don't assume endpoint names without confirming the certificate-specific spec
This is a separate product surface from the mobile pay-by-plate Flowbird integration already documented elsewhere in this corpus - don't conflate the two when scoping partner access
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?