Asendia · Schema

GenericPreProcessParcelRequest

CompanyShippingLogisticsParcelCross-border eCommerceTrackingPostal

Properties

Name Type Description
trackingNumber stringnull The tracking number belonging to the parcel preprocessed with DWS Only 1 tracking number per API request
processingLocation stringnull The Asendia's location where the physical package will be processed. If null, the processing location from API account settings will be used (BR-1-3) Examples: SIN(Singapore), HON(Hong Kong), AUS(Aust
totalPackageWeight number The parcel’s actual weight for the given weightUnit
weightUnit object The package's unit of weight
dimLength numbernull The package's dimensional length
dimWidth numbernull The package's dimensional width
dimHeight numbernull The package's dimensional height
dimUnit object The package's dimensional unit. IMPORTANT (BR-1-4): For APAC DWS machines, this can be null. When null, dimensions are assumed to be in MM and will be automatically converted to CM by dividing by 10.
machineId stringnull Unique identifier for the DWS machine (BR-5-3) Will be stored as Scale ID in the system
View JSON Schema on GitHub

JSON Schema

asendia-generic-pre-process-parcel-request-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/asendia/main/json-schema/asendia-generic-pre-process-parcel-request-schema.json",
  "title": "GenericPreProcessParcelRequest",
  "x-generated": "2026-10-13",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/asendia-a1-dws-openapi.yml#/components/schemas/GenericPreProcessParcelRequest",
  "type": "object",
  "properties": {
    "trackingNumber": {
      "type": [
        "string",
        "null"
      ],
      "description": "The tracking number belonging to the parcel preprocessed with DWS\r\nOnly 1 tracking number per API request"
    },
    "processingLocation": {
      "type": [
        "string",
        "null"
      ],
      "description": "The Asendia's location where the physical package will be processed.\r\nIf null, the processing location from API account settings will be used (BR-1-3)\r\nExamples: SIN(Singapore), HON(Hong Kong), AUS(Australia) and NEW(New Zealand)."
    },
    "totalPackageWeight": {
      "type": "number",
      "description": "The parcel’s actual weight for the given weightUnit",
      "format": "double"
    },
    "weightUnit": {
      "allOf": [
        {
          "$ref": "#/$defs/weightUnitEnum"
        }
      ],
      "description": "The package's unit of weight"
    },
    "dimLength": {
      "type": [
        "number",
        "null"
      ],
      "description": "The package's dimensional length",
      "format": "double"
    },
    "dimWidth": {
      "type": [
        "number",
        "null"
      ],
      "description": "The package's dimensional width",
      "format": "double"
    },
    "dimHeight": {
      "type": [
        "number",
        "null"
      ],
      "description": "The package's dimensional height",
      "format": "double"
    },
    "dimUnit": {
      "allOf": [
        {
          "$ref": "#/$defs/dimUnitEnum"
        }
      ],
      "description": "The package's dimensional unit.\r\nIMPORTANT (BR-1-4): For APAC DWS machines, this can be null.\r\nWhen null, dimensions are assumed to be in MM and will be automatically converted to CM by dividing by 10.",
      "nullable": true
    },
    "machineId": {
      "type": [
        "string",
        "null"
      ],
      "description": "Unique identifier for the DWS machine (BR-5-3)\r\nWill be stored as Scale ID in the system"
    }
  },
  "additionalProperties": false,
  "$defs": {
    "dimUnitEnum": {
      "enum": [
        "IN",
        "CM",
        "MM"
      ],
      "type": "string"
    },
    "weightUnitEnum": {
      "enum": [
        "Lb",
        "Kg"
      ],
      "type": "string"
    }
  }
}

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/asendia-generic-pre-process-parcel-request"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.