Developers

The public API is the dashboard, with an access-token.

Two HTTP surfaces share AggregatorService. Sellers use JWT at /api/v1/seller/…. Integrations use a ParcelX-style v3 API with the seller’s API key as access-token. OpenAPI documents v3 shipping.

Auth

POST /api/v3/…
Header: access-token: <SellerProfile.api_key>

OpenAPI: /api/docs/
Base: https://backend.justshyp.com

JWT, channels, COD remittance and weight disputes stay on the seller dashboard — they are not in the public v3 spec.

What v3 covers

  • Warehouses

    CRUD seller-owned pickup locations; default used when omitted.

  • Serviceability

    Drop and pickup pincode, COD and reverse flags from CourierServiceability.

  • Rates

    Zone, volumetric, slabs, COD, RTO fallback, 18% GST.

  • Create & ship

    Channel or custom payload; explicit courier_keyword or auto-assign.

  • Label & invoice

    Persist courier label URL; generate invoice PDF on the shipment.

  • Track & cancel

    Scan-shaped tracking persisted; cancel refunds wallet if already debited.

  • Bulk

    Bulk ship, labels and invoices as BulkOperation rows.

  • NDR

    List initiated / RTO / closed; reattempt, RTO, update phone or address.

After signup, generate a key from the seller hub. Need a sandbox walkthrough? Contact engineering.

Ship from your stack this week

Create an account, add a warehouse, and compare live courier rates in a few minutes.