Revolo API
Connect a DMS to Revolo
The Revolo API lets a dealer management system connect to a Revolo organization with OAuth 2.0, list that organization's workflows, create vehicles, and send those vehicles into one or more workflows.
Authentication is OAuth — there are no per-organization API keys. A Revolo user signs in on a branded consent page on the Revolo app, grants your application access to one organization, and you call the API with the resulting access token.
Base URL
https://app.revolo.aiDocumentation lives on revolo.ai. Authorization, token exchange, and API calls all go to the app host above.
Endpoints
| Method | Path | Purpose |
|---|---|---|
| GET | /oauth/authorize | User login and org consent |
| POST | /oauth/token | Exchange a code or refresh a token |
| POST | /oauth/revoke | Revoke an access or refresh token |
| GET | /api/v1/organization | Confirm the connected organization |
| GET | /api/v1/workflows | List active workflows |
| POST | /api/v1/assets | Create a vehicle |
| POST | /api/v1/assets/:id/workflows | Send an existing vehicle to workflows |
| POST | /api/v1/assets/submit | Create a vehicle and send it to workflows |
Typical DMS flow
- Redirect the Revolo user to OAuth authorize.
- Exchange the authorization code for tokens.
- On a vehicle detail screen, list workflows.
- Submit the vehicle (VIN, year, make, model, mileage, photos, and any other details) to one or more selected workflows.
Organization opt-in
API access is off by default. A Revolo owner or admin enables it in Settings → Integrations. Until that toggle is on, consent is rejected and API calls return 403.
Next
Start with Authentication, then Vehicles.