Skip to content

Go-live checklist

Work through this list in test mode. When every point holds, ask your Tujyane contact for a live key.

  • Your receiver verifies Tujyane-Signature on the raw body and rejects old timestamps.
  • It answers 2xx within 10 seconds, and processes the event afterwards.
  • It stores each event once by id, and acknowledges event types it does not know.
  • It checks mode, and never handles a TEST event as a live order.
  • You confirm only after your customer has paid you, and before confirmBy.
  • Every write sends an Idempotency-Key, and a retry of the same action sends the same key.
  • Your code handles every status, including NO_PARTNER_FOUND (retry, or tell your customer) and RETURNED with each failureReason.
  • Your code does not wait for shipment.partner_arrived_pickup or shipment.partner_arriving. They depend on the partner’s GPS and may not come.
  • Your code handles 409 CREDIT_LIMIT_EXCEEDED, 422 OUTSIDE_SERVICE_AREA and 429 RATE_LIMITED.
  • Your customer receives the deliveryCode before the partner arrives.
  • Your code handles shipment.delivery_code_locked.
  • A full TEST run passed with a normal reference.
  • TEST runs passed with references that contain unreachable, refused, wrong-address, damaged and no-partner.
  • The live key is in your server’s secret store, not in an app or in source control.
  • POST /webhooks/test with the live key answers delivered: true.
  • Your customers get delivery updates from you, because Tujyane does not message them.