create planned routes by geojson
GET/list-planning-routesRequisição
Query Params
route_date
string
required
route date to search
Match pattern:
^\d{4}-\d{2}-\d{2}$
search_term
string
optional
route name, driver name, activty and vehicle name to search
page
number
optional
current page
Default:
1
per_page
number
optional
quantity of items per page
Default:
10
order_by
enum<string>
optional
order by
Allowed values:
planned_start_hourplanned_end_hourroute_nameplanned_productive_kmplanned_dead_start_kmplanned_dead_end_kmstop_counts
Default:
planned_start_hour
order_direction
enum<string>
optional
order direction
Allowed values:
ascdesc
Default:
asc
Exemplos de Requisição
Responses
OK(200)
Pedido inválido(400)
Não autorizado(401)
Proibido(403)
Registro não encontrado(404)
Erro do servidor(500)
Código HTTP: 200
Tipo de Conteúdo: JSONapplication/json
ok
Data Schema
routes
array [object {21}]
optional
planned_route_id
string
optional
summary_route_id
string
optional
route_name
string
optional
planned_start_hour
string
optional
planned_end_hour
string
optional
stop_counts
integer <int32>
optional
planned_productive_km
number <float>
optional
planned_dead_start_km
number <float>
optional
planned_dead_end_km
number <float>
optional
activity
string
optional
organization_id
integer <int32>
optional
route_day
string
optional
realized_start_hour
string
optional
realized_end_hour
string
optional
realized_productive_km
number <float>
optional
realized_dead_start_km
number <float>
optional
realized_dead_end_km
number <float>
optional
realized_driver_id
integer <int32>
optional
realized_vehicle_id
integer <int32>
optional
planned_driver_id
integer <int32>
optional
planned_vehicle_id
integer <int32>
optional
Example
Not configured
Last modified: a month ago