Summary
We are integrating dangerous goods shipping (ground, EU, ADR, Limited Quantity)
via the Shipping API using Request.SubVersion 1807. Our Shipping request is
rejected with:
127160: Missing or Invalid ChemicalRecordIdentifier
on PackageServiceOptionsHazMat.ChemicalRecordIdentifier. Per the schema this
field is mandatory from SubVersion 1701 onwards, so lowering the SubVersion is
not an option for us (we need it for correct Limited Quantity handling).
What we already understand
- The Dangerous Goods API (Chemical Reference Data / Acceptance Audit Precheck)
consumes a ChemicalRecordIdentifier as input but does not create one. - The DangerousGoods spec states the account/ShipperNumber must have a valid
Dangerous Goods contract to use these endpoints. - We could not find any REST endpoint to create a new Chemical Record; the
traditional path appears to be the WorldShip Dangerous Goods Chemical Record
Editor.
Our questions
How does one obtain a valid ChemicalRecordIdentifier for testing a DG
Shipping call in the CIE sandbox (wwwcie.ups.com)? Is there a documented
sandbox test value or a supported way to create a Chemical Record without
WorldShip?
In an OAuth Authorization Code flow, where the end customer authorizes our
application with their own DG-enabled UPS account: is the customer account's
ChemicalRecordIdentifier accepted for the Shipping call, or must our own
integration account additionally hold a Dangerous Goods contract?
Is there any minimal working JSON example of a DG Shipping request
(SubVersion 1807, ADR, Limited Quantity) that populates
PackageServiceOptionsHazMat correctly?
Environment
- API: Shipping API (+ Dangerous Goods API)
- Environment: CIE / sandbox (wwwcie.ups.com)
- Request.SubVersion: 1807
- Scenario: Ground, EU-to-EU, ADR, Limited Quantity
- Error: 127160 Missing or Invalid ChemicalRecordIdentifier
Thanks in advance.
Summary
We are integrating dangerous goods shipping (ground, EU, ADR, Limited Quantity)
via the Shipping API using Request.SubVersion 1807. Our Shipping request is
rejected with:
127160: Missing or Invalid ChemicalRecordIdentifier
on PackageServiceOptionsHazMat.ChemicalRecordIdentifier. Per the schema this
field is mandatory from SubVersion 1701 onwards, so lowering the SubVersion is
not an option for us (we need it for correct Limited Quantity handling).
What we already understand
consumes a ChemicalRecordIdentifier as input but does not create one.
Dangerous Goods contract to use these endpoints.
traditional path appears to be the WorldShip Dangerous Goods Chemical Record
Editor.
Our questions
How does one obtain a valid ChemicalRecordIdentifier for testing a DG
Shipping call in the CIE sandbox (wwwcie.ups.com)? Is there a documented
sandbox test value or a supported way to create a Chemical Record without
WorldShip?
In an OAuth Authorization Code flow, where the end customer authorizes our
application with their own DG-enabled UPS account: is the customer account's
ChemicalRecordIdentifier accepted for the Shipping call, or must our own
integration account additionally hold a Dangerous Goods contract?
Is there any minimal working JSON example of a DG Shipping request
(SubVersion 1807, ADR, Limited Quantity) that populates
PackageServiceOptionsHazMat correctly?
Environment
Thanks in advance.