-
Notifications
You must be signed in to change notification settings - Fork 5
/
Asset_tracking.dtd
23 lines (23 loc) · 1.3 KB
/
Asset_tracking.dtd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
{
"$schema": "http://json-schema.org/draft-04/schema#",
"id": "https://github.com/route4me/route4me-json-schemas/blob/master/Asset_tracking.dtd",
"title": "Asset tracking",
"type": "object",
"description": "A user has many assets (such as a package) that they must deliver. The user uploads a list of generated tracking numbers, and the corresponding delivery address and Route4Me creates one or more delivery routes. As packages are added to each batch, the routes are re-balanced until all the packages have been added into the system. Now that all the tracking numbers are in the system, the user needs to label and sequence each package. Doing it by hand is tedious, because they don't know which route each package goes on. By re-scanning each package manually, or on a conveyor, the client application will automatically output the route ID and the sequence number in the route that the package is found in, by querying the system with the package's unique ID. url: https://route4me.com/api.v4/status.php",
"required": [
"api_key",
"tracking"
],
"properties": {
"api_key": {
"type": "string",
"title": "Api key",
"descrption": "The API key of the application client"
},
"tracking": {
"type": "string",
"title": "Tracking",
"descrption": "The ID of the asset that is being located"
}
}
}