Shippigo

Shippigo is an Indian shipping aggregator: sellers book express, surface, reverse and time-definite shipments through one account, Shippigo allocates an underlying courier, and handles label, manifest, tracking and COD remittance. For a connector the objects that matter are serviceability, shipment creation with AWB and label, pickup, tracking events, NDR, RTO and COD remittance. There is no public developer portal and no published endpoint reference. Credentials are issued per seller by the Shippigo team, in the pattern common to mid-size Indian aggregators. This page records what can be established from Shippigo's own front end, its terms of service, and the Unicommerce integration guide.

At a glance

What it is

Shippigo is a shipping aggregator for Indian e-commerce sellers, operating at shippigo.com with a seller panel at app.shippigo.com. Its terms of service describe the service set: express and surface shipments in light and heavy weight, reverse shipments and time-definite delivery, across air, rail, ocean and road, executed through third-party "Service Providers" rather than an owned fleet. Sellers hold a "Shippigo Credit Account" that bookings are charged against, and claims for lost or damaged shipments are settled as credit notes against that account.

The terms also confirm the commercial shape of the relationship: KYC and due diligence on signup, a security deposit at Shippigo's discretion to cover counterfeit or fraud losses, COD remittance handled as a support ticket process rather than an automated feed, and claims processed within 10 working days.

Beyond that, little could be verified. The marketing site is a JavaScript-only single page application that serves no readable content to an automated fetcher, so the courier partner list, pincode coverage and seller count could not be confirmed on 2026-09-21. Shippigo does not appear in ClickPost's list of 428 integrated carriers, which is a mild signal that it is smaller than Shiprocket, NimbusPost or iThink Logistics.

API access

There is no developer console, no public key issuance and no published reference.

• Host probing on 2026-09-21: shippigo.com and www.shippigo.com serve the marketing app, app.shippigo.com serves the seller panel, and docs.shippigo.com, api.shippigo.com and developer.shippigo.com do not resolve at all.
• The seller panel's own public JavaScript bundle names https://v2api.shippigo.com/ as its backend. That host is live and returns a JSON error object for unknown paths, which confirms a JSON API exists behind it. Requests to /docs, /swagger, /swagger.json, /api-docs, /v2/api-docs and /openapi.json all return HTTP 404, so nothing is published there.
• The version marker in the host name (v2api) is the only versioning signal available. No version appears in any documented path or header.
• No official SDK exists. A GitHub search on 2026-09-21 found no Shippigo client library, plugin or Postman collection.

Authentication

Not published. What is known comes from the Unicommerce connector form, which lists the credentials Shippigo hands a seller:

The presence of a per-seller "API Url" is worth noting: it suggests the base URL is not a single fixed host for every client. Confirm this, because it changes how a credential store must be shaped (base URL becomes part of the credential, not a constant).

No token request or authenticated call sample is given on this page, because writing one would mean inventing endpoint paths and field names.

Objects we can read

Shipments and tracking

The only object with public evidence. The Unicommerce guide confirms, for Shippigo specifically:

• Both forward and reverse shipments are supported. Forward carries both COD and prepaid shipping methods with "AWB Generation selected as API". Reverse is prepaid pickup only.
• "Label pdf is provided by Shippigo."
• "Manifest is also provided by Shippigo."
• "AWB Tracking is provided in Uniware for Shippigo shipped orders", meaning Shippigo returns status updates that an external system can persist against an AWB.
• Serviceability is modelled in Unicommerce as a pincode list per facility, which implies Shippigo either publishes a serviceable pincode set or answers a per-pincode check. Which of the two is not stated.

Endpoint paths, request and response schemas, the tracking event vocabulary, NDR reason codes and RTO status names are all not published.

Orders, order items, products, listings, inventory

Not applicable, this is a carrier. Shippigo holds no catalogue. Orders enter as shipment booking requests. Consignee name, address and phone travel with the booking and are therefore PII held by Shippigo; the privacy policy explicitly covers "personally identifiable information / details of the customer / buyer of the User".

Locations

A pickup address book exists: the Unicommerce form references a Pickup Address Id configured per seller. Pickup locations appear to be pre-registered with Shippigo and referenced by an opaque id, rather than created through the API.

Payments and settlements

COD remittance and the Shippigo Credit Account are contractual features described in the terms of service. No settlement or remittance API is published, and the terms direct COD remittance queries to an email ticket, which suggests there is no self-serve feed.

Writing back: listings, price and stock

Not applicable, this is a carrier. Shippigo holds no product catalogue, price or sellable stock, so there is nothing to write back in the listings sense.

The write path is the shipment lifecycle. What can be asserted:

• Create shipment and generate AWB. Confirmed indirectly: Unicommerce configures forward COD and prepaid methods with "AWB Generation selected as API", so AWB is minted by a Shippigo API call rather than from a pre-allocated series.
• Pickup. Controlled by the Hand Over Mode setting, Drop or Pick. Whether a separate pickup request call exists, or pickup is implicit in booking, is not published.
• Label and manifest. Both are produced by Shippigo. The Fetch Label Link flag implies the API can return either a label document or a URL to one.
• Cancel shipment. Not documented in any source read. Assume it exists, confirm before building.

No bulk or feed mechanism is published.

Webhooks and notifications

None published, and no third-party source asserts one. Unlike most of its peers, Shippigo has no ClickPost carrier page, so there is not even an aggregator capability matrix to check.

Until Shippigo confirms otherwise, plan to poll:

• Poll tracking by AWB for every shipment not in a terminal state.
• 30 to 60 minutes is the usual fit for Indian last-mile carriers, where scans arrive in batches a few times a day. Do not go below 15 minutes without an agreed rate limit, since none is published.
• Stop polling an AWB about 7 days after it reaches a terminal state.

Ask Shippigo directly whether a status push or a daily event file is available for larger clients.

Rate limits and pagination

Not published. No limits, quota headers, burst allowance or pagination model could be found. Throttle client-side and use exponential backoff until Shippigo states a number in writing.

Mapping to the unified model

Only shipments can be populated, and the platform-side field names are unknown, so the right column records what the value is rather than a field name that cannot be verified.

Gaps and open questions

• No first-party API reference could be read. Every endpoint, header, field name, status value and limit is unverified.
• Whether the base URL is a single host or per-seller is unresolved. The Unicommerce form has an explicit "API Url" field, which hints at the latter.
• Whether authentication is a token exchange or per-request credentials is unknown.
• Whether a serviceability endpoint answers per-pincode or returns a full list is unknown.
• Shipment cancellation, a separate pickup request call, NDR read and action, and COD remittance reporting are all undocumented.
• Whether webhooks exist for larger clients is the highest-value question to ask, since polling every open AWB is the expensive alternative.
• The company's own scale, courier partner list and pincode coverage could not be verified, because the marketing site serves no content without JavaScript.

Sources

• https://www.shippigo.com/, read 2026-09-21. JavaScript-only application shell; no developer links. The front-end bundle at /static/js/main.da0a709c.chunk.js names https://v2api.shippigo.com/ as the backend host and https://app.shippigo.com/login as the panel.
• https://v2api.shippigo.com/, probed 2026-09-21. Returns JSON errors; no Swagger, OpenAPI or documentation path responds.
• Shippigo terms of service and privacy policy, as shipped inside the site bundle, read 2026-09-21. Service definitions, Shippigo Credit Account, COD remittance process, claims within 10 working days, KYC and security deposit terms.
• Unicommerce support, Integration with Shippigo, read 2026-09-21. The only source naming concrete configuration fields: User Name, Password, Service Type, Hand Over Mode, Pickup Address Id, Fetch Label Link, API Url. Confirms forward and reverse support, API-generated AWB, Shippigo-provided label PDF and manifest, and AWB tracking.
• ClickPost carrier list, sitemap read 2026-09-21. 428 carrier integration pages; Shippigo is not among them.
• GitHub repository and code search for "shippigo", 2026-09-21. No SDK, plugin or collection.