Integrations & API

Connect the systems you already run

BusPro integrates with payment providers, messaging channels, mapping, kiosk hardware and accounting systems — and exposes the same records through a scoped, versioned API.

Credentials are stored server-side and never exposed to the browser.

Connections

Integration families

Payments

Card, wallet and regional payment providers, with payouts and platform fees kept on separate ledgers.

  • Stripe Connect
  • PayPal
  • Apple Pay & Google Pay
  • Regional providers

Messaging

Transactional email, SMS and WhatsApp through configurable providers, with templates and delivery logs.

  • Email delivery
  • Twilio SMS
  • WhatsApp Business
  • Push notifications

Maps & location

Geocoding, route geometry, terminal coordinates and live vehicle positions.

  • Mapbox
  • Route geometry
  • Geofencing
  • GPS telemetry

Hardware

Kiosk terminals, display screens, scanners and Bluetooth thermal printers.

  • Thermal printers
  • Kiosk enclosures
  • QR scanners
  • Display players

Business systems

Push operational and financial records into the systems your finance and support teams already use.

  • Accounting exports
  • Webhooks
  • REST API
  • Signed payloads

Developer platform

Versioned REST access, scoped keys, sandbox and production environments and delivery logs.

  • API v1
  • Scoped keys
  • Webhook signing
  • Usage monitoring

Developer platform

Built for approved integrators

Scoped API keys

Keys are created per environment with explicit scopes, rotated on a schedule and revoked instantly. Secrets never reach a browser.

Versioned REST

A documented v1 surface for bookings, trips, schedules, availability, tickets, payments and operational events.

Signed webhooks

Every delivery is signed, logged and retried with backoff; failures stay visible until resolved.

Sandbox & production

Test against a sandbox tenant before promoting the same integration to live records.

API v1 · selected endpoints

GET/v1/routesPublished routes with stops and segments
GET/v1/tripsDepartures by route, date and origin
GET/v1/trips/{id}/availabilitySeat availability for a segment
POST/v1/bookingsCreate a booking with passengers and seats
GET/v1/bookings/{id}Booking detail and ticket references
POST/v1/tickets/{id}/validateServer-side ticket validation
GET/v1/settlementsSettlement statements for a period
POST/v1/webhooksRegister a signed webhook destination

Webhook events

  • booking.created
  • booking.cancelled
  • ticket.scanned
  • trip.departed
  • trip.delayed
  • payment.settled
  • incident.reported

Deliveries are signed with a per-endpoint secret, logged with status and latency, and retried with exponential backoff. Rate limits are applied per key.

Building on BusPro?

Tell us what you want to connect. Approved partners receive sandbox credentials, scoped keys and documentation.