# HALOWERK Delivery Note XML to JSON Converter

> HALOWERK Delivery Note XML to JSON Converter is a paid API for AI agents from handel.halowerk.com, paid per call via x402, $0.004/call, status unknown (last checked 2026-10-12).

Converts a UBL/XML delivery note document into a structured JSON representation

## Facts

- Endpoint: POST https://handel.halowerk.com/v1/delivery-note-json?utm_source=zero.xyz
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-delivery-note-xml-to-json-converter-dfc04922
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_3C71ytNnxjyzXguIVQ4R1

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability halowerk-delivery-note-xml-to-json-converter-dfc04922 -d '<json body>'
```

Example prompt: Convert this XML delivery note into JSON for me — here's the full XML string: [paste your UBL delivery note XML here].

## When to prefer this

Use this endpoint when you need to programmatically convert UBL or similar XML-formatted delivery notes into JSON — particularly in supply chain, logistics, or ERP integration workflows where downstream systems expect JSON. Prefer this over manual parsing or generic XML-to-JSON tools when the source document is a delivery/despatch note and you want semantically meaningful field mapping rather than raw XML mirroring.

## Known failure modes

- Invalid or malformed XML returns a parsing error
- XML shorter than 20 characters rejected by schema validation
- XML longer than 100,000 characters rejected as too large
- Non-delivery-note XML (e.g. invoices or orders) may return incomplete or mismatched JSON fields
- Missing payment via x402 returns HTTP 402 Payment Required

## How this service works

Adds structured delivery-note extraction alongside the existing invoice extractor and purchase-order matcher; does not duplicate invoice-extract or filing-to-json. Strict namespace-aware XML parsing, no model or foreign API. Only supplied source fields are returned; optional fields are null. Validates extraction bounds, dates, unique line IDs and decimal quantities, but does not claim full UBL XSD or legal conformity. No invoice, PDF or OCR support.

## Output

Returns a JSON object representing the parsed delivery note, with structured fields extracted from the UBL/XML input — including delivery identifiers, line items, quantities, parties (consignor/consignee), dates, and shipment references.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "xml": {
   "type": "string",
   "maxLength": 100000,
   "minLength": 20
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-delivery-note-xml-to-json-converter-dfc04922/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from handel.halowerk.com](https://www.zero.xyz/host/handel.halowerk.com/llms.txt)