Loadsmart Shipment Events API
Our API supports fetch and change of a variety of shipments status, the main ones areresponsible to move the shipment from booked to in transit and delivered, They mustobey the following order:* **shipment:en-route-to-pickup** - The first state responsible to start the haul.* **shipment:check-in-pickup** - Used when driver arrives at pickup facility.* **shipment:check-out-pickup** - Used when driver leaves the pickup facility.* **shipment:check-in-delivery** - Used when driver arrives at delivery facility.* **shipment:check-out-delivery** - Used when the driver delivers the shipment.NOTE: These events are allowed to be changed via API.There are other events to support the main flow, they are available on webhooks or can be listed via APIShipment events, specific events that can happen for a shipment:* **shipment:incident** - When a incident is registered to a shipment.* **shipment:canceled** - When the shipment is canceled for some reason.Appointment events, these events are normally set before the load starts to move:* **shipment:appointment-pickup** - Used to set an appointment at pickup.* **shipment:appointment-delivery** - Used to set an appointment at delivery.Carrier related events, indicate changes in the carrier, drop, etc. normally happens before the load starts to move:* **shipment:carrier-updated** - Used for changes on a load related to a carrier, i.e. trailer # change.* **shipment:carrier-dropped** - Indicates a carrier drop for a particular shipment.* **shipment:driver-assigned** - A carrier driver assignment.* **shipment:driver-unassigned** - A carrier driver unassignment.Carrier location update, happens while the load is in transit until final delivery:* **shipment:location-updated** - Used to indicate the geographic coordinates of the carrier.
Loadsmart Shipment Events API is one of 48 APIs that Loadsmart publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Shipment Events. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.
This API exposes 2 operations across 1 path. It is described by OpenAPI 3.2.0, at version 1.0.0.
Requests are made against 2 base URLs: https://api.loadsmart.com, https://api.sandbox.loadsmart.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Loadsmart Shipment Events API declares
2 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (Application-JWT).
It accepts HTTP bearer tokens (JWT) (User-JWT).
Application-JWT— Authorize the request with the application context (preferred for the endpoints that support it): { "sub": "sys", "iss": "token-issuer", "exp": 1626239022, "ia…User-JWT— Authorize the request with an user context. A payload example would be: { "sub": "usr:87127882-d1db-4e50-8f7c-c792a80d7c49", "iss": "token-issuer", "iat": 1517…
Paths & Operations 2
Across 1 path, the API surfaces 2 operations — 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Our API supports fetch and change of a variety of shipments status, the main ones are responsible to move the shipment from booked to in transit and delivered, They must obey the…
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Loadsmart 12
Other APIs Loadsmart publishes across the network.
This is an independent, third-party profile of Loadsmart Shipment Events API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.