EasyNXT

EasyNxt is a Gurugram multi-carrier shipping aggregator. A live REST API host at api.easynxt.in answers with HTTP Basic auth, but no endpoints are published.

EasyNxt, trading as Easynxt Logistics Private Limited of Gurugram, is an Indian multi-carrier shipping aggregator selling express parcel, cross border, freight and warehousing to B2C, D2C and B2B shippers, with a self serve seller panel, pincode serviceability and rate calculator tools, COD, and a tracking page. It is a reseller of carrier capacity rather than a carrier: it owns no network and holds no catalogue, price or stock. The interesting finding for an integrator is that EasyNxt does run a live REST API host, api.easynxt.in, which answers an unauthenticated request with an HTTP Basic authentication challenge, but not one endpoint, field or response is documented anywhere public. An API exists; its contract does not.

At a glance

Note

Use easynxt.in, not easynxt.com. The .com is a parked domain that immediately redirects the browser to a /lander page and serves no product, although the company does still publish help@easynxt.com as a contact address alongside help@easynxt.in. All product routes and the API host are on the .in.

What it is

Easynxt Logistics Private Limited gives its address as SCO 36, Sector 10A, Gurugram 122001, Haryana. The published proposition is an integrated logistics offering built on four lines: express parcel, cross border, freight, and software value added services, plus warehousing and factory to end user supply chain work. It sells to businesses across B2C, D2C and B2B and also takes individual consumer shipments, domestic and international, with free doorstep pickup.

The named capabilities are the standard Indian aggregator set: multi carrier selection per shipment, pincode serviceability lookup, a rate calculator, pickup request, real time tracking, COD and prepaid, faster COD remittance, business intelligence reporting, and inventory and order processing help. Two oddities in the copy are worth noting because they suggest the product is older than it looks: a "unique smile code" for contactless COVID safe delivery, and "peer to peer relay connectivity" for network routing.

The scale appears small. The marketing site is built on the ThemeForest "Merit" HTML5 template and still carries unreplaced template filler in places, including testimonial placeholder text, a "Premium Multi-Purpose HTML5 Template" heading and a tel:123-456-7890 link. No funding, seller count, shipment volume or carrier roster is published. The company has no GitHub presence at all.

API access

An API host exists and is reachable. No documentation for it exists.

What was established by direct observation on 2026-09-22:

api.easynxt.in resolves, to the same address as easynxt.in and ship.easynxt.in.
A GET of https://api.easynxt.in/ returns 405 with an empty body and the header WWW-Authenticate: Basic realm="REST API". A POST to the same path returns 411 Length Required from IIS, meaning the route accepts POST and the rejection is about the missing content length, not the method.
Response headers give the stack: Server: Microsoft-IIS/10.0, X-Powered-By: ASP.NET, X-Powered-By-Plesk: PleskWin, and a ci_session cookie. The ci_session cookie and the CodeIgniter default 404 page returned by unknown paths confirm the application is CodeIgniter running under IIS. The Basic realm="REST API" challenge is the default emitted by the widely used CodeIgniter REST Server library, which is consistent with everything else observed.
Unknown paths under the host return the CodeIgniter "404 Page Not Found" page. help, docs, swagger, api-docs and v1 all 404, so there is no self documenting help page, no Swagger or OpenAPI document and no version prefix in use.
No official SDK exists in any language. There is no Postman collection, no WSDL, and no EasyNxt owned GitHub organisation or repository.
EasyNxt appears in no aggregator carrier documentation set and is absent from ClickPost's carrier integration sitemap.

The practical consequence is that the endpoint inventory has to come from EasyNxt. Ask for the API document, a Basic auth credential pair, and the base path convention; everything else is guesswork and guesswork must not be written into a connector.

Warning

Do not attempt to discover endpoints by brute forcing paths against api.easynxt.in. Nothing about the path scheme is published, an unauthenticated probe reveals nothing beyond the 404 page, and an aggregator API of this shape will often accept a booking on a POST. Get the document from the vendor.

Authentication

HTTP Basic, as far as can be established without an account.

Obtain a Basic auth username and password from EasyNxt. There is no visible self serve key issuance in the panel and no published request form for it, so the route is the support address help@easynxt.in or a sales contact.
Send them as a standard Authorization: Basic header on every request. There is no token endpoint to call first, nothing expires, and nothing needs refreshing.
For multiple shipper accounts, store one credential pair per EasyNxt account. There is no evidence of an application credential distinct from an account credential, and no scope or role model is published.

Because the endpoint paths are unknown, no meaningful token request or authenticated call example can be given without inventing one. What can be shown honestly is the challenge itself, which is how the auth model was determined:

  the observed challenge, confirming Basic auth on the API host
curl -sI https://api.easynxt.in/

  HTTP/2 405
  www-authenticate: Basic realm="REST API"
  server: Microsoft-IIS/10.0
  x-powered-by-plesk: PleskWin

The seller panel at ship.easynxt.in is a separate, cookie based session login posting to ship.easynxt.in/login/do_login, with a password reset at login/forgotpassword. That is a browser flow, not an interface to build against.

Objects we can read

None documented. No endpoint, parameter, pagination model or response schema is published for any object, so nothing can be written here without fabricating it.

What the product is claimed to hold, and would therefore be worth asking EasyNxt for, in the order it matters for the unified model: shipments with tracking event history, NDR records with action, RTO status, COD remittance records, pincode serviceability, and rate quotes by origin, destination and weight. EasyNxt holds no orders of its own beyond the shipment it was given, and no listings, products or inventory.

Three routes on the public marketing site are observable and hint at the internal shapes, but they are website form handlers and not a supported interface: easynxt.in/pincode_check/fetch behind the serviceability form, easynxt.in/tracking behind the tracking form, and easynxt.in/rate_calculate behind the rate calculator. They are recorded only as evidence that serviceability, tracking and rating logic exists server side. Do not build against them; an unversioned form handler on a marketing page will change without notice.

Writing back: listings, price and stock

Not applicable, this is a carrier aggregator. EasyNxt 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 is shipment create returning an AWB and a label, shipment cancel, and pickup request. All three exist in the product: the panel has a booknow route for creating a shipment, a cancel_refund route, and a pickup_location route for managing pickup addresses, and the marketing copy advertises pickup request and label generation. None of it is documented as an API call, so no request body, response or confirmation mechanism can be given.

Webhooks and notifications

Not published. There is no callback registration, no event type list, no signing secret, no signature header and no retry policy in any public source. Any claim that EasyNxt pushes shipment events is unsupported.

Because no read endpoint is published either, no polling recommendation can be given yet. Once the endpoint document is obtained, the cadence to aim for on an aggregator of this kind is a status poll on the active shipment set every 3 to 6 hours, tightening for out for delivery and NDR states, plus a daily pull of COD remittance. Whether EasyNxt supports a bulk or date windowed status call, which is what makes that affordable, is unknown.

Rate limits and pagination

Not published. No quota is stated, no X-RateLimit style header appeared on any observed response, and no pagination model is documented.

The one inference worth acting on is architectural rather than contractual: a CodeIgniter application on a single Plesk for Windows IIS instance, serving the marketing site, the seller panel and the API host from the same address, will not tolerate concurrency well. Until a limit is agreed in writing, serialise per credential, keep concurrency at 1 or 2, back off with jitter on any non 200 or any HTML error body, and cache serviceability results for at least 24 hours.

Mapping to the unified model

No field level mapping can be given. Not one EasyNxt API field name has been published, and none is observable without a credential.

The structural mapping is nonetheless predictable for this platform type and can be stated as a target: EasyNxt is a source of shipments and of the COD side of settlements, and nothing else. It holds no products, listings or inventory, its orders are only the shipments it was handed, and its customers data is per shipment consignee PII rather than a customer record. returns will appear as RTO status on a shipment rather than as a separate object. Fill the table only after the vendor document is in hand.

Gaps and open questions

The entire endpoint inventory is unknown. This is the blocking gap: an API host is confirmed live and Basic authenticated, and nothing else about it is known.
How to obtain an API credential is unknown. Nothing in the self serve signup or KYC flow visibly issues one.
Whether the API covers reads at all, or only shipment creation, is unknown. Some small Indian aggregators expose a create and a track call and nothing else.
Whether a bulk or date windowed status call exists is unknown, and it determines whether daily extraction is economic.
Whether the platform is EasyNxt's own build or a white labelled instance of another Indian aggregator could not be determined. The CodeIgniter on IIS with Plesk stack is common among white labelled Indian shipping panels, so this is worth establishing early: if it is white labelled, the real contract belongs to the underlying vendor.
The carrier roster is not published, so which last mile partners a shipment can be routed to is unknown.
Company size, incorporation date, funding, seller count and shipment volume could not be verified from any first party source. The template filler still present on the site suggests a small operation, which is an impression rather than a finding.

Sources

EasyNxt homepage, read 2026-09-22, for the service lines, capability list and the panel route inventory
EasyNxt about page, read 2026-09-22
EasyNxt pricing page, read 2026-09-22, which gives the legal name Easynxt Logistics Private Limited and the Gurugram address
EasyNxt seller panel login, read 2026-09-22, showing the session login post to login/do_login
Live header probe of https://api.easynxt.in/ on 2026-09-22, which returned 405 with WWW-Authenticate: Basic realm="REST API", Server: Microsoft-IIS/10.0, X-Powered-By-Plesk: PleskWin and a ci_session cookie, and 411 Length Required on POST. Path probes for help, docs, swagger, api-docs and v1 all returned the CodeIgniter 404 page
DNS checks on 2026-09-22: easynxt.in, www.easynxt.in, api.easynxt.in and ship.easynxt.in resolve to the same address; docs.easynxt.in and developer.easynxt.in return no address record; easynxt.com serves a parked lander
ClickPost carrier integration sitemap, read 2026-09-22, which contains no EasyNxt carrier page
GitHub repository and code search for "easynxt" on 2026-09-22, which returned no EasyNxt owned repository and no integration code