Get a collection of listings based on the specified search criteria.
partnerReferenceId: A user supplied ID used for reference.
Be sure to URL encode any parameters that contain spaces or special characters.
A user supplied ID used for reference.
Example:dad00000-e89b-12d3-a456-426614174000
Determines which record in the collection will be the first one displayed. This value is 1-based, meaning the count starts at 1.
Default:1
Example:1
The maximum number of items to be returned in the response.
Default:25
>= 0<= 500
Example:10
The major version of the API to make a request against. This is a custom MIME type that contains vnd.coxauto.v[#]+. For example, to request a resource from version 2.x.x of an API, the Accept header should be set to application/vnd.coxauto.v2+json.
Example:application/vnd.coxauto.v2+json
OK. Successful request.
A collection of listings.
The URL used to query the current collection of the resource.
Example:https://marketplace-api.centraldispatch.com/listings?limit(5,1)
The total count of resources in the collection.
Example:23
Details of a listing.
Get the listing for the provided listing ID.
Location header that contains the fully qualified URL of the newly created resource. The final segment of the URL will be the ID of the resource.The ID of the listing.
Example:42220470
The major version of the API to make a request against. This is a custom MIME type that contains vnd.coxauto.v[#]+. For example, to request a resource from version 2.x.x of an API, the Accept header should be set to application/vnd.coxauto.v2+json.
Example:application/vnd.coxauto.v2+json
OK. Successful request.
Details of a listing.
The ID of the listing.
Example:42220470
The ID of the Central Dispatch customer who is the shipper.
Example:afd2fb59-b89d-4572-8f9a-e57f82a61c68
These are provisions added to a contract that specify extra obligations, rights, or conditions beyond the standard terms.
Real Life Example: Charging cables need to be picked up with vehicles and if left behind a $200 fee will be applied.
Rules: This information will be visible only to the assigned carrier after the load is dispatched, and it will no longer be editable at that point.
Example:Charging cables need to be picked up with vehicles and if left behind a $200 fee will be applied.
The date and time the listing was archived, in UTC/ISO 8601 format.
Example:2024-08-01T00:00:00Z
The available date of the listing, in UTC/ISO 8601 format.
Example:2025-11-05T00:00:00.000Z
The date and time the listing was created, in UTC/ISO 8601 format.
Example:2024-10-15T00:00:00Z
The date and time the listing was deleted, in UTC/ISO 8601 format.
Example:2024-09-10T00:00:00Z
The desired delivery date of the listing, in UTC/ISO 8601 format.
Example:2025-03-04T00:00:00Z
The expiration date of the listing, in UTC/ISO 8601 format.
Example:2025-08-15T00:00:00.000Z
An identifier managed by the user. Shippers can use this field to map a record (e.g. order, shipment, dispatch) in their local TMS to a Central Dispatch record. This value is displayed as the load number on the Central Dispatch website.
Example:RND10 CHEV
Indicates whether the vehicle is inoperable.
Example:false
The fully qualified URL of the listing.
Example:https://marketplace-api.centraldispatch.com/listings/id/42220470
The status of the listing.
ACTIVE load automatically becomes NOTLISTED when it passes its available-to-ship date by four days, reaches its expiration date, or has searchable set to false. Available beginning 8/10/26.This list is not exhaustive and additional values may be added at any time.
Allowed values:ACTIVEARCHIVEDDELETEDNOTLISTED
Example:ACTIVE
The Central Dispatch ID of the partner who created or last updated the transaction on behalf of the customer. Will be null if the customer made the API call directly.
Example:b6e8c9e4-989a-4b37-8dd7-99fd34882bd0
The Central Dispatch ID of the user who created or last updated the resource.
Example:6e93ff07-6ea6-4239-b502-7bf4f68d2600
Indicates the shipper requests for the carrier to use the Central Dispatch Mobile App to perform vehicle inspection at pickup and delivery. If true, the carrier will be asked to acknowledge the request before accepting the load.
Example:true
Indicates if the driver verification process is required. A driver must be assigned to the load before delivery. Information will be emailed to the contact physically present at the pickup location for use in verifying the driver’s identification. The Central Dispatch Mobile App must be used to perform the pickup and delivery inspection. (Only currently applicable to select private Marketplaces).
Example:true
Details of the marketplace.
A user supplied ID used for reference.
Example:25-KL8CH6
Details of the price.
The ID of the shipper order.
Example:123-abc 900
Details of the service level agreement (SLA) for a listing.
The source of the listing. This list is not exhaustive and additional values may be added at any time.
Allowed values:APIUICSV
Example:API
Details of a stop.
Details of a listing tag.
The total travel distance in miles.
Example:267
The trailer type. This list is not exhaustive and additional values may be added at any time.
Allowed values:DRIVEAWAYENCLOSEDOPEN
Example:OPEN
Details of a vehicle.
Displayed in Central Dispatch website/app as “Transport Special Instructions”, these are specific guidelines or details for the safe and efficient pick up, delivery, or transportation of a load. This may contain sensitive data and is not available prior to acceptance of terms by a carrier.
Rules: This information is visible only to the assigned carrier after the load is dispatched and remains editable at any time.
Example:You will need special clearance to get in the lot. Call Jean at 303-999-1212.
Update a listing.
If-Match header is required and its value can be found in the ETag response header of the resource’s GET by ID endpoint.This endpoint’s behavior has changed. In v1, vehicleId was optional on update — the system would attempt to match the vehicle using other fields. In v2, vehicleId is required whenever you are updating an existing vehicle. If you omit it for a vehicle you intended to update, the request will not fail — instead, it will be processed as a new vehicle creation, and it will count against your vehicle quota. This is a common integration bug for teams porting v1 code, since the old client code often didn’t set this field.
🚨 Action required: update your integration to store and pass the vehicleId returned from your original POST (or from a GET on the listing/vehicle) on every subsequent PUT.
The ID of the listing.
Example:42220470
This is a required field to ensure the update is being completed on an item that has not changed since it was last read. The value of this field will be the value of the ETag header that was received on the preceding get call.
Example:8675309
The major version of the API to make a request against. This is a custom MIME type that contains vnd.coxauto.v[#]+. For example, to request a resource from version 2.x.x of an API, the Content-Type header should be set to application/vnd.coxauto.v2+json.
Example:application/vnd.coxauto.v2+json
ListingRequest
Details of a listing.
The ID of the shipper order.
<= 50 characters
Example:123-abc 900
An identifier managed by the user. Shippers can use this field to map a record (e.g. order, shipment, dispatch) in their local TMS to a Central Dispatch record. This value is displayed as the load number on the Central Dispatch website.
<= 50 characters
Example:RND10 CHEV
The trailer type. This list is not exhaustive and additional values may be added at any time.
Allowed values:DRIVEAWAYENCLOSEDOPEN
Default:OPEN
Example:OPEN
These are provisions added to a contract that specify extra obligations, rights, or conditions beyond the standard terms.
Real Life Example: Charging cables need to be picked up with vehicles and if left behind a $200 fee will be applied.
Rules: This information will be visible only to the assigned carrier after the load is dispatched, and it will no longer be editable at that point.
<= 500 characters
Example:Charging cables need to be picked up with vehicles and if left behind a $200 fee will be applied.
Indicates the shipper requests for the carrier to use the Central Dispatch Mobile App to perform vehicle inspection at pickup and delivery. If true, the carrier will be asked to acknowledge the request before accepting the load.
Default:false
Example:true
Indicates if the driver verification process is required. A driver must be assigned to the load before delivery. Information will be emailed to the contact physically present at the pickup location for use in verifying the driver’s identification. The Central Dispatch Mobile App must be used to perform the pickup and delivery inspection. (Only currently applicable to select private Marketplaces).
Default:false
Example:true
The available date of the listing, in UTC/ISO 8601 format. Must not be before today or later than 30 days from today.
Example:2025-02-20T00:00:00Z
The expiration date of the listing, in UTC/ISO 8601 format. Must not be before today or later than 30 days from today. Will default to after creation date if not supplied.
Example:2025-03-10T00:00:00Z
The desired delivery date of the listing, in UTC/ISO 8601 format. Must be equal or greater than availableDate and not before today or later than 30 days from today (optional).
Example:2025-03-04T00:00:00Z
A user supplied ID used for reference.
<= 50 characters
Example:969175d4-a3f8-4e43-b64f-a95d77475aa0
Details of the price.
Details of the service level agreement (SLA) for a listing. Only required for listings in marketplaces allowing digital offers. Currently only applicable to private marketplaces.
Details of a stop.
Details of a vehicle.
Details of a marketplace.
Details of a tag.
Displayed in Central Dispatch website/app as “Transport Special Instructions”, these are specific guidelines or details for the safe and efficient pick up, delivery, or transportation of a load. This may contain sensitive data and is not available prior to acceptance of terms by a carrier.
Rules: This information is visible only to the assigned carrier after the load is dispatched and remains editable at any time.
Example:You will need special clearance to get in the lot. Call Jean at 303-999-1212.
If creating a listing from a canceled dispatch, provide the dispatch ID on Create Listing to qualify for quota exemption on matching vehicles. For each vehicle whose VIN matches a vehicle on the original dispatch, the prior quota allocation may be reused instead of incrementing. Not required and has no effect on Update Listing.
Example:d159acc0-e89b-12d3-a456-426614174000
No Content. Successful request.
Delete a listing.
The ID of the listing.
Example:42220470
The major version of the API to make a request against. This is a custom MIME type that contains vnd.coxauto.v[#]+. For example, to request a resource from version 2.x.x of an API, the Accept header should be set to application/vnd.coxauto.v2+json.
Example:application/vnd.coxauto.v2+json
No Content. Successful request.
Get a collection of listings for the provided listing IDs or URLs.
The major version of the API to make a request against. This is a custom MIME type that contains vnd.coxauto.v[#]+. For example, to request a resource from version 2.x.x of an API, the Content-Type header should be set to application/vnd.coxauto.v2+json.
Example:application/vnd.coxauto.v2+json
An array of listing IDs and/or listing URLs.
OK. Successful request.
A collection of listings.
The URL used to query the current collection of the resource.
Example:https://marketplace-api.centraldispatch.com/listings?limit(5,1)
The total count of resources in the collection.
Example:23
Details of a listing.