Skip to main content

Changelog

The Dash Open API and Webhook contract, consolidated as v1.0. Everything below describes the current, public contract.

v1.0 · Oct 2024 – May 2026
LatestAPIWebhooks

Initial public release

REST API

  • Five endpoints: Get Quote, Create Delivery, Get Delivery, Cancel Delivery, Notify Driver.
  • Two service categories — EXPRESS and LOGISTIC. EXPRESS is selected by using the /express/v1/... endpoints; LOGISTIC still uses the shared /v1/deliveries/... paths with the optional serviceCategory field for now.
  • EXPRESS endpoints live under /express/v1/... (quote, create, get, cancel, notify). The legacy shared /v1/deliveries/... paths are deprecated (21 May 2026) and will be obsoleted on 21 Nov 2026.
  • weight on Get Quote, Create Delivery, and Get Delivery; per-package dimensions (width / length / height).
  • Optional packages[].type on Get Quote and Create Delivery — REGULAR, SPECIAL, SENSITIVE, HIGH_VALUE, or OTHER. Create Delivery stores an omitted value as REGULAR and returns it per package, as does Get Delivery; Get Quote validates the value without defaulting it. A label only; it does not change pricing, allocation, or batching.
  • Cash on Delivery and per-delivery driver instructions (including WEBVIEW).
  • Cancellation allowed any time before the package is picked up — ALLOCATING, PENDING_PICKUP, or PICKING_UP.

Webhooks

  • Single JSON envelope per event; the status field drives which lifecycle event you're handling.
  • Full lifecycle coverage including PENDING_DELIVERY, COMPLETED, CANCELLED, and FAILED.
  • pickupAt is set from PENDING_DELIVERY onward (EXPRESS); failedReason and cancelledReason on the terminal events.
  • Cumulative weight on the webhook contract; media is an array of POD entries (PICKUP_PROOF, DELIVERY_PROOF, FAILED_PROOF).
  • Custom Authentication Key/Value header model; deliveries retried 3× over 60s on failure.

Conventions

  • Unified base URL https://api.dashelectric.co — Sandbox and Production are differentiated by credential pair, not hostname.
  • Provider-first terminology throughout; Bearer-token authentication via POST /v1/auth/providers/token.
  • Standard Indonesian-language error envelope across all endpoints.
  • Recipient email on Create Delivery is optional.