A valid request URL is required to generate request examples[
{
"jobID": 123,
"tenantID": 123,
"locationCode": "<string>",
"type": "REFRESH",
"added": "<string>",
"started": "<string>",
"finished": "<string>",
"originalFilename": "<string>",
"hasData": true,
"itemCount": 123,
"status": "PENDING",
"success": true,
"messages": [
"<string>"
],
"numResults": 123
}
]Create jobs to redistribute inventory across tags for the given tenant
A valid request URL is required to generate request examples[
{
"jobID": 123,
"tenantID": 123,
"locationCode": "<string>",
"type": "REFRESH",
"added": "<string>",
"started": "<string>",
"finished": "<string>",
"originalFilename": "<string>",
"hasData": true,
"itemCount": 123,
"status": "PENDING",
"success": true,
"messages": [
"<string>"
],
"numResults": 123
}
]JWT Authorization header using the Bearer scheme.
Success
Internal identifier that uniquely identifies a single job
Unique internal identifier of the tenant that owns the job
Unique internal Identifier of the owning location
Purpose of the job
REFRESH, ADJUST, RELEASE_SHIPMENTS, CREATE_PICK_WAVE, CLOSE_PICK_WAVE, PUT_AWAY_FILE, SHORT_PICK_ERROR, BIN_AUDIT_START, BIN_AUDIT_COMPLETION, CREATE_BIN_AUDIT, RELEASE_PENDING_ITEMS, ALLOCATE, DEALLOCATE, FULFILL, DELETE Time and date the job was added to the queue in ISO8601 format in UTC
Time and date the job was started in ISO8601 format in UTC
Time and date the job was finished in ISO8601 format in UTC
The full name of the file that was picked up at the secure droppoint server before being split up by location. Applies only to refresh and adjust jobs created via file fetch process
True if the job was not created from a fetched file
The number of items processed, only for job types REFRESH and ADJUST
Current status of job completion
PENDING, WORKING, SUCCESS, FAILED Flag for success
List of messages
Number of results