Carrier’s official API
CEVA Logistics API: integration guide
CEVA Logistics gives its US domestic ground customers three integration points: a SOAP rate service hosted on its ONEView customer portal, an XML order interface into its Matrix TMS that returns a house bill number and a BOL PDF, and a REST Track & Trace API. The services are aimed at shippers, 3PLs and TMS vendors that already have a CEVA customer profile, especially for heavyweight and white-glove home delivery freight.
This guide covers CEVA Logistics’s own API. Credentials come from CEVA Logistics, not from FreightAPIs, and we are not affiliated with them.
Want one API key for carrier terminals, NMFC and ports instead? CEVA Logistics location API · FreightAPIs API docs →
At a glance
| Carrier | CEVA Logistics |
|---|---|
| Type | Heavyweight freight forwarder & LTL carrier |
| Interface | SOAP/XML (SOAP 1.1, document/literal), REST with XML request body (order), REST/JSON (tracking) |
| Authentication | SOAP credentials in the request body (rating); OAuth 2.0 client credentials bearer token (order and tracking) |
| Capabilities | Rate quote, Transit time, Order creation & BOL, Shipment tracking, Proof of delivery & invoices |
Getting access
- These APIs are for existing CEVA customers. The rate service documentation and the order schema are provided to customers and authorized trading partners on request; the order XSD is marked for CEVA and authorized trading partners only.
- For rating, ask your CEVA account representative for ONEView web-service credentials: a user name, password and a customer Profile Key. The service levels you get back are driven by how that customer profile is configured.
- For order creation, your CEVA representative also has to issue the Matrix identifiers that go in request headers (business unit, customer ID and cost center code).
- The REST APIs sit behind CEVA's API gateway. You register on CEVA's developer portal, create an application to obtain OAuth client credentials, and subscribe to the APIs you need (for example Track & Trace).
- The documentation does not mention pricing, rate limits or a published sandbox. Alaska, Hawaii, Puerto Rico and Canada lanes are quoted by a CEVA representative, not by the rate service.
Authentication
SOAP credentials in the request body (rating); OAuth 2.0 client credentials bearer token (order and tracking).
- Rating: every request carries a Header element inside the RateRequest with UserName, Password and ProfileKey. UserType is optional and can be left empty. There is no token exchange for the SOAP service.
- Order and tracking: exchange your client_id and client_secret for an access token with grant_type=client_credentials (form-encoded POST to the gateway token endpoint), then send it as Authorization: Bearer YOUR_TOKEN.
- Bearer tokens are valid for about one hour (expires_in 3600). Cache the token, refresh it shortly before expiry, and fetch a new one on any 401.
- Order calls also need Matrix routing headers: MX-BusinessUnitId, MX-CustomerId and MX-CostCenterCode (from CEVA), plus MX-Source (B2B_API_SYNC), MX-SourceId (your own order reference), MX-SchemaVersion (1.4) and MX-TradingPartner (CEVA_USDOM for US domestic).
Endpoints
Rate quote
Send origin and destination ZIP codes, package lines and any special services; CEVA returns one priced result per service level configured on your profile. Each service level carries an itemized charge list that ends with a Total charge.
| SOAP | GetCEVARate | QuickRate service: returns charges and billing weight for each configured service level. |
Transit time
A second operation takes exactly the same request and adds a transit-day estimate to the rate response. Use it instead of GetCEVARate when you need both price and days.
| SOAP | GetCEVARateTransit | Same as GetCEVARate, plus TransitDays in the response. |
Order creation & BOL
Post a B2BMatrixOrder XML document (schema version 1.4) to create a shipment in CEVA's Matrix TMS. The JSON response returns the CEVA house bill number and the BOL as a Base64-encoded PDF. The same document type cancels or replaces an order through DocumentHeader.PurposeCode.
| POST | Matrix Order (B2BMatrixOrder v1.4) | Create, cancel or replace an order; returns HAWB_NUMBER and BOL file. |
Shipment tracking
Look up a shipment by its house bill number to get a summary, the latest milestone, events grouped by location, exceptions and shipment details. Delivery is shown by a POD milestone event, which can include the signer's name.
| GET | Track & Trace: shipments/{houseBill}/{houseBill} | Returns status, milestone history and exceptions for one house bill. |
Proof of delivery & invoices
No separate POD image or invoice API is documented. Delivery confirmation and the signer name come from the tracking response; POD scans and invoices are obtained through your CEVA representative or the customer portal.
| GET | Track & Trace: shipments/{houseBill}/{houseBill} | Read the POD milestone event and its signature field. |
Example request
Weight is in pounds and dimensions in inches. The response lists one ServiceLevel per level on your profile, each ending in a Total charge, plus TransitDays.
Integration notes
- The rate service and the order API use different codes for the same accessorial. Rating uses ServiceTypeCode values such as Inside, Room-of-Choice and White-Glove; orders use OrderService codes such as IDD, ROC and WGD. Keep a mapping table.
- If you send a ServiceType, both PickUP and Delivery must be set to Y or N. Every Package field (Quantity, Weight, Length, Width, Height) is required.
- Which service levels come back depends on your customer profile, not on the request. Codes vary by profile (for example RESI, 2ND, THRE, WG, NOSI), so do not hard-code a single level.
- Billed weight can exceed actual weight because CEVA rates on dimensional weight. Use the returned BillingWeight rather than recomputing it.
- The house bill number (HAWB_NUMBER) is the key for tracking and support. It is only issued by the order call, so store it alongside your own PO or BOL reference.
- The order response returns the BOL as a Base64 string inside JSON, even though the request body is XML. Decode it to get the PDF.
- Free-text order fields such as EntityName, Address and ContactName are best wrapped in CDATA so ampersands and other XML characters do not break the document.
- Tracking timestamps should be treated as UTC and converted for display. Events are grouped by location, so flatten and sort them yourself to build a timeline.
FAQ
Does CEVA Logistics have an API for LTL rate quotes?
Yes. CEVA offers a SOAP QuickRate service with two operations, GetCEVARate and GetCEVARateTransit. You need ONEView web-service credentials and a customer Profile Key from your CEVA representative.
How do I authenticate with the CEVA API?
The rate service takes UserName, Password and ProfileKey inside the SOAP request. The REST order and tracking APIs use an OAuth 2.0 client-credentials bearer token that lasts about one hour.
How do I track a CEVA shipment through the API?
Call the Track & Trace API with the CEVA house bill number returned by the order call. The response includes the latest milestone, event history, exceptions and, once delivered, a POD event with the signer name.
Can I download a CEVA POD or invoice through the API?
No separate POD image or invoice API is documented. Delivery confirmation comes from the tracking response; POD scans and invoices are requested from your CEVA representative or the customer portal.
On FreightAPIs
Official resources
- CEVA QuickRate service WSDL (ONEView): oneview.cevalogistics.com/OneView/WebService/QuickRate/QuickRateService.svc?wsdl
Written from CEVA Logistics’s published API documentation and last checked 2026-10-09. FreightAPIs is not affiliated with CEVA Logistics; endpoints and access rules can change, so confirm details in the carrier’s own documentation before going live.
Other carrier API guides
ABF Freight · Estes Express Lines · Saia LTL Freight · TForce Freight · Old Dominion Freight Line · XPO (LTL) · AAA Cooper Transportation · AIT Worldwide Logistics