intelligent.pageDocs

Bhejoo

Bhejoo (Bhejooo) is a defunct Indian shipping aggregator: both domains are dead, no API published, only an abandoned 2022 seller panel repository survives.

Bhejoo, spelled Bhejooo in its own code, was an Indian shipping aggregator with a seller dashboard covering order creation, order management, KYC, sales channel connections and a prepaid wallet. It is not a live product. Neither bhejoo.com nor bhejooo.com serves a site, the API host it used does not resolve, and the only surviving artifacts are abandoned GitHub repositories last touched in 2022. This page records what can be established and recommends the catalogue entry be corrected or retired.

At a glance

Warning

Recommendation: correct or retire this catalogue entry. bhejoo.com resolves to a Hostinger parked page, and the only Wayback capture of it (July 2025) shows a "Your domain is expired" holding page, meaning the domain never served archived product content under that spelling. The real spelling used by the product was bhejooo.com with three letter o characters, and that domain has no DNS record at all, nor does api.bhejooo.com. There is nothing to build a connector against.

What it is

Very little can be said with confidence, because no marketing site survives in any archive under either spelling.

What is established comes from an abandoned front end repository, raulkozy/Bhejooo-app-frontend, described by its author as "a react template based frontend for the bhejooo logistics app", last pushed in November 2022. Its screen structure shows what the product did:

  • Order creation and order management.
  • A KYC flow, which in Indian logistics means seller verification before COD is enabled.
  • A sales channel settings screen, implying store integrations (Shopify, WooCommerce and similar).
  • A prepaid wallet with an "add money" modal and a transactions summary, which is the standard prepaid billing model used by Indian shipping aggregators such as Shiprocket and NimbusPost.
  • Shipping tools labelled "Customize" and "Priority", which is the usual shape of a carrier allocation rule engine.

Together that is a conventional D2C shipping aggregator: connect a store, top up a wallet, create orders, let the platform allocate a courier, print labels, track.

Three related repositories exist under the same and adjacent authors (raulkozy/Bhejooo-Client, raulkozy/bhejoook8s, parantap-pt/bhejooo), all last pushed between October 2021 and November 2022. A Postman workspace named bhejooo exists, published by an individual in December 2023, but it contains only a globals environment and no collections.

API access

No API is available today, and none was ever published.

  • bhejooo.com, www.bhejooo.com, bhejooo.in, bhejooo.app and api.bhejooo.com all have no DNS address record.
  • bhejoo.com resolves to a Hostinger parked domain page. Its single Wayback capture, from July 2025, is a "Your domain is expired" notice.
  • No documentation host, no developer page, no SDK, no OpenAPI specification and no Postman collection exist.
  • Bhejoo appears in no aggregator carrier list. It is not in ClickPost's carrier documentation set, and a search of Unicommerce's shipping provider knowledge base returns nothing.
  • The front end repository names https://api.bhejooo.com as its API base, in a .env file and as a hard coded fallback. That is the only evidence the API ever existed.

Authentication

Reconstructed from the abandoned front end, and therefore describing a system that no longer runs. It is recorded here only so that a surviving Bhejoo credential can be recognised if one turns up.

The login screen used three routes off the API base:

The OTP request carried two static headers alongside the request body: client, with the value BHEJOOO_FE_CLIENT, and api_key, a hard coded UUID committed to the public repository. That is a front end application key, not a per seller secret.

After login, the access token was stored client side and sent on every subsequent request as a bearer token:

axios.interceptors.request.use((config) => {
  const accessToken = sessionStorage.getItem('access_token')
  if (accessToken) {
    config.headers.Authorization = `Bearer ${accessToken}`
  }
  return config
})

Token lifetime, refresh behaviour, scopes and whether any server to server credential existed at all are unknown. There is no evidence Bhejoo ever offered a merchant facing API as opposed to a web panel backed by a private one.

Note

A working looking application key was committed to a public repository in plain text. It is not reproduced here. It is dead along with the host, but it is a fair indicator of the engineering maturity of the product, which is relevant if the brand ever relaunches.

Objects we can read

None. There is no reachable endpoint.

Had the product been live, the panel's screens imply it held orders, order items, shipments with tracking, a seller KYC record, sales channel connections and a wallet ledger. None of it is accessible, and no field name from any of those objects has ever been published.

Writing back: listings, price and stock

Not applicable, this was a carrier aggregator, so it never held listings, price or stock. The write path a carrier normally offers, shipment creation and cancellation, is also unavailable because there is no reachable API. The panel had an order creation screen, so the capability existed behind the private API, but its contract was never documented.

Webhooks and notifications

Not published, and nothing survives to describe one. There is nothing to subscribe to and nothing to poll.

Rate limits and pagination

Not applicable. No API surface exists.

Mapping to the unified model

No mapping can be given. No Bhejoo field name has ever been published, and none can be observed.

The only names recoverable at all are from the authentication routes (phone_no, verify_id, access_token), which are not unified model objects.

Gaps and open questions

  • Whether the company still exists under another name or domain could not be determined. The bhejoo.com registration lapsed and is parked; bhejooo.com has no DNS at all.
  • The catalogue spelling is bhejoo with two letter o characters. The product's own code, repositories and client identifier all use three (bhejooo, BHEJOOO_FE_CLIENT). If the catalogue entry is kept, the spelling should be corrected, since searching for the two letter o spelling finds only a parked domain.
  • Whether Bhejoo ever offered a merchant facing API, as distinct from a private API serving its own panel, is unknown. No integration guide, no partner page and no third party integration exists.
  • No pricing, volume, funding, customer or corporate registration detail could be verified.
  • No archived copy of any Bhejoo marketing site exists under either spelling, which is unusual even for a small startup and suggests the product had very little public presence.

Sources