LeasHub

LeasHub Docs · Fleet owner platform

Put your EV fleet to work.

List your vehicles and drivers, accept bookings that fit your fleet, and track your earnings.

Start here

A clear path from first login to first successful request.

Quickstart tutorial

Make your first request and see a booking move through the LeasHub lifecycle.

  1. 1

    Create an integration credential

    Give your app a clear name and only the scopes it needs.

  2. 2

    Fetch available resources

    Load vehicles, drivers or categories for your workflow.

  3. 3

    Create and track a booking

    Use idempotency, handle the response and listen for events.

Your first authenticated call

cURL
# List the vehicle categories you can work withcurl https://leashub-backend-prod-14573850302.europe-west1.run.app/api/v1/fleet-owners/vehicle-categories \  -H "Authorization: Bearer lh_live_..." \  -H "Accept: application/json"

Authentication

Use API credentials for external integrations.

  • Send Authorization: Bearer lh_live_... with every request.
  • Request only the scopes your integration needs.
  • Store keys securely: a key is shown once, when it is created.

Webhooks

Receive booking requests, vehicle updates, driver activity and trip status changes.

  • Verify the HMAC SHA-256 signature on every delivery.
  • Use a public HTTPS endpoint.
  • Return a 2xx response within 10 seconds.

Errors & troubleshooting

Find the cause quickly with status codes and request IDs.

  • 401: invalid, expired or revoked credential.
  • 403: the credential is missing a required scope.
  • 404: not found, including resources that belong to another account.

API reference

33 documented fleet owner endpoints.

Try it in the interactive reference

Profile3

  • GET/api/v1/fleet-owners/meGet your fleet profile
  • PATCH/api/v1/fleet-owners/meUpdate your fleet profile
  • PATCH/api/v1/fleet-owners/me/market-connectUpdate Marketplace Connect

Bookings6

  • GET/api/v1/fleet-owners/vehicle-categoriesList vehicle categories
  • GET/api/v1/fleet-owners/bookings/requestsView booking requests
  • GET/api/v1/fleet-owners/bookingsList fleet bookings
  • POST/api/v1/fleet-owners/bookings/:id/acceptAccept booking
  • POST/api/v1/fleet-owners/bookings/:id/rejectReject booking
  • POST/api/v1/fleet-owners/bookings/:id/assignAssign vehicle and driver

Drivers13

  • POST/api/v1/fleet-owners/drivers/inviteInvite driver
  • POST/api/v1/fleet-owners/drivers/bulk-inviteInvite drivers in bulk
  • GET/api/v1/fleet-owners/driversList fleet drivers
  • GET/api/v1/fleet-owners/drivers/:idGet driver details
  • PATCH/api/v1/fleet-owners/drivers/:idUpdate driver
  • GET/api/v1/fleet-owners/drivers/:id/vehiclesList driver vehicles
  • POST/api/v1/fleet-owners/drivers/:id/paymentsCreate driver payment
  • GET/api/v1/fleet-owners/drivers/:id/paymentsList driver payments
  • POST/api/v1/fleet-owners/drivers/:id/shiftsCreate driver shift
  • GET/api/v1/fleet-owners/drivers/:id/shiftsList driver shifts
  • GET/api/v1/fleet-owners/drivers/:id/activityView driver activity
  • POST/api/v1/fleet-owners/drivers/:id/suspendSuspend driver
  • POST/api/v1/fleet-owners/drivers/:id/reactivateReactivate driver

Leave requests3

  • GET/api/v1/fleet-owners/leave-requestsList leave requests
  • POST/api/v1/fleet-owners/leave-requests/:id/approveApprove leave request
  • POST/api/v1/fleet-owners/leave-requests/:id/rejectReject leave request

Earnings4

  • GET/api/v1/fleet-owners/earnings/dashboardView earnings dashboard
  • GET/api/v1/fleet-owners/earnings/pendingList pending earnings
  • GET/api/v1/fleet-owners/earnings/completedList completed earnings
  • GET/api/v1/fleet-owners/earnings/transactionsList earnings transactions

Developer4

  • GET/api/v1/fleet-owners/developer/credentialsList API credentials
  • POST/api/v1/fleet-owners/developer/credentialsCreate API credential
  • GET/api/v1/fleet-owners/developer/webhooksList webhook endpoints
  • POST/api/v1/fleet-owners/developer/webhooksCreate webhook endpoint
Open interactive API reference

LeasHub Documentation · Last updated October 2026 · Questions? Contact the team