VRt.Universal [UV] (6.20.2289)

Description

Software interface for universal trip planning.

Features

  • Ability to pick up cargo from any location
  • Possibility of unloading in any location
  • Pair orders of several types: PICKUP (loading), DROP (unloading)
  • Single requests of several types: DROP_FROM_BOX (unloading cargo that is already in the body), PICKUP_TO_BOX (cargo pickup into the body without subsequent unloading), WORK (working at the location without moving the cargo)
  • A complex order can consist of any number of orders of any type
  • Transport and executors are divided into different entities, when planning, the optimal assignment of the executor to the transport occurs
  • The transport has several compartments - each of which can accommodate cargo and has its own characteristics
  • Accounting for the compatibility of cargo with transport in terms of cargo dimensions (length, width, height, additional capacity parameters)
  • Taking into account the compatibility of the cargo-compartment of transport (the ability to take into account the features of the compartment: refrigerator, thermal bag, fasteners, etc.)
  • Substitute applications, i.e. the ability to execute one of the substitute applications, the choice of which is based on its geographic location and time window

Restrictions support

Performer restrictions:

  • Start/finish location
  • Accounting for the performer's way to the transport location
  • Performer's availability schedule is a list of time windows when the performer can move and work on locations
  • The maximum duration of the performer's work during the specified time period

Transport restrictions:

  • Start/finish location
  • Transport availability schedule is a list of time windows when the transport is available
  • The maximum route distance
  • Several compartments in the transport, each with its own parameters
  • Capacity upper limit (weight, volume, number of orders, number of demands)

Order restrictions:

  • Strict time windows
  • Ability to specify different valid time windows for a location and time windows to fulfil the desired demand
  • Accounting for the requests fulfillment order within the route
  • A list of desired time windows with different associated costs

Compatibilities

Entities are compatible if the capabilities list of one entity corresponds to the list of restrictions of another entity (example: fleet parameters corresponds to cargo parameters to be delivered).

Supported compatibilities:

NameRestrictionsFeatures
Order - Performerorder.performer_restrictionsperformer.performer_features
Order - Not a performerorder.performer_blacklistperformer.performer_features
Cargo - Compartmentorder.cargo.box_restrictionstransport.box.box_features
Location - Transportlocation.transport_restrictionstransport.transport_features
Transport - Performertransport.performer_restrictionsperformer.performer_features
Performer - Transportperformer.transport_restrictionstransport.transport_features
Order - Orderorder.order_restrictionsorder.order_features

Business rule examples:

NameBusiness rule example
Order - PerformerThe driver must have a special license to fulfil the order
Order - Not a performerThe driver is in the blacklist
Cargo - BoxFor transportation of frozen products, a compartment with a special temperature profile is required
Location - TransportRestrictions on the transport height
Transport - PerformerThe truck driver must have the class C driving license
Performer - TransportThe driver is allowed to work on a specific transport
Order - OrderIt is not allowed to transport fish and fruits in the same compartment

Cargo placement

List of possibilities of a object rotations (90 degree step):

  • ALL - can rotate by any axis
  • YAW - can yaw
  • PITCH - can pitch
  • ROLL - can roll

rotation

Trip model

The trip is described by the list of states of the executor, while the executor can be in several states at the same time (for example, to be inside the working time window of a location and fulfill an order at the same location).

Possible values ​​of the flags responsible for the geographical location:

  • AROUND_LOCATION - the performer is located near the location - in the process of parking or leaving it.
  • INSIDE_LOCATION - the performer is at the location.

Possible values ​​of the flags responsible for being in time windows:

  • INSIDE_WORKING_WINDOW - the executor is inside the working time window.
  • INSIDE_LOCATION_WINDOW - the executor is inside the location's working time.
  • INSIDE_EVENT_HARD_WINDOW - the executor is inside a hard time window.
  • INSIDE_EVENT_SOFT_WINDOW - the executor is inside the soft time window.

Possible values ​​of flags responsible for actions:

  • ON_DEMAND - the executor is working on the request.
  • WAITING - the performer is in standby mode.
  • RELOCATING - the executor is moving to the next stop.
  • BREAK - the performer is on a break.

An example of a route with multiple states at each point in time

timeset of active flagslocation / order / application / eventcomment
10:00INSIDE_LOCATION
AROUND_LOCATION
2 / - / - / -starting location
10:10RELOCATING- / - / - / -we go to the first order
10:20AROUND_LOCATION2 / - / - / -arrived at the first order
10:40AROUND_LOCATION
INSIDE_LOCATION
WAITING
2 / - / - / -parked
11:00AROUND_LOCATION
INSIDE_LOCATION
INSIDE_LOCATION_WINDOW
WAITING
INSIDE_EVENT_HARD_WINDOW
2 / - / - / -waited for the start of the location window and at the same time the availability of the order
11:25AROUND_LOCATION
INSIDE_LOCATION
INSIDE_LOCATION_WINDOW
ON_DEMAND
INSIDE_WORKING_WINDOW
INSIDE_EVENT_HARD_WINDOW
2 / 1 / 2 / 3waited for the change of artist
11:30AROUND_LOCATION
INSIDE_LOCATION
INSIDE_LOCATION_WINDOW
ON_DEMAND
INSIDE_WORKING_WINDOW
INSIDE_EVENT_HARD_WINDOW
INSIDE_EVENT_SOFT_WINDOW
2 / 1 / 2 / 3while working - a soft window happened
11:40AROUND_LOCATION
INSIDE_LOCATION
INSIDE_LOCATION_WINDOW
INSIDE_WORKING_WINDOW
2 / - / - / -finished working
11:45AROUND_LOCATION
INSIDE_WORKING_WINDOW
2 / - / - / -drove out of the parking lot
11:45RELOCATING
INSIDE_WORKING_WINDOW
- / - / - / -we go to the next order

Planning configuration

For each planning, it is possible to specify a planning configuration that defines the objective function, the desired quality of the routes, and the calculation speed.

The name of the scheduling configuration is passed in the trips_settings.configuration field.

Main configurations:

TitleTask
optimize_distanceArrange as many orders as possible, then optimize the total mileage (the number of vehicles is selected based on the mileage), used by default
optimize_transportsPlace as many orders as possible, while using as little transport as possible, ceteris paribus, optimize the work time of performers
optimize_locality_groupingPlace as many orders as possible, while striving to optimize the visual grouping of routes, but not their number
optimize_cars_then_distanceArrange as many orders as possible, then optimize the number of vehicles, then the mileage
optimize_timePlace as many orders as possible, then optimize the total work time of performers
optimize_cars_then_timeArrange as many orders as possible, then optimize the number of transport, then the total time of the performers
optimize_moneyOptimize the value of "profit - costs", consists of rewards for applications and costs for performers and transports (optimized value is non-negative)

Additional configurations:

TitleTask
visual_groupingArrange as many orders as possible while using as little transport as possible and routes should be visually grouped
optimize_visual_groupingArrange as many orders as possible, then evenly distribute orders taking into account transport accessibility zones (similar to visual_grouping, but visual grouping is calculated differently)
optimize_cars_then_locality_groupingArrange as many orders as possible, then optimize the number of vehicles, then visually group the routes
optimize_cars_then_single_location_grouping_sequencedPlace as many orders as possible, then optimize the number of machines, then reliability

In addition to the existing planning options, it is possible to create an objective function directly for the client's business processes (request configuration).

For development, it is recommended to use optimize_cars_then_distance, since this configuration does not require detailed selection of rates and order values.

Data validation

Input data validation consists of several steps, which are described below.

Validation of planning results (including the search for possible reasons why orders were not planned) is located in the analytics method.

1. Schema check

If the request does not follow the schema, then scheduling is not fully started and such an error is returned along with a 400 code in schema_errors.

We recommend validating the request against the schema (or yaml file) before sending it to the server.

2. Check for logical errors that prevent planning from continuing

Schema-correct data passes the second stage of checking for the possibility of starting planning.

An example of errors at this stage are keys leading to empty entities, or if all orders are incompatible with all performers, i.e. something that makes the planning task pointless.

These errors are returned along with a 400 code in logical_errors.

3. Check for logical errors that prevent planning from continuing

At the third stage, each entity is checked separately.

All entities that have not passed validation are cut out from the original task and are not sent for planning.

Depending on the setting of treat_warnings_as_errors, the results of this type of validation are returned to warnings either with a 400 code or with the scheduling result.

4. Checks in the planning process

Part of the checks can only be carried out in the planning process.

For example - that according to the specified tariffs and according to the current traffic forecast, it is physically impossible to reach a certain point.

The results of these checks are returned in warnings or together with the scheduling result.

Entity relationship diagram

erd

Xlsx

Performers

The name of the sheet is performers.

List of available performers.

Described object:

key
required
string [ 1 .. 1024 ] characters

Performer's key, unique identifier.

required
Array of objects (performer_shift) [ 1 .. 15001 ] items unique

List of working shifts of performer.

own_transport_type
string (transport_type)
Enum: "CAR" "TRUCK_1500" "TRUCK_3000" … 9 more

Transport types:

  • CAR - car
  • TRUCK_1500 - truck with permissible weight 1500 kg
  • TRUCK_3000 - truck with permissible weight 3000 kg
  • TRUCK_5000 - truck with permissible weight 5000 kg
  • TRUCK_10000 - truck with permissible weight 10000 kg
  • TRUCK_20000 - truck with permissible weight 20000 kg
  • TRUCK_GARBAGE_1 - truck for transporting garbage (type 1)
  • TRUCK_GARBAGE_2 - truck for transporting garbage (type 2)
  • TUK_TUK - tuk-tuk
  • BICYCLE - bicycle
  • PEDESTRIAN - pedestrian
  • PUBLIC_TRANSPORT - public transport

Permissible weight is the weight of the equipped transport with cargo and driver, set by the manufacturer as the maximum allowable.

object or null (performer_compatibilities)

Performer compatibilities.

object or null (performer_limits)

The performer limitations.

Array of objects (attributes) [ 0 .. 1000 ] items unique

Attributes. Used to add service information.

{
  • "key": "performer0001",
  • "shifts": [
    ],
  • "own_transport_type": "CAR",
  • "compatibilities": {
    },
  • "limits": {
    },
  • "attributes": [ ]
}

Transports

The name of the sheet is transports.

List of available transport.

Described object:

key
required
string [ 1 .. 1024 ] characters

Transport key, unique identifier.

required
Array of objects (transport_shift) [ 1 .. 15001 ] items unique

List of working shifts of transport.

transport_type
string (transport_type)
Enum: "CAR" "TRUCK_1500" "TRUCK_3000" … 9 more

Transport types:

  • CAR - car
  • TRUCK_1500 - truck with permissible weight 1500 kg
  • TRUCK_3000 - truck with permissible weight 3000 kg
  • TRUCK_5000 - truck with permissible weight 5000 kg
  • TRUCK_10000 - truck with permissible weight 10000 kg
  • TRUCK_20000 - truck with permissible weight 20000 kg
  • TRUCK_GARBAGE_1 - truck for transporting garbage (type 1)
  • TRUCK_GARBAGE_2 - truck for transporting garbage (type 2)
  • TUK_TUK - tuk-tuk
  • BICYCLE - bicycle
  • PEDESTRIAN - pedestrian
  • PUBLIC_TRANSPORT - public transport

Permissible weight is the weight of the equipped transport with cargo and driver, set by the manufacturer as the maximum allowable.

Array of objects (box) [ 0 .. 100 ] items unique
Default: []

A list of transport compartments that can accommodate the cargo.

object or null (transport_compatibilities)

Transport compatibilities.

object or null (transport_limits)

Transport load limits.

Array of objects (attributes) [ 0 .. 1000 ] items unique

Attributes. Used to add service information.

{
  • "key": "transport001",
  • "shifts": [
    ],
  • "transport_type": "CAR",
  • "boxes": [ ],
  • "compatibilities": {
    },
  • "limits": {
    },
  • "attributes": [ ]
}

Boxes

The name of the sheet is transports.boxes.

List of transport compartments that can hold cargo. The table is required if there are orders with PICKUP and DROP types in the calculation. In the description of the compartments, those fields that describe the cargo are required.

Described object:

key
required
string [ 1 .. 1024 ] characters

Unique compartment key used to identify the cargo placement in compartments.

object or null (capacity)

The compartment capacity, which limits the maximum amount for all capacity fields of all the cargoes.

object or null (box_compatibilities)

A transport box compatibilities.

object or null (box_limits)

max_one_cargo_capacity - capacity fields limitation for one cargo.

{
  • "key": "box01",
  • "capacity": {
    },
  • "compatibilities": {
    },
  • "limits": {
    }
}

Orders

The name of the sheet is orders.

Order list.

Described object:

key
required
string [ 1 .. 1024 ] characters

Order key, unique identifier.

required
Array of objects (demand) [ 1 .. 1000 ] items unique

Demands list.

Array of objects (cargo) [ 0 .. 1000 ] items unique
Default: []

The list of cargoes referred to by the demands of this order. The list must be empty if all demands in the order are of type WORK.

object or null (order_compatibilities)
Array of objects (attributes) [ 0 .. 1000 ] items unique

Attributes. Used to add service information.

{
  • "key": "order01",
  • "demands": [
    ],
  • "cargos": [ ],
  • "compatibilities": {
    },
  • "attributes": [ ]
}

Cargos

The name of the sheet is orders.cargos.

List of cargoes. May contain one load for DROP, list for PICKUP, empty for WORK. The table is optional if all tickets are of type WORK.

Described object:

key
required
string [ 1 .. 1024 ] characters

Cargo key, unique identifier.

object or null (capacity)

Cargo additive measures.

object or null (cargo_compatibilities)
target_box_key
string or null [ 1 .. 1024 ] characters
Default: null

The key of the transport compartment in which the cargo is already located. Applicable only for cargo that is in the order with the type DROP_FROM_BOX. For other order types, the key must be empty.

{
  • "key": "cargo01",
  • "capacity": {
    },
  • "compatibilities": {
    },
  • "target_box_key": "box01"
}

Trips

The name of the sheet is trips.

List of flights.

Described object:

key
required
string [ 1 .. 1024 ] characters

Unique trip identifier.

name
string (trip_name) [ 0 .. 64 ] characters

Trip name.

required
object (assigned_performer)

Performer's shift assigned to the specified time (shift_time).

required
object (assigned_transport)

Transport's shift assigned to the specified time (shift_time).

required
Array of objects (trip_state) [ 0 .. 15001 ] items

List of performer's states.

waitlist
Array of strings (trip_waitlist) [ 0 .. 15001 ] items unique [ items [ 1 .. 1024 ] characters ]

A list of keys assigned to orders, but not scheduled for a specific time.

Array of objects (attributes) [ 0 .. 1000 ] items unique

Attributes. Used to add service information.

{
  • "key": "631988f0-9e27-11ed-a8fc-0242ac120002",
  • "name": "1-ABC",
  • "performer": {
    },
  • "transport": {
    },
  • "states": [
    ],
  • "waitlist": [
    ],
  • "attributes": [ ]
}

Facts

The name of the sheet is facts.

List of facts.

Described object:

Array of objects (order_fact) [ 0 .. 50001 ] items

List of order's facts.

Array of objects (performer_fact) [ 0 .. 15001 ] items

List of performers's facts.

{
  • "order_facts": [
    ],
  • "performer_facts": [
    ]
}

Plan settings

The name of the sheet is plan_settings.

Planning settings.

Described object:

object (trips_settings)

Trip creation settings.

object (geo_settings)

Geodata usage settings.

object (calculation_settings)

Calculation settings.

{
  • "trips_settings": {
    },
  • "geo_settings": {
    },
  • "calculation_settings": {
    }
}

Actualize settings

The name of the sheet is actualize_settings.

Actualize settings.

Described object:

current_time
string or null<date-time>

Current date and time according to the ISO 8601. If not specified, the current time when the request was received by the server is taken.

object (geo_settings)

Geodata usage settings.

object (calculation_settings)

Calculation settings.

{
  • "current_time": "2024-02-21T09:30:00+03:00",
  • "geo_settings": {
    },
  • "calculation_settings": {
    }
}

Replan settings

The name of the sheet is replan_settings.

Replan settings.

Described object:

object (replan_strategy)

Replan strategy.

object (trips_settings)

Trip creation settings.

object (geo_settings)

Geodata usage settings.

object (calculation_settings)

Calculation settings.

{
  • "replan_strategy": {
    },
  • "trips_settings": {
    },
  • "geo_settings": {
    },
  • "calculation_settings": {
    }
}

Plan

规划——根据订单、表演者和交通创建旅行。

计划请求可以以同步和异步模式执行。

Planning (SYNC)

Sync method for trip planning. Use only for testing and manual plannings. For production use async method.

Authorizations:
ApiKeyAuth
Request Body schema: application/json
required

New planning request.

required
Array of objects (location) [ 1 .. 15001 ] items unique

List of locations used for orders and shifts.

required
Array of objects (order) [ 1 .. 15001 ] items unique

Orders list.

required
Array of objects (performer) [ 1 .. 15001 ] items unique

Available performers list.

required
Array of objects (transport) [ 1 .. 15001 ] items unique

Available transports list.

Array of objects (hardlink) [ 0 .. 15001 ] items unique
Default: []

Assignments list.

object (plan_settings)

Planning settings.

Array of objects (routing_transport_matrix_list) [ 0 .. 12 ] items unique

Time and distance matrices list for each transport type from dataset. By specifying an external routing matrix external_routing, parameters geo_settings are not used.

dataset_name
string (dataset_name) [ 0 .. 1000 ] characters

The name of the dataset. A technical field that does not affect planning.

Responses

Response Schema: application/json
required
object (tracedata)

Data for request tracing.

required
Array of objects (trip) [ 0 .. 15001 ] items unique
Default: []

Schedule of trips assigned to performers.

required
object or null (plan_statistics)

General statistics on planned trips.

Array of objects (entity_warning_list) [ 0 .. 15001 ] items

Warning list.

object (unplanned_items)

Unplanned items list.

progress
required
integer<int32> (calculation_progress) [ 0 .. 100 ]

Calculation progress as a percentage. The progress displays the current number of completed steps.

required
object (calculation_info)

Calculation information.

Request samples

Content type
application/json
Example
{
  • "locations": [
    ],
  • "orders": [
    ],
  • "performers": [
    ],
  • "transports": [
    ],
  • "plan_settings": {
    }
}

Response samples

Content type
application/json
Example
{
  • "tracedata": {
    },
  • "trips": [
    ],
  • "statistics": {
    },
  • "progress": 100,
  • "info": {
    },
  • "warnings": [ ],
  • "unplanned_items": {
    }
}

Planning (ASYNC)

Trip planning. The result can be obtained using the result method, removing - with delete.

Authorizations:
ApiKeyAuth
Request Body schema: application/json
required

Launching the asynchronous planning.

required
Array of objects (location) [ 1 .. 15001 ] items unique

List of locations used for orders and shifts.

required
Array of objects (order) [ 1 .. 15001 ] items unique

Orders list.

required
Array of objects (performer) [ 1 .. 15001 ] items unique

Available performers list.

required
Array of objects (transport) [ 1 .. 15001 ] items unique

Available transports list.

Array of objects (hardlink) [ 0 .. 15001 ] items unique
Default: []

Assignments list.

object (plan_settings)

Planning settings.

Array of objects (routing_transport_matrix_list) [ 0 .. 12 ] items unique

Time and distance matrices list for each transport type from dataset. By specifying an external routing matrix external_routing, parameters geo_settings are not used.

dataset_name
string (dataset_name) [ 0 .. 1000 ] characters

The name of the dataset. A technical field that does not affect planning.

Responses

Response Schema: application/json
required
object (tracedata)

Data for request tracing.

id
required
string<uuid> (calculation_id)

Calculation identifier.

Request samples

Content type
application/json
Example
{
  • "locations": [
    ],
  • "orders": [
    ],
  • "performers": [
    ],
  • "transports": [
    ],
  • "plan_settings": {
    }
}

Response samples

Content type
application/json
{
  • "tracedata": {
    },
  • "id": "11111111-2222-3333-4444-555555555555"
}

Calculation state

Read calculation state by the calculation identifier.

Authorizations:
ApiKeyAuth
path Parameters
id
required
string<uuid> (calculation_id)
Example: 11111111-2222-3333-4444-555555555555

计算标识符

Responses

Response Schema: application/json
required
object (tracedata)

Data for request tracing.

progress
required
integer<int32> (calculation_progress) [ 0 .. 100 ]

Calculation progress as a percentage. The progress displays the current number of completed steps.

required
object (calculation_info)

Calculation information.

Response samples

Content type
application/json
{
  • "tracedata": {
    },
  • "progress": 52,
  • "info": {
    }
}

Cancel calculation

Cancel calculation by the calculation identifier.

Authorizations:
ApiKeyAuth
path Parameters
id
required
string<uuid> (calculation_id)
Example: 11111111-2222-3333-4444-555555555555

计算标识符

Responses

Response samples

Content type
application/json
{
  • "tracedata": {
    },
  • "message": "logical",
  • "schema_errors": [ ],
  • "logical_errors": [
    ],
  • "warnings": [ ]
}

Getting the result

Getting the planning result based on the calculation identifier.

Authorizations:
ApiKeyAuth
path Parameters
id
required
string<uuid> (calculation_id)
Example: 11111111-2222-3333-4444-555555555555

计算标识符

Responses

Response Schema: application/json
required
object (tracedata)

Data for request tracing.

required
Array of objects (trip) [ 0 .. 15001 ] items unique
Default: []

Schedule of trips assigned to performers.

required
object or null (plan_statistics)

General statistics on planned trips.

Array of objects (entity_warning_list) [ 0 .. 15001 ] items

Warning list.

object (unplanned_items)

Unplanned items list.

progress
required
integer<int32> (calculation_progress) [ 0 .. 100 ]

Calculation progress as a percentage. The progress displays the current number of completed steps.

required
object (calculation_info)

Calculation information.

Response Schema: application/json
required
object (tracedata)

Data for request tracing.

required
Array of objects (trip) [ 0 .. 15001 ] items unique
Default: []

Schedule of trips assigned to performers.

required
object or null (plan_statistics)

General statistics on planned trips.

Array of objects (entity_warning_list) [ 0 .. 15001 ] items

Warning list.

object (unplanned_items)

Unplanned items list.

progress
required
integer<int32> (calculation_progress) [ 0 .. 100 ]

Calculation progress as a percentage. The progress displays the current number of completed steps.

required
object (calculation_info)

Calculation information.

Response samples

Content type
application/json
Example
{
  • "tracedata": {
    },
  • "trips": [
    ],
  • "statistics": {
    },
  • "progress": 100,
  • "info": {
    },
  • "warnings": [ ],
  • "unplanned_items": {
    }
}

Result removal

Removal of the planning result by the calculation identifier.

Authorizations:
ApiKeyAuth
path Parameters
id
required
string<uuid> (calculation_id)
Example: 11111111-2222-3333-4444-555555555555

计算标识符

Responses

Response samples

Content type
application/json
{
  • "tracedata": {
    },
  • "message": "logical",
  • "schema_errors": [ ],
  • "logical_errors": [
    ],
  • "warnings": [ ]
}

Data validation

Check data before using.

Authorizations:
ApiKeyAuth
Request Body schema: application/json
required

Data for validation.

required
Array of objects (location) [ 1 .. 15001 ] items unique

List of locations used for orders and shifts.

required
Array of objects (order) [ 1 .. 15001 ] items unique

Orders list.

required
Array of objects (performer) [ 1 .. 15001 ] items unique

Available performers list.

required
Array of objects (transport) [ 1 .. 15001 ] items unique

Available transports list.

Array of objects (hardlink) [ 0 .. 15001 ] items unique
Default: []

Assignments list.

object (plan_settings)

Planning settings.

Array of objects (routing_transport_matrix_list) [ 0 .. 12 ] items unique

Time and distance matrices list for each transport type from dataset. By specifying an external routing matrix external_routing, parameters geo_settings are not used.

dataset_name
string (dataset_name) [ 0 .. 1000 ] characters

The name of the dataset. A technical field that does not affect planning.

Responses

Response Schema: application/json
required
object (tracedata)

Data for request tracing.

required
Array of objects (entity_warning_list) [ 0 .. 15001 ] items

Warning list.

Request samples

Content type
application/json
Example
{
  • "locations": [
    ],
  • "orders": [
    ],
  • "performers": [
    ],
  • "transports": [
    ],
  • "plan_settings": {
    }
}

Response samples

Content type
application/json
{
  • "tracedata": {
    },
  • "warnings": [
    ]
}

Actualize

Trips actualization - updating the planned ETA, taking into account the facts and without changing the order of the roundabout.

Actualization takes place in three stages - verification, application of facts, updating times for failed trip states.

Use data cleaning to get the result of applying facts to the original task.

Accounting for the current time current_time:

  • Only facts that happened later than current_time are taken into account.
  • The minimum time of all states of computed trips is taken from current_time.

Accounting facts about the order:

  • If the order has completed all applications - it is considered completed.
  • If the order is completed or canceled - it, and the entities to which only it refers, are removed from the data for actualization.
  • If an order has a PICKUP demand, then the corresponding DROP demand will be converted into a DROP_FROM_BOX demand.
  • The fact about the order has a higher priority than the facts about the demands for this order (if the facts about the demands contradict the fact about the order, they will not be taken into account).
  • Only one unclosed fact DEMAND_START is allowed per trip (closed by the fact DEMAND_DONE) - since the performer can only fulfill one request at a time.
  • If there is a fact about the work on the application, which contradicts the planned order in the specified trip, this application will be completed first, then the trip will continue according to the planned order.

Accounting facts about the performer:

  • List of facts about the location of the performer in a particular location.
  • If the trip has started (the time of the fact is later than the scheduled start time of the trip) - the transport is considered to be in the same location as the performer.
  • If there are several facts, only the latest one in the time field is taken into account.
  • The location referenced by the fact must be in the locations list.

Accounting for existing trips:

  • Entities that are not referenced by input trips are removed - locations, performers, transport, hard links, orders, requests, events.
  • Changes of the performer and transport assigned to the trip cannot be used on other trips.

The trips received as a result of updating contain only those works that remain to be completed.

Actualization (SYNC)

Trips actualization.

Authorizations:
ApiKeyAuth
Request Body schema: application/json
required

New request for actualization.

required
Array of objects (location) [ 1 .. 15001 ] items unique

List of locations used for orders and shifts.

required
Array of objects (order) [ 1 .. 15001 ] items unique

Orders list.

required
Array of objects (performer) [ 1 .. 15001 ] items unique

Available performers list.

required
Array of objects (transport) [ 1 .. 15001 ] items unique

Available transports list.

Array of objects (hardlink) [ 0 .. 15001 ] items unique

Assignments list.

required
Array of objects (trip) [ 0 .. 15001 ] items unique

Existing routes.

object (facts)

Events that have taken place.

Array of objects (routing_transport_matrix_list) [ 0 .. 12 ] items unique

Time and distance matrices list for each transport type from dataset. By specifying an external routing matrix external_routing, parameters geo_settings are not used.

object (actualize_settings)

Actualize settings.

dataset_name
string (dataset_name) [ 0 .. 1000 ] characters

The name of the dataset. A technical field that does not affect planning.

Responses

Response Schema: application/json
required
object (tracedata)

Data for request tracing.

required
Array of objects (trip) [ 0 .. 15001 ] items unique
Default: []

Schedule of trips assigned to performers.

required
object or null (plan_statistics)

General statistics on planned trips.

Array of objects (entity_warning_list) [ 0 .. 15001 ] items

Warning list.

object (unplanned_items)

Unplanned items list.

progress
required
integer<int32> (calculation_progress) [ 0 .. 100 ]

Calculation progress as a percentage. The progress displays the current number of completed steps.

required
object (calculation_info)

Calculation information.

Request samples

Content type
application/json
{
  • "locations": [
    ],
  • "orders": [
    ],
  • "performers": [
    ],
  • "transports": [
    ],
  • "trips": [
    ]
}

Response samples

Content type
application/json
{
  • "tracedata": {
    },
  • "trips": [ ],
  • "statistics": {
    },
  • "warnings": [ ],
  • "unplanned_items": {
    },
  • "progress": 52,
  • "info": {
    }
}

Data validation

Check data before using.

Authorizations:
ApiKeyAuth
Request Body schema: application/json
required

Data for validation.

required
Array of objects (location) [ 1 .. 15001 ] items unique

List of locations used for orders and shifts.

required
Array of objects (order) [ 1 .. 15001 ] items unique

Orders list.

required
Array of objects (performer) [ 1 .. 15001 ] items unique

Available performers list.

required
Array of objects (transport) [ 1 .. 15001 ] items unique

Available transports list.

Array of objects (hardlink) [ 0 .. 15001 ] items unique

Assignments list.

required
Array of objects (trip) [ 0 .. 15001 ] items unique

Existing routes.

object (facts)

Events that have taken place.

Array of objects (routing_transport_matrix_list) [ 0 .. 12 ] items unique

Time and distance matrices list for each transport type from dataset. By specifying an external routing matrix external_routing, parameters geo_settings are not used.

object (actualize_settings)

Actualize settings.

dataset_name
string (dataset_name) [ 0 .. 1000 ] characters

The name of the dataset. A technical field that does not affect planning.

Responses

Response Schema: application/json
required
object (tracedata)

Data for request tracing.

required
Array of objects (entity_warning_list) [ 0 .. 15001 ] items

Warning list.

Request samples

Content type
application/json
{
  • "locations": [
    ],
  • "orders": [
    ],
  • "performers": [
    ],
  • "transports": [
    ],
  • "hardlinks": [
    ],
  • "trips": [
    ],
  • "facts": {
    },
  • "external_routing": [ ],
  • "actualize_settings": {
    },
  • "dataset_name": "custom_dataset_one"
}

Response samples

Content type
application/json
{
  • "tracedata": {
    },
  • "warnings": [
    ]
}

Data refine

Refine data before using.

Authorizations:
ApiKeyAuth
Request Body schema: application/json
required

Data for refine.

required
Array of objects (location) [ 1 .. 15001 ] items unique

List of locations used for orders and shifts.

required
Array of objects (order) [ 1 .. 15001 ] items unique

Orders list.

required
Array of objects (performer) [ 1 .. 15001 ] items unique

Available performers list.

required
Array of objects (transport) [ 1 .. 15001 ] items unique

Available transports list.

Array of objects (hardlink) [ 0 .. 15001 ] items unique

Assignments list.

required
Array of objects (trip) [ 0 .. 15001 ] items unique

Existing routes.

object (facts)

Events that have taken place.

Array of objects (routing_transport_matrix_list) [ 0 .. 12 ] items unique

Time and distance matrices list for each transport type from dataset. By specifying an external routing matrix external_routing, parameters geo_settings are not used.

object (actualize_settings)

Actualize settings.

dataset_name
string (dataset_name) [ 0 .. 1000 ] characters

The name of the dataset. A technical field that does not affect planning.

Responses

Response Schema: application/json
required
Array of objects (location) [ 1 .. 15001 ] items unique

List of locations used for orders and shifts.

required
Array of objects (order) [ 1 .. 15001 ] items unique

Orders list.

required
Array of objects (performer) [ 1 .. 15001 ] items unique

Available performers list.

required
Array of objects (transport) [ 1 .. 15001 ] items unique

Available transports list.

Array of objects (hardlink) [ 0 .. 15001 ] items unique

Assignments list.

required
Array of objects (trip) [ 0 .. 15001 ] items unique

Existing routes.

object (facts)

Events that have taken place.

Array of objects (routing_transport_matrix_list) [ 0 .. 12 ] items unique

Time and distance matrices list for each transport type from dataset. By specifying an external routing matrix external_routing, parameters geo_settings are not used.

object (actualize_settings)

Actualize settings.

dataset_name
string (dataset_name) [ 0 .. 1000 ] characters

The name of the dataset. A technical field that does not affect planning.

Request samples

Content type
application/json
{
  • "locations": [
    ],
  • "orders": [
    ],
  • "performers": [
    ],
  • "transports": [
    ],
  • "trips": [
    ]
}

Response samples

Content type
application/json
{
  • "locations": [
    ],
  • "orders": [
    ],
  • "performers": [
    ],
  • "transports": [
    ],
  • "hardlinks": [
    ],
  • "trips": [
    ],
  • "facts": {
    },
  • "external_routing": [ ],
  • "actualize_settings": {
    },
  • "dataset_name": "custom_dataset_one"
}

Replan

Replanning - creation of new trips based on existing trips, taking into account the facts.

Replanning takes place in three stages - checking, applying facts and creating restrictions for planning based on existing trips, planning.

Replanning (SYNC)

Trips replanning - changing existing and creating new trips based on the facts and data about orders, performers and transport.

Authorizations:
ApiKeyAuth
Request Body schema: application/json
required

New replanning request.

required
Array of objects (location) [ 1 .. 15001 ] items unique

List of locations used for orders and shifts.

required
Array of objects (order) [ 1 .. 15001 ] items unique

Orders list.

required
Array of objects (performer) [ 1 .. 15001 ] items unique

Available performers list.

required
Array of objects (transport) [ 1 .. 15001 ] items unique

Available transports list.

Array of objects (hardlink) [ 0 .. 15001 ] items unique
Default: []

Assignments list.

required
Array of objects (trip) [ 0 .. 15001 ] items unique

Existing routes.

object (facts)

Events that have taken place.

Array of objects (routing_transport_matrix_list) [ 0 .. 12 ] items unique

Time and distance matrices list for each transport type from dataset. By specifying an external routing matrix external_routing, parameters geo_settings are not used.

object (replan_settings)

Replanning settings.

dataset_name
string (dataset_name) [ 0 .. 1000 ] characters

The name of the dataset. A technical field that does not affect planning.

Responses

Response Schema: application/json
required
object (tracedata)

Data for request tracing.

required
Array of objects (trip) [ 0 .. 15001 ] items unique
Default: []

Schedule of trips assigned to performers.

required
object or null (plan_statistics)

General statistics on planned trips.

Array of objects (entity_warning_list) [ 0 .. 15001 ] items

Warning list.

object (unplanned_items)

Unplanned items list.

progress
required
integer<int32> (calculation_progress) [ 0 .. 100 ]

Calculation progress as a percentage. The progress displays the current number of completed steps.

required
object (calculation_info)

Calculation information.

Request samples

Content type
application/json
{
  • "locations": [
    ],
  • "orders": [
    ],
  • "performers": [
    ],
  • "transports": [
    ],
  • "trips": [
    ]
}

Response samples

Content type
application/json
{
  • "tracedata": {
    },
  • "trips": [
    ],
  • "statistics": {
    },
  • "progress": 100,
  • "info": {
    },
  • "warnings": [ ],
  • "unplanned_items": {
    }
}

Replanning (ASYNC)

Trip replanning - changing existing and creating new trips based on the facts and data about orders, performers and transport. The result can be obtained using the result method, removing - with delete.

Authorizations:
ApiKeyAuth
Request Body schema: application/json
required

Launching the asynchronous replanning.

required
Array of objects (location) [ 1 .. 15001 ] items unique

List of locations used for orders and shifts.

required
Array of objects (order) [ 1 .. 15001 ] items unique

Orders list.

required
Array of objects (performer) [ 1 .. 15001 ] items unique

Available performers list.

required
Array of objects (transport) [ 1 .. 15001 ] items unique

Available transports list.

Array of objects (hardlink) [ 0 .. 15001 ] items unique
Default: []

Assignments list.

required
Array of objects (trip) [ 0 .. 15001 ] items unique

Existing routes.

object (facts)

Events that have taken place.

Array of objects (routing_transport_matrix_list) [ 0 .. 12 ] items unique

Time and distance matrices list for each transport type from dataset. By specifying an external routing matrix external_routing, parameters geo_settings are not used.

object (replan_settings)

Replanning settings.

dataset_name
string (dataset_name) [ 0 .. 1000 ] characters

The name of the dataset. A technical field that does not affect planning.

Responses

Response Schema: application/json
required
object (tracedata)

Data for request tracing.

id
required
string<uuid> (calculation_id)

Calculation identifier.

Request samples

Content type
application/json
{
  • "locations": [
    ],
  • "orders": [
    ],
  • "performers": [
    ],
  • "transports": [
    ],
  • "trips": [
    ]
}

Response samples

Content type
application/json
{
  • "tracedata": {
    },
  • "id": "11111111-2222-3333-4444-555555555555"
}

Calculation state

Read calculation state by the calculation identifier.

Authorizations:
ApiKeyAuth
path Parameters
id
required
string<uuid> (calculation_id)
Example: 11111111-2222-3333-4444-555555555555

计算标识符

Responses

Response Schema: application/json
required
object (tracedata)

Data for request tracing.

progress
required
integer<int32> (calculation_progress) [ 0 .. 100 ]

Calculation progress as a percentage. The progress displays the current number of completed steps.

required
object (calculation_info)

Calculation information.

Response samples

Content type
application/json
{
  • "tracedata": {
    },
  • "progress": 52,
  • "info": {
    }
}

Cancel calculation

Cancel calculation by the calculation identifier.

Authorizations:
ApiKeyAuth
path Parameters
id
required
string<uuid> (calculation_id)
Example: 11111111-2222-3333-4444-555555555555

计算标识符

Responses

Response samples

Content type
application/json
{
  • "tracedata": {
    },
  • "message": "logical",
  • "schema_errors": [ ],
  • "logical_errors": [
    ],
  • "warnings": [ ]
}

Getting the result

Getting the replanning result based on the calculation identifier.

Authorizations:
ApiKeyAuth
path Parameters
id
required
string<uuid> (calculation_id)
Example: 11111111-2222-3333-4444-555555555555

计算标识符

Responses

Response Schema: application/json
required
object (tracedata)

Data for request tracing.

required
Array of objects (trip) [ 0 .. 15001 ] items unique
Default: []

Schedule of trips assigned to performers.

required
object or null (plan_statistics)

General statistics on planned trips.

Array of objects (entity_warning_list) [ 0 .. 15001 ] items

Warning list.

object (unplanned_items)

Unplanned items list.

progress
required
integer<int32> (calculation_progress) [ 0 .. 100 ]

Calculation progress as a percentage. The progress displays the current number of completed steps.

required
object (calculation_info)

Calculation information.

Response Schema: application/json
required
object (tracedata)

Data for request tracing.

required
Array of objects (trip) [ 0 .. 15001 ] items unique
Default: []

Schedule of trips assigned to performers.

required
object or null (plan_statistics)

General statistics on planned trips.

Array of objects (entity_warning_list) [ 0 .. 15001 ] items

Warning list.

object (unplanned_items)

Unplanned items list.

progress
required
integer<int32> (calculation_progress) [ 0 .. 100 ]

Calculation progress as a percentage. The progress displays the current number of completed steps.

required
object (calculation_info)

Calculation information.

Response samples

Content type
application/json
{
  • "tracedata": {
    },
  • "trips": [
    ],
  • "statistics": {
    },
  • "progress": 100,
  • "info": {
    },
  • "warnings": [ ],
  • "unplanned_items": {
    }
}

Result removal

Removal of the planning result by the calculation identifier.

Authorizations:
ApiKeyAuth
path Parameters
id
required
string<uuid> (calculation_id)
Example: 11111111-2222-3333-4444-555555555555

计算标识符

Responses

Response samples

Content type
application/json
{
  • "tracedata": {
    },
  • "message": "logical",
  • "schema_errors": [ ],
  • "logical_errors": [
    ],
  • "warnings": [ ]
}

Data validation

Check data before using.

Authorizations:
ApiKeyAuth
Request Body schema: application/json
required

Data for validation.

required
Array of objects (location) [ 1 .. 15001 ] items unique

List of locations used for orders and shifts.

required
Array of objects (order) [ 1 .. 15001 ] items unique

Orders list.

required
Array of objects (performer) [ 1 .. 15001 ] items unique

Available performers list.

required
Array of objects (transport) [ 1 .. 15001 ] items unique

Available transports list.

Array of objects (hardlink) [ 0 .. 15001 ] items unique
Default: []

Assignments list.

required
Array of objects (trip) [ 0 .. 15001 ] items unique

Existing routes.

object (facts)

Events that have taken place.

Array of objects (routing_transport_matrix_list) [ 0 .. 12 ] items unique

Time and distance matrices list for each transport type from dataset. By specifying an external routing matrix external_routing, parameters geo_settings are not used.

object (replan_settings)

Replanning settings.

dataset_name
string (dataset_name) [ 0 .. 1000 ] characters

The name of the dataset. A technical field that does not affect planning.

Responses

Response Schema: application/json
required
object (tracedata)

Data for request tracing.

required
Array of objects (entity_warning_list) [ 0 .. 15001 ] items

Warning list.

Request samples

Content type
application/json
{
  • "locations": [
    ],
  • "orders": [
    ],
  • "performers": [
    ],
  • "transports": [
    ],
  • "trips": [
    ]
}

Response samples

Content type
application/json
{
  • "tracedata": {
    },
  • "warnings": [
    ]
}

Data refine

Refine data before using.

Authorizations:
ApiKeyAuth
Request Body schema: application/json
required

Data for refine.

required
Array of objects (location) [ 1 .. 15001 ] items unique

List of locations used for orders and shifts.

required
Array of objects (order) [ 1 .. 15001 ] items unique

Orders list.

required
Array of objects (performer) [ 1 .. 15001 ] items unique

Available performers list.

required
Array of objects (transport) [ 1 .. 15001 ] items unique

Available transports list.

Array of objects (hardlink) [ 0 .. 15001 ] items unique
Default: []

Assignments list.

required
Array of objects (trip) [ 0 .. 15001 ] items unique

Existing routes.

object (facts)

Events that have taken place.

Array of objects (routing_transport_matrix_list) [ 0 .. 12 ] items unique

Time and distance matrices list for each transport type from dataset. By specifying an external routing matrix external_routing, parameters geo_settings are not used.

object (replan_settings)

Replanning settings.

dataset_name
string (dataset_name) [ 0 .. 1000 ] characters

The name of the dataset. A technical field that does not affect planning.

Responses

Response Schema: application/json
required
Array of objects (location) [ 1 .. 15001 ] items unique

List of locations used for orders and shifts.

required
Array of objects (order) [ 1 .. 15001 ] items unique

Orders list.

required
Array of objects (performer) [ 1 .. 15001 ] items unique

Available performers list.

required
Array of objects (transport) [ 1 .. 15001 ] items unique

Available transports list.

Array of objects (hardlink) [ 0 .. 15001 ] items unique
Default: []

Assignments list.

required
Array of objects (trip) [ 0 .. 15001 ] items unique

Existing routes.

object (facts)

Events that have taken place.

Array of objects (routing_transport_matrix_list) [ 0 .. 12 ] items unique

Time and distance matrices list for each transport type from dataset. By specifying an external routing matrix external_routing, parameters geo_settings are not used.

object (replan_settings)

Replanning settings.

dataset_name
string (dataset_name) [ 0 .. 1000 ] characters

The name of the dataset. A technical field that does not affect planning.

Request samples

Content type
application/json
{
  • "locations": [
    ],
  • "orders": [
    ],
  • "performers": [
    ],
  • "transports": [
    ],
  • "hardlinks": [ ],
  • "trips": [
    ],
  • "facts": {
    },
  • "external_routing": [ ],
  • "replan_settings": {
    },
  • "dataset_name": "custom_dataset_one"
}

Response samples

Content type
application/json
{
  • "locations": [
    ],
  • "orders": [
    ],
  • "performers": [
    ],
  • "transports": [
    ],
  • "hardlinks": [ ],
  • "trips": [
    ],
  • "facts": {
    },
  • "external_routing": [ ],
  • "replan_settings": {
    },
  • "dataset_name": "custom_dataset_one"
}

Convert

数据转换。

JSON >> XLSX

Used for conversion of input and output data to the VRt.Universal XLSX format.

Authorizations:
ApiKeyAuth
Request Body schema: application/json
required

Conversion request to the XLSX.

Array of objects (location) [ 0 .. 15001 ] items unique

List of locations used for orders and shifts.

Array of objects (order) [ 0 .. 15001 ] items unique

Orders list.

Array of objects (performer) [ 0 .. 15001 ] items unique

Available performers list.

Array of objects (transport) [ 0 .. 15001 ] items unique

Available transports list.

Array of objects (hardlink) [ 0 .. 15001 ] items unique

Assignments list.

Array of objects (trip) [ 0 .. 15001 ] items unique

Existing routes.

object (facts)

Events that have taken place.

object or null (plan_statistics)

General statistics on planned trips.

Array of objects (routing_transport_matrix_list) [ 0 .. 12 ] items unique

Time and distance matrices list for each transport type from dataset. By specifying an external routing matrix external_routing, parameters geo_settings are not used.

object (plan_settings)

Planning settings.

object (replan_settings)

Replanning settings.

object (actualize_settings)

Actualize settings.

dataset_name
string (dataset_name) [ 0 .. 1000 ] characters

The name of the dataset. A technical field that does not affect planning.

Responses

Response Schema: application/octet-stream
string<byte> (file_xlsx)

File with data in XLSX format.

Request samples

Content type
application/json
{
  • "locations": [
    ],
  • "orders": [
    ],
  • "performers": [
    ],
  • "transports": [
    ],
  • "trips": [
    ]
}

Response samples

Content type
application/json
{
  • "tracedata": {
    },
  • "message": "logical",
  • "schema_errors": [ ],
  • "logical_errors": [
    ],
  • "warnings": [ ]
}

XLSX >> JSON

Used for data conversion from the VRt.Universal XLSX format to the VRt.Universal JSON format.

Authorizations:
ApiKeyAuth
Request Body schema: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
required

Conversion request to the JSON format.

string<byte> (file_xlsx)

File with data in XLSX format.

Responses

Response Schema: application/json
Array of objects (location) [ 0 .. 15001 ] items unique

List of locations used for orders and shifts.

Array of objects (order) [ 0 .. 15001 ] items unique

Orders list.

Array of objects (performer) [ 0 .. 15001 ] items unique

Available performers list.

Array of objects (transport) [ 0 .. 15001 ] items unique

Available transports list.

Array of objects (hardlink) [ 0 .. 15001 ] items unique

Assignments list.

Array of objects (trip) [ 0 .. 15001 ] items unique

Existing routes.

object (facts)

Events that have taken place.

object or null (plan_statistics)

General statistics on planned trips.

Array of objects (routing_transport_matrix_list) [ 0 .. 12 ] items unique

Time and distance matrices list for each transport type from dataset. By specifying an external routing matrix external_routing, parameters geo_settings are not used.

object (plan_settings)

Planning settings.

object (replan_settings)

Replanning settings.

object (actualize_settings)

Actualize settings.

dataset_name
string (dataset_name) [ 0 .. 1000 ] characters

The name of the dataset. A technical field that does not affect planning.

Response samples

Content type
application/json
{
  • "locations": [
    ],
  • "orders": [
    ],
  • "performers": [
    ],
  • "transports": [
    ],
  • "hardlinks": [
    ],
  • "trips": [
    ],
  • "facts": {
    },
  • "statistics": {
    },
  • "external_routing": [ ],
  • "plan_settings": {
    },
  • "replan_settings": {
    },
  • "actualize_settings": {
    },
  • "dataset_name": "custom_dataset_one"
}

JSON >> THRIFT

Used for conversion of input data to the THRIFT format.

Authorizations:
ApiKeyAuth
Request Body schema: application/json
required

Conversion request to the THRIFT.

Array of objects (location) [ 0 .. 15001 ] items unique

List of locations used for orders and shifts.

Array of objects (order) [ 0 .. 15001 ] items unique

Orders list.

Array of objects (performer) [ 0 .. 15001 ] items unique

Available performers list.

Array of objects (transport) [ 0 .. 15001 ] items unique

Available transports list.

Array of objects (hardlink) [ 0 .. 15001 ] items unique

Assignments list.

Array of objects (trip) [ 0 .. 15001 ] items unique

Existing routes.

object (facts)

Events that have taken place.

object or null (plan_statistics)

General statistics on planned trips.

Array of objects (routing_transport_matrix_list) [ 0 .. 12 ] items unique

Time and distance matrices list for each transport type from dataset. By specifying an external routing matrix external_routing, parameters geo_settings are not used.

object (plan_settings)

Planning settings.

object (replan_settings)

Replanning settings.

object (actualize_settings)

Actualize settings.

dataset_name
string (dataset_name) [ 0 .. 1000 ] characters

The name of the dataset. A technical field that does not affect planning.

Responses

Response Schema: text/plain
string (file_text)

File with data in text format.

Request samples

Content type
application/json
{
  • "locations": [
    ],
  • "orders": [
    ],
  • "performers": [
    ],
  • "transports": [
    ],
  • "trips": [
    ]
}

Response samples

Content type
application/json
{
  • "tracedata": {
    },
  • "message": "logical",
  • "schema_errors": [ ],
  • "logical_errors": [
    ],
  • "warnings": [ ]
}

System

系统功能。 所有服务共有的辅助功能。

检查服务可用性

检查服务可用性。

Responses

Response Schema: application/json
health
required
number<double> [ 0 .. 1 ]

Current health.

Response samples

Content type
application/json
{
  • "health": 0.999
}

获取服务版本

获取服务版本。

Responses

Response Schema: application/json
major
required
integer<int32> [ 1 .. 100 ]

产品版本。 在单个版本中,保证了服务之间通用数据结构的兼容性。 版本更改表示与以前版本的产品(和所有服务)不兼容的更改。

minor
required
integer<int32> [ 0 .. 111 ]

服务的小版本。 版本更改表示新功能。 该更新向后兼容服务的主要版本。

build
required
string [ 1 .. 64 ] characters

构建版本。 包含向后兼容的错误修复和文档更新。

Response samples

Content type
application/json
{
  • "major": 4,
  • "minor": 4,
  • "build": "1754RC"
}

检查服务可用性

检查服务可用性。

path Parameters
filename
required
string [ 6 .. 128 ] characters
Example: file_en.html

File name.

Responses

Response Schema:
string (file_html)

File with data in HTML format.

Response samples

Content type
application/json
{
  • "resource_id": "resource_id",
  • "detail": {
    }
}