All issues

Search results

Nine cross-field business rules are documented in prose but absent from the schema, so generated clients cannot enforce them

Status: Open.

#280 In DEFRA/waste-tracking-service;

· fabio-rovai opened on Aug 28, 2026

Five reference-data vocabularies are bound to request fields only in prose, so no client can enforce them

Status: Open.

#279 In DEFRA/waste-tracking-service;

· fabio-rovai opened on Aug 28, 2026

Six examples in ReceiptAPI.yml are rejected by the schema that declares them

Status: Open.

#278 In DEFRA/waste-tracking-service;

· fabio-rovai opened on Aug 28, 2026

pops.components[].code and hazardous.components[].name are listed in required: but documented as "Optional field"

Status: Open.

#271 In DEFRA/waste-tracking-service;

· ilovegithub2 opened on Aug 16, 2026

Sending a receipt of waste without the "carrier" object causes a HTTP 500 response

Status: Open.

#270 In DEFRA/waste-tracking-service;

· patrickfegan opened on Aug 14, 2026

Integration Environment enforces undocumented 'submitingOrganisation' business rule on PUT; spec changes not reflected in changelog

Status: Open.

#266 In DEFRA/waste-tracking-service;

· AWDMcIntyre opened on Aug 11, 2026

Error message key for hazCodes not full path

Status: Open.

#255 In DEFRA/waste-tracking-service;

· TGRHavoc opened on Jul 9, 2026

DWT Production validation error for Hazardous consignment notes

Status: Open.

#230 In DEFRA/waste-tracking-service;

· DsposalTom opened on May 11, 2026

Markdown Tables incorrectly formatted

Status: Open.

#227 In DEFRA/waste-tracking-service;

· DsposalTom opened on May 1, 2026

Some string fields not properly validated

Status: Open.

#224 In DEFRA/waste-tracking-service;

· TGRHavoc opened on Apr 23, 2026

reasonForNoConsignmentCode should return validation error when an incorrect value is sent

Status: Open.

#204 In DEFRA/waste-tracking-service;

· carlaor007 opened on Mar 6, 2026