Go-live checklist

Before you switch EPARCEL_BASE_URL to production, check that your integration does all of this:

• The API key and base URL come from configuration. The key never reaches logs, client-side code or version control.
• Development and automated tests use the test environment only.
• Every single create sends a deterministic Idempotency-Key, reused on retries, with one key per physical parcel.
• The client timeout is at least 60 seconds. Timeouts and 5xx are retried with backoff and the same key; 4xx is never retried unchanged.
• Weights and dimensions are converted to integer grams and millimetres, rounded up. zipcode is kept as a string. Both recipient email and phone are sent.
• shipment_id, tracking_number, carrier and the label are stored before anything else can fail.
• Batch results are checked item by item, and failed items are surfaced or retried individually.
• Parcels that can’t be shipped (400, 422) reach a human with the reason.
• Labels print at 101 × 200 mm, actual size.
• The live scenarios ran once on the test environment and pass.

Then ask E-Parcel for your production key.

Getting help

Contact your E-Parcel contact with the shipment_id, your customer_reference, the time of the request and the response you got. Never include the API key in a support message.