This document describes quick API implementation details of a simple workflow to create and manage an order. All examples are provided as
curl commands. Review API reference to learn more about requests and responses.
Step 1: Obtain ClientID and ClientSecret
ClientID and ClientSecret are available after creating an account on Shipper TMS. Request access if you don't have an account yet.
If you have an account, email [email protected] to obtain credentials.
Step 2: Authenticate your API client
All API requests must be authenticated. We support industry-standard OAuth 2.0.
Our first request is to send an authentication request:
This API request uses basic access authentication;
ClientSecret are provided as credentials. The API returns a successfull response with
access_token if the credentials are correct:
Step 3: Send a test API request
To make sure that the integration works, let's send a test request (
access_token is sent as an authentication header.):
The above request creates a new internal carrier. The response body should look like:
Step 4: Create an order
To follow the simple workflow, the API client should:
- Create an order
- Find a carrier
- Send the order to the carrier as a load offer
- Track the status(es) of the load offer and order
- Get BOL
- Mark the order as paid to the carrier
Create an order by sending a
POST request to
This request creates an order and returns its details with the unique global identifier:
guid. The API client should use this field to find, update, manage, or delete the order (or any object in the system).
A sample response can be reviewed on the API reference: Create an order.
Step 5: Find a carrier
When the order is ready to ship, it's time to find a carrier who can move this order. We support the flows below that help shippers and brokers to move loads:
- Via Super Loadboard: the order is posted to Super Loadboard and Super Dispatch notifies carriers who can move this order. Preferred carriers can book this order immediately. Other carriers can send a load request. The process is fully automated here.
- Via Central Dispatch: the order is posted to Central Dispatch and interested carriers will call you using more traditional methods. Later, this order can be assigned to a carrier, and the carrier may use Super Dispatch to move the order.
- The API client does know what carrier can move this order: the carrier's
guidor USDOT number is stored somewhere. In this case, the order can be sent to the carrier directly as a load offer.
- Find a carrier using our Load Matching system: our prediction system can offer carriers who may be interested to move this order. After choosing a carrier, the order can be sent to this carrier as a load offer.
Let's assume that you know the carrier's USDOT number or
Step 6: Send a load offer
You can use
carrier_usdot to send a load offer:
This request (reference) creates a load offer, and sends it to the carriers as an email and text message. The carrier can accept the load offer or decline it.
Each load offer has its own
guid is necessary to track the its status.
Step 7: Track
All the statuses are tracked via webhooks. A webhook action is sent to a URL when the load offer or order status is changed, for example: the carrier accepted or declined the offer, a driver picked up or delivered the order.
Read more about Webhooks.
Step 8: Get a BOL
The order BOL can be accessed by sending a GET request to
The response contains the BOL URL (a PDF file):
Step 9: Mark as paid to a carrier
When you send money to the carrier, you can document it using the endpoint
The response is a full order object. Reference: Mark an order as paid to the carrier.