Wireframe with example data. Nothing on these pages reads a live service.

Back to search CHED · production

GBCHED.2026.0001234

Status
Valid
TRACES status code
16
Last updated
18 Nov 2026, 09:38:44 UTC
Origin
Received from TRACES
Commodities
1 line · 1,240.5 kg

Data source: GET /certificates/cheds/{id} returns the mapped profile only. There is no XML endpoint and no original-envelope capture.

View published events for this reference

Warning A forced republish of an unchanged CHED is deduplicated by the FIFO stream and can return 200 without anything being republished. Show the outcome from the consumer, not the route status.

Record

Contents

{
      "id": "GBCHED.2026.0001234",
      "statusCode": "16",
      "updated": "2026-11-18T09:38:44Z",
      "commodities": [
        { "code": "0101210000", "netMass": 1240.5, "unit": "KGM" }
      ],
      "documents": ["C640"]
    }
Not buildable yet

TRACES returns SOAP and the gateway maps it on the way in. Capturing the original envelope is a new gateway capability (store-the-raw-request), not a UI change — this tab stays empty until that exists.

Attachments are asynchronous: the first request answers 202 with Retry-After, and a later request returns the file.

Document Status Size Retrieved
C640 — certificate.pdf Available 412 KB 18 Nov 2026, 09:40
C678 — lab-report.pdf Pending — Retry in 15 minutes

PDF only, virus scanned, 180-day retention, 15-minute retry on non-scan failures.

Data source: GET /certificates/cheds/{id}/attachments follows the 202-then-200 pattern. Failure codes: CHED_NOT_FOUND, ATTACHMENT_NOT_FOUND, TRACES_PERMISSION_DENIED, UNSUPPORTED_FILE_TYPE, FILE_VIRUS, FILE_EMPTY, FILE_TOO_LARGE, FILE_INVALID_TYPE, TRACES_UNAVAILABLE, UPLOAD_FAILED.