API access quickstart and authentication
How to start integration access and understand current authentication modes.
This quickstart explains how to begin a Maxmove integration, including current authentication and scope expectations.
What this is
Maxmove provides operational APIs across order, driver, fleet, vehicle, and chat domains with environment-specific access control.
What to provide
- Orders:
/v1/ordersand order status/history endpoints. - Driver/Fleet operations:
/v1/driver/*and/v1/fleet/*paths. - Vehicle catalog and types:
/v1/vehicles/*paths. - Chat conversation workflows:
/v1/chat/*paths. - Expected production traffic profile, required scopes, and target environment.
What happens next
- Available now: authenticated workspace sessions for most operational routes.
- Available now: API key validation in selected flows (for example analytics endpoints using
x-api-key). - Coming soon: broader partner-grade provisioning and standardized external auth rollout by integration cohort.
- Support confirms access model, scopes, and launch sequencing for production onboarding.
For integration onboarding, request environment details, allowed scopes, and expected traffic profile first.
Was this article helpful?
Related articles
Orders API fields and multi-stop payloads
Required order structure and how to model intermediate stops.
Status updates, retries, and webhook strategy
Current status retrieval pattern and recommended retry behavior.
API security, rate limits, idempotency, and support
Integration hardening practices for production-safe API clients.
← Back to API and Integrations
Still need help? Contact support