LogiNext

LogiNext is enterprise delivery and logistics automation software, not a carrier. A retailer, restaurant chain or 3PL runs LogiNext to plan routes, assign orders to its own delivery associates, track them live and capture proof of delivery. For a connector that means the objects available are orders (which LogiNext calls shipments), trips, delivery associates, hubs, serviceability geofences, tracking locations, e-POD and cash transactions. There is no rate card and no pincode serviceability in the courier sense, because LogiNext does not carry anything itself. Its API is properly documented, with tiered rate limits, batching rules and a rich webhook catalogue, but the public developer portal has gone offline and the documentation now survives mainly as the source of that portal on LogiNext's own GitHub organisation.

At a glance

What it is

LogiNext is a logistics software company founded in Mumbai, now operating as Stellation Inc. doing business as LogiNext, per the copyright line on its own help centre in 2026. It sells four products: Mile (last-mile delivery: route planning, schedule planning, live tracking, delivery validation), Reverse (returns and pickups), On-Demand (order sequencing and pickup and drop optimisation) and Haul (long-haul and full-truckload trips). It is sold to enterprises, and its own site cites Gartner, G2 and Capterra placements.

The commercial model matters for a connector. LogiNext's customer is the company doing the delivering. If a seller in our catalogue "ships with LogiNext", they either run their own fleet on it or their 3PL does. There is no LogiNext waybill you can buy, no rate to compare and no COD remittance from LogiNext.

LogiNext also has a concept called a Shipper, which is the customer's customer. Orders can be created on behalf of a Shipper using a clientCode field. Note that rate limits are shared across all of a client's Shippers, not allocated per Shipper.

API access

• Base URL: https://api.loginextsolutions.com/. On 2026-09-21 both POST /LoginApp/login/authenticate and POST /ShipmentApp/mile/v2/create return HTTP 401 with application/json, which confirms the documented routes still exist.
• Credentials: a username and password, issued either by auto-signup or by the LogiNext account manager. Tokens can also be generated from the "API Token Management" page in the LogiNext web application.
• Webhooks are not self-serve. You send your endpoint URL to your account manager or Customer Service Associate, who configures it.
• Versioning is in the path. Different applications sit on different versions: ShipmentApp/mile/v2 for order creation, ShipmentApp/mile/v1 for order retrieval, TrackingApp/mile/v1 for tracking, GeofenceApp/mile/v1 for serviceability. Keep the application prefix and version per endpoint rather than assuming one base path.
• No official SDK or Postman collection is published.

Authentication

1. POST https://api.loginextsolutions.com/LoginApp/login/authenticate with Content-Type: application/json.

{
  "userName": "demouser",
  "password": "Admin#1!",
  "sessionExpiryTimeout": 87600
}

2. The token comes back in a response header, not the body. The body is a plain status envelope.

{ "status": 200, "message": "success", "data": null, "hasError": false }

WWW-Authenticate: BASIC 075b8961-bd02-454c-83eb-259f965f313f

3. Send that same header on every subsequent call, alongside Content-Type: application/json.

curl "https://api.loginextsolutions.com/ShipmentApp/mile/v1/shipment?status=ALL&page_no=1&page_size=10" \
  -H "Content-Type: application/json" \
  -H "WWW-Authenticate: BASIC $LOGINEXT_TOKEN"

4. sessionExpiryTimeout is the session lifetime in hours, chosen by the caller: 1 for an hour, 24 for a day, 4320 for six months, 8760 for a year, 43800 for five years, 87600 for ten. Omitting it gives 90 days.
5. GET /LoginApp/login/token/refresh invalidates the current token and returns a new one in the same response header. There is no separate refresh grant.
6. A second, distinct flow exists for the mobile driver app: POST /LoginApp/login/mobile/auth with userName, password, imei and optional latitude, longitude, androidId, androidTime. It returns a per-delivery-associate token valid for four years. The Mobile API group requires this token, not the account token.

Multi-account support is one username, password and token per channel_account_id. Note the documentation's own warning: some field values, paymentType in Create Order among them, depend on the language preference of the user account the token was created for. Create API tokens against an English-language user account.

Objects we can read

Orders

LogiNext calls them shipments. Retrieval is GET /ShipmentApp/mile/v1/shipment with query parameters start_date, end_date, status, order_no, orderReferenceId, customer_code, employee_id, page_no and page_size. Dates use a YYYY-MM-DD HH:MM:SS form in the query string, while request and response bodies use UTC ISO 8601 such as 2016-07-01T11:18:00.000Z.

{
  "status": 200,
  "message": "SUCCESS",
  "moreResultsExists": false,
  "data": [
    {
      "referenceId": "f40cf4493a5949199775499b5750a272",
      "orderNo": "GR432U5",
      "parentOrderNo": "GKS12",
      "clientName": "UNY Logistics",
      "branchName": "West Brooklyn Hub",
      "origin": "West Brooklyn Hub",
      "destination": "California Hub",
      "shipmentOrderTypeCd": "DELIVER",
      "orderState": "FORWARD",
      "deliveryType": "TRK",
      "deliveryLocationType": "PUP",
      "shipmentOrderDt": 1485153536000,
      "startTimeWindow": 1485174600000,
      "endTimeWindow": 1485181800000,
      "paymentType": "COD",
      "packageValue": 300.0,
      "shippingCost": 50,
      "status": "DELIVERED",
      "serviceTime": 5,
      "deliveryMediumName": "James",
      "deliverMediumPhoneNumber": "9757282492",
      "assignedThrough": "Manually",
      "tripName": "TRIP-5276"
    }
  ]
}

Pagination is page-based (page_no, page_size) with a moreResultsExists boolean rather than a total count. Note that timestamps in this response are epoch milliseconds while elsewhere they are ISO strings; both conventions appear in the same API.

GET Status is a lighter endpoint for status only. Get EPOD and ESIGN and Get Custom Forms retrieve delivery evidence.

Order items

Line items exist as crates and line items on an order, with a dedicated Update Crates and Line Items call. There is no separate line-item read endpoint.

Products and listings, inventory

Not applicable, this is a delivery platform. Neither object exists.

Shipments and tracking

GET /TrackingApp/mile/v1/track/lastlocation?shipmentReferences=ID1,ID2 returns the last known geocoordinates for up to 20 order reference IDs in one call:

{
  "status": 200,
  "message": "Latest Location found successfully",
  "data": [
    { "lat": 19.1119794, "lng": 72.9094968, "shipmentReference": "21b538edf7f047028334480036179c70" }
  ],
  "hasError": false
}

This is a live position, not a scan history. LogiNext's model is geolocation plus status events, not carrier hub scans. Status history comes from the webhook stream, which is why the documentation is explicit that webhooks are the intended mechanism and polling the Get Order API is not.

There is also a customer-facing tracking iframe at https://api.loginextsolutions.com/track/#/order?ordno=...&aid=..., where aid is a different token from the API token, obtained from the account manager.

Returns and cancellations

Create Return and Cancel are both order-level calls under ShipmentApp. orderState takes FORWARD, and reverse flows are handled through LogiNext Reverse and the return order type. cancellationAllowedFl and returnAllowedFl are per-order flags set at creation.

Serviceability

Not a pincode lookup. POST /GeofenceApp/mile/v1/serviceability/get answers whether a location falls inside one of your configured geofences:

{
  "latitude": "40.760838",
  "longitude": "74.832830",
  "streetName": "Link Road",
  "locality": "Goregaon West",
  "city": "Mumbai",
  "country": "IND",
  "state": "MH",
  "postalCode": "4000104"
}

{
  "status": 200,
  "data": {
    "geofenceName": "GeofenceA",
    "geofenceType": "Hub",
    "geofenceShape": "Polygon",
    "geofenceArea": 335.55,
    "geofenceReferenceId": "3e290b46495b482a8e70e1078bd73c3f",
    "deliveryAssociates": [
      { "isActiveFl": true, "deliveryAssociateName": "John Doe", "deliveryAssociateRefId": "5c4fa64a97e24399a6cf91ef9767f980" }
    ]
  },
  "hasError": false
}

Either geocoordinates or an address can be sent; an address is geocoded first. One location per call, and the documented rate limit is 20 requests per second, higher than the general tiers.

Payments and settlements

There is no settlement API. Cash Transactions under Mile covers cash collected by delivery associates, which is the nearest equivalent and is an operational reconciliation, not a channel settlement.

Locations, customers, vehicles, drivers

First-class objects with their own create, read, update and delete calls: Customer, Address, Shipper, Delivery Associate, Hub, Vehicle, Driver, Geofence. Hubs are the branch or fulfilment centre. Customer and address records are PII.

Writing back: listings, price and stock

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

The write surface is large. Order creation alone has nine documented variants under POST /ShipmentApp/mile/v2/create, selected by the body rather than the path: Pick Up Only, Delivery Only, Pickup and Delivery, Point to Point, Multi Leg End-to-End, Deliver End-to-End, Pickup End-to-End, Point to Point End-to-End, Recurring End-to-End, plus Multi Stop and Create Return.

The request body is an array, which is how batching works:

[
  {
    "orderNo": "GR432U5",
    "awbNumber": "435-16685675",
    "shipmentOrderTypeCd": "DELIVER",
    "orderState": "FORWARD",
    "autoAllocateFl": "N",
    "shipmentOrderDt": "2016-07-15T10:30:00.000Z",
    "distributionCenter": "Chicago",
    "packageWeight": "10",
    "packageVolume": "4500",
    "packageLength": 2.5,
    "packageBreadth": 2.5,
    "packageHeight": 2.5,
    "priority": "PRIORITY1",
    "serviceType": "Premium",
    "paymentType": "Prepaid",
    "packageValue": "500",
    "shippingCost": "50",
    "numberOfItems": 1,
    "partialDeliveryAllowedFl": "Y",
    "returnAllowedFl": "Y",
    "cancellationAllowedFl": "N",
    "deliverBranch": "Boston",
    "deliverServiceTime": "20",
    "deliverStartTimeWindow": "2016-07-16T10:31:00.000Z",
    "deliverEndTimeWindow": "2016-07-18T10:31:00.000Z",
    "deliveryLocationType": "Home"
  }
]

Other write calls: Update, Update Status, Update Crates and Line Items, Assign, Unssign (spelled that way in the documentation), Cancel, plus Trip, Manifest and Route Planning operations, and a Mobile group that pushes driver-side events (accept order, check in, load, deliver) using the delivery associate token.

Labels are not part of this API in the courier sense. LogiNext produces manifests and e-POD, not carrier waybills; awbNumber on an order is a field you supply, not one LogiNext mints.

Webhooks and notifications

Webhooks are the documented primary mechanism, and the catalogue is unusually complete. Order events alone cover: Create, Update, Order Status Update, Accepted, Rejected, Cancel, Check In, Load Items, Load Complete, Delivered, Partially Delivered, Not Delivered, Pickedup, Not Pickedup, Allocation End, Get E-POD and ESign, Custom Form, Create End-to-End Order and Update End-to-End Order Status. Further groups cover Trips, Route Planning, Allocation Engine, Delivery Associates, Hubs and Routes.

Mechanics:

A 4xx or 5xx response, or a timeout, counts as a failure. The documented best practice is to return 200 immediately and process asynchronously.

Rate limits and pagination

LogiNext publishes real numbers, which is rare. Limits are per API tier and apply on a rolling interval:

Each endpoint's description states its tier. Authenticate Delivery Associate is Tier 2; token refresh and last-location tracking are Tier 1.

Important for multi-tenant designs: limits are shared across all of a client's Shippers, not allocated per Shipper. If you integrate on behalf of several Shippers under one LogiNext client, they compete for the same 5 or 10 requests per second.

Exceeding a limit returns HTTP 429 with "Max Request Limit Reached" and a temporary ban. The documented advice is to implement retries for 429 and 500.

Batching: APIs that support it accept up to 20 records per request, including Create Order and last-location tracking. Sending more than 20 fails the whole request. Create Order can return a partial success, where some orders are created and others are not, so the response has to be walked per record rather than treated as all-or-nothing.

Pagination on the order list is page_no and page_size with a moreResultsExists flag.

Practical cadence: webhooks as the only real-time source; the order list endpoint once a day over a date window for reconciliation; serviceability cached per geofence.

Mapping to the unified model

Gaps and open questions

• The documentation source is dated December 2020 and the portal it was built for no longer resolves. Confirm every endpoint, field and limit with LogiNext before building. The live 401 responses confirm the routes exist but say nothing about the request schema.
• No consolidated order status vocabulary is published. It has to be assembled from the webhook catalogue and the Delivery Associate Status and Trip Status appendices.
• Timestamp representation is inconsistent: ISO 8601 UTC in request bodies, epoch milliseconds in the order read response, and a space-separated form in query strings.
• No sandbox is documented. Ask whether one exists.
• Whether x-loginext-signature is still the only webhook verification mechanism, and whether a true HMAC option now exists, should be confirmed.
• The relationship between LogiNext and Stellation Inc. is not explained anywhere public. It affects which entity the data-processing contract sits with.
• ClickPost lists LogiNext as an integrable carrier with order creation, cancellation, polling, webhook, POD and NDR support and ClickPost-generated labels. That framing treats LogiNext as a carrier, which it is not; it reflects ClickPost's own abstraction rather than LogiNext's API.
• The Haul product (long-haul trips, vehicles, drivers) was not read in depth for this page.

Sources

• github.com/loginextsolutions/docs, read 2026-09-21. LogiNext's own Slate documentation source, source/index.html.md, 15,422 lines, last pushed 2020-12-22. This is the source of every endpoint, field, limit and webhook detail above.
• https://api.loginextsolutions.com/LoginApp/login/authenticate and https://api.loginextsolutions.com/ShipmentApp/mile/v2/create, probed 2026-09-21: both return HTTP 401 with application/json, confirming the routes are live.
• developers.loginextsolutions.com, checked 2026-09-21: NXDOMAIN. The portal referenced by LogiNext's own documentation is gone.
• LogiNext homepage, read 2026-09-21. Product lines Mile, Reverse, On-Demand and Haul.
• https://support.loginextsolutions.com/, read 2026-09-21. Login-walled help centre; its footer reads "2026 Stellation Inc. dba LogiNext".
• ClickPost, LogiNext carrier integration, read 2026-09-21. Third-party capability matrix, which frames LogiNext as a carrier.