The Routes API lets you manually create delivery routes or auto-plan them via OpenRouteService (ORS). Each route belongs to an order (Documentation Index
Fetch the complete documentation index at: https://mintlify.com/JorLOrT/rappi2/llms.txt
Use this file to discover all available pages before exploring further.
orden_id) and can carry an ordered list of stops (paradas). When auto-planning, the API calls ORS to compute distance and duration, then optionally creates a buffer geofence around the computed geometry in MongoDB.
All endpoints require a valid Bearer token. The required permission is noted on each operation.
List routes
GET /rutas
Permission: rutas:read
Filter routes by order ID. Omit to return all routes.
Create route
POST /rutas
Manually create a route with a set of stops.
Permission: rutas:write
ID of the order this route belongs to. Must reference an existing order.
Total route distance in kilometres.
Estimated travel time as an ISO 8601 duration string (e.g.
"PT45M").Ordered list of stops to include on creation.
Auto-plan route via ORS
POST /rutas/planificar
Calls OpenRouteService to compute the optimal route between an origin and destination, stores the computed distance and travel time, and optionally creates a buffer geofence in MongoDB around the returned geometry.
Permission: rutas:write
Order to associate with the planned route.
Origin longitude (
-180 to 180).Origin latitude (
-90 to 90).Destination longitude (
-180 to 180).Destination latitude (
-90 to 90).When
true, a ruta_buffer geofence is created in MongoDB around the computed route geometry.Buffer tolerance in metres for the geofence polygon (
1–5000).Get route
GET /rutas/{ruta_id}
Retrieve a single route with all its stops.
Permission: rutas:read
Route ID.
Update route
PATCH /rutas/{ruta_id}
Partially update a route’s distance or estimated time. All body fields are optional.
Permission: rutas:write
Route ID.
Updated distance in kilometres.
Updated estimated duration as ISO 8601 duration (e.g.
"PT1H").Delete route
DELETE /rutas/{ruta_id}
Deletes the route and all associated geofences stored in MongoDB.
Permission: rutas:delete
Route ID.
List stops
GET /rutas/{ruta_id}/paradas
Return all stops for a route ordered by secuencia.
Permission: rutas:read
Route ID.
Add stop
POST /rutas/{ruta_id}/paradas
Append a new stop to an existing route.
Permission: rutas:write
Route ID.
Street address of the stop.
Position in the delivery sequence (1-based).
Order associated with this stop.
District name.
Initial stop status:
Pendiente, Visitada, or Omitida.Get stop
GET /rutas/{ruta_id}/paradas/{parada_id}
Retrieve a single stop by ID, scoped to the given route.
Permission: rutas:read
Route ID.
Stop ID.
Update stop
PATCH /rutas/{ruta_id}/paradas/{parada_id}
Update a stop’s status, timestamp, address, or district. All body fields are optional.
Permission: rutas:write
Route ID.
Stop ID.
New status:
Pendiente, Visitada, or Omitida.ISO 8601 datetime at which the stop was visited.
Updated street address.
Updated district name.
Delete stop
DELETE /rutas/{ruta_id}/paradas/{parada_id}
Remove a stop from a route.
Permission: rutas:write
Route ID.
Stop ID.
Response schema
Route ID (auto-incremented).
Order this route belongs to.
Distance in kilometres, returned as a decimal string.
Estimated travel time in ISO 8601 duration format (e.g.
"PT30M").Ordered list of stops on this route.