Kibo Commerce · Schema

Job Queue Response

Response for getting a job

CompanyCommerceE-CommerceHeadless CommerceOrder ManagementB2BConsumerInventoryFulfillment

Properties

Name Type Description
added string Time and date the job was added to the queue in ISO8601 format in UTC
finished string Time and date the job was finished in ISO8601 format in UTC
hasData boolean True if the job was not created from a fetched file
itemCount integer The number of items processed, only for job types REFRESH and ADJUST
jobID integer Internal identifier that uniquely identifies a single job
locationCode string Unique internal Identifier of the owning location
messages array List of messages
numResults integer Number of results
originalFilename string 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
started string Time and date the job was started in ISO8601 format in UTC
status string Current status of job completion
success boolean Flag for success
tenantID integer Unique internal identifier of the tenant that owns the job
type string Purpose of the job
View JSON Schema on GitHub

JSON Schema

kibo-commerce-job-queue-response-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/kibo-commerce/main/json-schema/kibo-commerce-job-queue-response-schema.json",
  "title": "Job Queue Response",
  "description": "Response for getting a job",
  "x-generated": "2026-10-18",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/kibo-commerce-inventory-openapi.yml#/components/schemas/JobQueueResponse",
  "properties": {
    "added": {
      "description": "Time and date the job was added to the queue in ISO8601 format in UTC",
      "type": "string"
    },
    "finished": {
      "description": "Time and date the job was finished in ISO8601 format in UTC",
      "type": "string"
    },
    "hasData": {
      "description": "True if the job was not created from a fetched file",
      "type": "boolean"
    },
    "itemCount": {
      "description": "The number of items processed, only for job types REFRESH and ADJUST",
      "type": "integer"
    },
    "jobID": {
      "description": "Internal identifier that uniquely identifies a single job",
      "type": "integer"
    },
    "locationCode": {
      "description": "Unique internal Identifier of the owning location",
      "type": "string"
    },
    "messages": {
      "description": "List of messages",
      "items": {
        "type": "string"
      },
      "type": "array"
    },
    "numResults": {
      "description": "Number of results",
      "type": "integer"
    },
    "originalFilename": {
      "description": "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",
      "type": "string"
    },
    "started": {
      "description": "Time and date the job was started in ISO8601 format in UTC",
      "type": "string"
    },
    "status": {
      "description": "Current status of job completion",
      "enum": [
        "PENDING",
        "WORKING",
        "SUCCESS",
        "FAILED"
      ],
      "type": "string"
    },
    "success": {
      "description": "Flag for success",
      "type": "boolean"
    },
    "tenantID": {
      "description": "Unique internal identifier of the tenant that owns the job",
      "type": "integer"
    },
    "type": {
      "description": "Purpose of the job",
      "enum": [
        "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"
      ],
      "type": "string"
    }
  },
  "type": "object"
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/kibo-commerce-job-queue-response"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.