TaxiFlow export format register
Version 3 October 2026 · Linköping Punkt Taxi AB, organisation number 559348-6425
This public register describes customer-specific data structures and formats for TaxiFlow's hosted booking and dispatch service. Staff prepare the export after an authorised request. There is no self-service export button.
Package and standards
Tabular records use UTF-8 CSV with headers (RFC 4180). Nested content uses UTF-8 JSON (RFC 8259). Customer files retain their stored or an equivalent common format. A secure ZIP archive (ISO/IEC 21320-1) or equivalent package contains a manifest, field description and available files. Stable record identifiers, relationships and timestamps are included where available. The manifest states timezone and field types, missing optional datasets, and any legacy-record or mapping limitation.
Exportable structures
The table lists current customer-specific record categories and principal fields. A file is included when the category exists for that customer. The actual export includes a field description for every delivered column and type.
| File | Records | Principal fields and structure |
|---|---|---|
business-profile.csv | Business identity and fleet account | id, domain, city, company and legal identity, billing contact, package and fleet counts, created_at |
settings.json | Customer-specific service settings | tenant_id; branding, languages, booking appearance, address-search settings, contact details, notification switches, fare and operating-area settings where configured |
vehicles.csv | Fleet vehicles | id, tenant_id, registration_number, make, model, color, year, is_active, created_at, updated_at |
drivers.csv | Drivers | id, name, phone_number, email, address, license_number, vehicle_id, vehicle_details, status, is_active, language, source_domain; last recorded coordinates where held |
driver-applications.csv | Driver applications, when used | id, tenant_id, name, phone_number, email, city_area, license_number, vehicle_details, status, notes, created_at, updated_at |
customers.csv | Passenger and customer contacts | id, name, phone, email, first_seen, last_seen, total_bookings, created_at, updated_at, source_domain |
bookings.csv | Bookings and journeys | id, customer_id, driver_id, passenger contact, pickup and dropoff address and coordinates, pickup date and time, status, fare and currency, passenger and bag counts, comments, trip times, source_domain, route distance and duration |
booking-stops.csv | Intermediate stops, when used | stop_id, booking_id, stop_order, stop_type, address, coordinates, leg distance and duration, status and event times |
booking-offers.csv | Dispatch offer history | id, booking_id, driver_id, attempt_no, status, offered_at, responded_at |
driver-finance.csv | Journey-linked driver financial records | id, driver_id, booking_id, amount, currency, status, created_at |
hotel-partners.csv | Hotel booking partners, when used | id, hotel_name, username, is_active, default_pickup_address, booking_email, created_at, updated_at |
content.json | Customer-authored website text and message templates | record id, content key, locale, body, channel, template key, subject, active status, created_at, updated_at |
usage-events.csv | Customer-specific service and communication events where separable | id, event type/name, provider, status, quantity, related booking/customer/driver ids, event time; other customer-specific metadata where held |
files/ | Customer-uploaded files and owned assets, when held | stored or equivalent common format, with record association in the manifest |
Scope and exclusions
TaxiFlow verifies tenant ownership before releasing each record, including legacy records with incomplete tenant links. Password hashes, access tokens, API keys, supplier credentials, shared security logs, platform-wide telemetry, internal algorithms, source code and licensed map content are excluded. An exclusion will not be used to withhold customer exportable data. Material omissions and mapping limits are explained in the export manifest.
This register describes an assisted process, not an existing automated export API or a guaranteed mapping to another provider. The register is also available as machine-readable JSON. An authorised receiving provider can request interface details at info@taxiflow.io.