ShipDocket

The catalogue entry "Shipdocket" resolves to Shipdockets Pvt Ltd, a shipping aggregator registered in Jaipur, Rajasthan that resells multi carrier domestic, international and LTL shipping to Indian sellers through a single dashboard. The company is live and trading as of September 2026, but the singular domain shipdocket.com is not theirs: it is a recycled GoDaddy registration that has served three unrelated businesses since 2020 and today hosts a bowling brand. The real site is shipdockets.com, and it publishes no developer documentation, no API reference and no integration guide of any kind. This page records what can be verified and recommends the catalogue entry be corrected to the plural domain and marked as having no API surface.

At a glance

What it is

Shipdockets Pvt Ltd gives its registered office as Panchsheel Enclave, 100, JLN Marg, Jaipur, Rajasthan 302018. It positions itself as an all in one shipping aggregator for Indian sellers, covering domestic and international shipping across B2B, B2C and LTL from one dashboard. The published feature list is the standard Indian aggregator set: multi carrier rate comparison, label generation, COD, real time tracking, automated order processing, NDR management with customer follow up and address correction, RTO reduction analytics, and automated COD reconciliation.

It is a reseller of carrier capacity, not a carrier: it owns no fleet and no network, and the shipments it handles move on partner couriers. On the evidence available it is a small and recent operation. The site carries a spin the wheel coupon widget on the homepage, the only route to an account is a callback request form asking for monthly shipment volume and average product weight, and the company has an active but modest presence on LinkedIn, Instagram, Facebook, X and YouTube. No funding, shipment volume, seller count or carrier roster figure is published anywhere on the site.

API access

There is no published API and no way to obtain credentials programmatically.

• Checked on 2026-09-22 and none resolves: api.shipdockets.com, app.shipdockets.com, docs.shipdockets.com, developer.shipdockets.com, panel.shipdockets.com.
• The site has no /api, /developers, /docs or /integrations reference page. shipdockets.com/channel-integrations exists but is marketing prose only: it promises "channel integrations" and "courier syncing" without naming a single channel, not even Shopify or WooCommerce, and gives no mechanism. shipdockets.com/carrier-integrations does not have its own content and serves the homepage instead, which suggests the route is unbuilt.
• No robots or sitemap file is served, so there is no index of unlinked pages to check.
• The seller panel login at shipdockets.com/login is a plain HTML form posting to shipdockets.com/login-check. That is a session cookie flow for a server rendered application, which is the opposite of what a token issuing API host looks like.
• No official SDK, Postman collection, OpenAPI document or WSDL exists. GitHub has no Shipdockets owned organisation or repository, and a code search across GitHub for the string returns only two unrelated files.
• Shipdockets appears in no aggregator carrier documentation set. It is absent from ClickPost's carrier integration sitemap, which lists over a thousand carrier pages.

The only third party claim that an API exists is a community maintained comparison file, src/data/platforms.ts in the GitHub repository Roman4ik22/shipping-calc, which lists an entry shipdockets as an India to global "International Aggregator" with hasApi: true and partnershipModel: "API". That file is an uncited hand written list with no endpoints, no auth model and no reference, so it cannot raise confidence above low. It is recorded here only because it is the sole external claim on the question.

Authentication

Not published. The only observable flow is a browser session: a username and password form post to shipdockets.com/login-check, returning a session cookie. No token endpoint, no API key issuance page and no signature scheme is documented or inferable. Do not attempt to build against the session flow; it is not a supported interface and will break without notice.

Objects we can read

None programmatically. There is no reachable, documented endpoint for any object.

From the marketing copy, the panel holds shipments with tracking event history, NDR records with follow up actions, RTO statistics, and COD remittance and reconciliation records. Serviceability by pincode and multi carrier rate comparison are also claimed. All of that is dashboard only on current evidence. If an onboarded seller account is available, the realistic extraction routes in order of preference are: ask Shipdockets directly whether a documented API exists for contract sellers, ask whether scheduled CSV or SFTP reports can be enabled, and only then consider panel exports.

Writing back: listings, price and stock

Not applicable, this is a carrier aggregator. Shipdockets holds no listings, no prices and no stock, so there is nothing of that kind to write.

The write path that matters for a carrier, shipment create returning an AWB and label, shipment cancel, pickup request and NDR action, is described in the marketing copy as available in the dashboard. No endpoint, request body or response is published for any of it, so no programmatic write path can be documented.

Webhooks and notifications

Not published. The site advertises "automatic NDR updates" and real time tracking to the seller, but names no callback registration, no event list, no signing secret and no retry policy. There is nothing to subscribe to and nothing to poll, because no read endpoint is published either.

Rate limits and pagination

Not applicable. No API surface is published, so there are no limits, no quota headers and no pagination model to document.

Mapping to the unified model

No mapping can be given. Not one Shipdockets field name has ever been published, and none can be observed without an account.

If a Shipdockets seller account is later obtained, the first question to settle is whether the panel is their own build or a white labelled instance of another Indian aggregator platform. Several aggregators of this size resell a third party panel, and if that is the case here the field names, and any API, will be the underlying vendor's rather than Shipdockets'. Establishing that would supply the real contract immediately and is the single most useful next step.

Gaps and open questions

• Whether a private API exists for contract sellers is unresolved. For an aggregator advertising channel integrations and courier syncing, some machine interface almost certainly exists internally, but nothing about it is public.
• Which carriers Shipdockets actually resells is not published. The carrier-integrations route serves the homepage rather than a carrier list, so the roster is unknown.
• Which sales channels it can pull orders from is not published either, despite a page dedicated to the subject.
• Whether the panel is proprietary or white labelled could not be determined without an account.
• Company size, incorporation date, funding, seller count and shipment volume could not be verified from any first party source.
• The relationship, if any, between Shipdockets Pvt Ltd and the singular shipdocket.com domain is unknown, and on the archive evidence there probably is none. The similarity is most likely how the catalogue entry acquired the wrong domain.

Sources

• Shipdockets homepage, read 2026-09-22, for positioning, the feature list and the Jaipur registered office
• Shipdockets channel integrations page, read 2026-09-22, which names no channel and no mechanism
• Shipdockets seller login, read 2026-09-22, showing the form post to login-check
• DNS checks on 2026-09-22: shipdockets.com and www.shipdockets.com resolve; api., app., docs., developer. and panel.shipdockets.com return no address record
• Archived shipdocket.com, April 2022, titled "Home, Global Professional B2B Platform"
• Archived shipdocket.com, May 2024, titled "VR Amusement World"
• Live fetch of shipdocket.com on 2026-09-22, returning a Firebase hosted page titled "SWEP, Bowl Your Way to Fun", plus a whois lookup giving creation date 2020-05-25, registrar GoDaddy, registrant organisation Domains By Proxy
• Roman4ik22/shipping-calc, file src/data/platforms.ts on GitHub, read 2026-09-22. Cited as the only external claim that an API exists, and treated as unverified
• ClickPost carrier integration sitemap, read 2026-09-22, which contains no Shipdockets or Shipdocket carrier page