Carrier’s official API

Numark Transportation API: integration guide

Numark Transportation is a regional LTL carrier that exposes four customer web services: rate quotes, pickup requests, track and trace, and document image retrieval. Three of them are SOAP services named TQUOTEAPI, TPICKUPAPI and TTRACKAPI; the image service, TIMAGEAPI, is a simple GET request. They are aimed at shippers, 3PLs and TMS vendors with a Numark customer account.

This guide covers Numark Transportation’s own API. Credentials come from Numark Transportation, not from FreightAPIs, and we are not affiliated with them.

Want one API key for carrier terminals, NMFC and ports instead? FreightAPIs API docs →

Interface SOAP/XML (WSDL) · HTTP GET with query parameters (image retrieval)Endpoints 5Reviewed 2026-10-09Open in ChatGPT↗Open in Claude↗

At a glance

CarrierNumark Transportation
TypeLTL carrier
InterfaceSOAP/XML (WSDL), HTTP GET with query parameters (image retrieval)
AuthenticationUsername and password in each request
CapabilitiesRate quote, Transit days & terminal service, Pickup request, Shipment tracking, Documents & images (BOL, POD, invoice)

Getting access

  • The API documentation is provided by Numark to customers on request. There is no public developer portal or self-service signup in the documents.
  • Numark issues the username and password. For quotes you also need an IAM code (S, D or C) from the carrier that says whether you quote as the shipper, debtor or consignee.
  • Each service is gated by a role on your user profile (TQUOTEAPI, TPICKUPAPI, TTRACKAPI, TIMAGEAPI). A NOROLE or NOTAUTH error means the carrier has not set up or granted that role yet, so ask Numark to enable it.
  • For pickups, the username must be linked to exactly one customer record; NOCST and MULTCST errors mean the carrier needs to fix that link.
  • The documentation does not mention fees, rate limits or a formal approval process.

Authentication

Username and password in each request.

  • SOAP services: send USERNAME and PASSWORD inside a SECURITYINFO structure in the request body.
  • Image retrieval: pass username and password as query parameters, alongside the PRO number and document type.
  • There is no token or session step. Credentials go on every call, and each service checks that your user has its role.
  • A wrong login returns the error code BADUSRPWD in the response body rather than a SOAP fault.

Endpoints

Rate quote

GetQuote rates one or more freight lines between two ZIP codes and returns the total split into freight, fuel and accessorials, a quote number and a line-by-line breakdown. A blank RATING.ERRORCODE means the quote is valid.

SOAPGetQuote (TQUOTEAPI)Returns an LTL rate quote with charge breakdown and service information.
Key inputsSECURITYINFO.USERNAME, SECURITYINFO.PASSWORDQUOTE.IAM (S | D | C)QUOTE.SHIPPER.ZIP (ignored when IAM is S), QUOTE.CONSIGNEE.ZIP (ignored when IAM is C)QUOTE.PPDCOL (P | C)QUOTE.ITEMCOUNT and QUOTE.ACCESSORIALCOUNTQUOTE.ITEM: PIECES, WEIGHT, PALLETS (if on a pallet rate), CLASS, DESCRIPTION (60 chars max), HAZ (Y or blank)QUOTE.ACCESSORIAL.CODE (e.g. INSDEL, LIFDEL, LIFPIC, NOTFEE, RESDEL, RESPIC)QUOTE.CODAMT, CODTERMS, CODWHO, BOL, PO (optional)
Key outputsRATING.ERRORCODE, RATING.QUOTENUMBERRATING.AMOUNT, RATING.TOTALFREIGHT, RATING.FUEL, RATING.TOTALACCESSORIALRATECOUNT and RATEITEM lines (ACCCODE, PIECES, WEIGHT, CLASS, RATE, AMOUNT)RATING.DISCLAIMER

Transit days & terminal service

The same GetQuote response carries a SERVICE block: the origin and destination terminals with phone numbers, direct or indirect service, which weekdays each point is served, the number of service days, and estimated delivery dates for the next seven ship dates.

SOAPGetQuote (TQUOTEAPI) — SERVICE blockReturns transit days, terminal details and estimated delivery dates with each quote.
Key outputsSERVICE.ERRORCODESERVICE.ORIGIN / SERVICE.DESTINATION: ZIP, TERMINAL, PHONE, DIRIND (D | I), SUN … SAT (Y | N | L)SERVICE.DAYSSERVICE.SHIPDATE and matching SERVICE.ESTDELIVERY arrays

Pickup request

RequestPickup books a pickup for one or more shipments at a shipper location and returns a pickup number. Leave the shipper address blank to use the location on your user profile.

SOAPRequestPickup (TPICKUPAPI)Schedules a pickup and returns the assigned pickup number.
Key inputsSecurityInfo.Username, SecurityInfo.PasswordShipperInfo: Name, Address1, Address2, City, State, Zip (blank = profile location), PhoneNumber and Contact (required), SpecialInstructionsReadyDate (mm/dd/yyyy), ReadyTime and CloseTime (HHMM, 24-hour)ShipmentCountShipments: DestZip, Pieces, Pallets, Weight, HAZ, Liftgate, SortSeg, dblstack (Y = yes), Pro (optional pre-assigned PRO)
Key outputsResults.ErrorCodePickupNumber (0 when there is an error)

Shipment tracking

TrackTrace returns the current status of one freight bill by PRO number: shipper and consignee, ship date, delivery or estimated delivery date, who signed, and the movement history.

SOAPTrackTrace (TTRACKAPI)Returns current status and movement history for a PRO number.
Key inputsSecurityInfo.Username, SecurityInfo.PasswordProNumber
Key outputsCurrentStatus.ErrorCode (e.g. BADPRONBR, NOTAUTHFB)CurrentStatus.Shipper / CurrentStatus.Consignee (Name, Address1, Address2, City, State, Zip)CurrentStatus.Status (max 60 chars), Shipdate, DeliveryDate, EstDeliveryDate, SignedbyHistoryCount and History (Date, Time, Location, Description)

Documents & images (BOL, POD, invoice)

TIMAGEAPI is a GET request that takes the login, a PRO number, a document type and a file format. It returns the document for that freight bill.

GETtimageapi (TIMAGEAPI)Retrieves the BOL, POD or invoice image for a PRO number.
Key inputsusername, passwordpronumberdoctype (BOL | POD | INV)format (PDF | MTIFF; INV supports PDF only)
Key outputsImageRequest with ProNumber, DocType, Format, DocCountImage > ImageName and base64-encoded ImageData

Example request

RequestPickup SOAP envelope (current format)xml
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tpic="http://tpickupapi.wsbeans.iseries/"> <soapenv:Header/> <soapenv:Body> <tpic:requestpickup> <arg0> <SECURITYINFO> <USERNAME>YOUR_USERNAME</USERNAME> <PASSWORD>YOUR_PASSWORD</PASSWORD> </SECURITYINFO> <SHIPMENTCOUNT>1</SHIPMENTCOUNT> <SHIPMENTS> <DESTZIP>90210</DESTZIP> <PIECES>3</PIECES> <PALLETS>1</PALLETS> <WEIGHT>255</WEIGHT> <HAZ>N</HAZ> <LIFTGATE>N</LIFTGATE> <SORTSEG>N</SORTSEG> <DBLSTACK>N</DBLSTACK> <PRO></PRO> </SHIPMENTS> <SHIPPERINFO> <NAME></NAME> <ADDRESS1></ADDRESS1> <CITY></CITY> <STATE></STATE> <ZIP></ZIP> <CONTACT>Dock Manager</CONTACT> <PHONENUMBER>5555550100</PHONENUMBER> <READYDATE>10/15/2026</READYDATE> <READYTIME>0900</READYTIME> <CLOSETIME>1700</CLOSETIME> <SPECIALINSTRUCTIONS></SPECIALINSTRUCTIONS> </SHIPPERINFO> </arg0> </tpic:requestpickup> </soapenv:Body> </soapenv:Envelope>

Blank shipper name and address fields mean "pick up at the location on my user profile". Generate your client from the WSDL Numark gives you rather than hand-writing envelopes.

Integration notes

  • The pickup service moved to a new server version on July 4, 2024. The WSDL location and the envelope changed: the old format used the http://tpickupapi.wsbeans.iseries/xsd namespace with prefixed elements under args0, the new one uses http://tpickupapi.wsbeans.iseries/ with unprefixed elements under arg0. Element contents did not change. Older clients need regenerating.
  • In the actual envelope, READYDATE, READYTIME and CLOSETIME sit inside SHIPPERINFO, even though the field table lists them under ShipmentInfo. Element names are upper-case on the wire.
  • Pickup times are HHMM in 24-hour format, and the close time must be at least 30 minutes after the ready time (error NEED30). Past dates (PASTDATE) and days the carrier is closed (CLOSED) are rejected.
  • If you fill in ShipperInfo.Name you must also send Address1, City, State and Zip (errors ADD1REQ, CITYREQ, STATEREQ, ZIPREQ). Leave them all blank to ship from your profile location.
  • In GetQuote, ITEMCOUNT and ACCESSORIALCOUNT must match the number of ITEM and ACCESSORIAL entries you send. The docs warn that a wrong count can produce a wrong quote, not an error.
  • The IAM code decides which side of the lane comes from your profile: with IAM=S the shipper ZIP is ignored, with IAM=C the consignee ZIP is ignored. Valid freight classes depend on your tariff, so confirm them with Numark.
  • Errors are returned as codes inside the response (RATING.ERRORCODE, Results.ErrorCode, CurrentStatus.ErrorCode). Always check those fields; a non-blank value means the result is not valid.
  • Image data comes back base64-encoded inside XML, so decode ImageData before saving the file. MTIFF (multi-page TIFF) is only available for BOL and POD; invoices are PDF only.

FAQ

Does Numark Transportation have an API?

Yes. Numark offers SOAP web services for rate quotes (TQUOTEAPI), pickup requests (TPICKUPAPI) and tracking (TTRACKAPI), plus a GET-based image service (TIMAGEAPI) for BOL, POD and invoice documents.

How do I get access to the Numark API?

Ask Numark for API access as a customer. They issue the username and password, give you an IAM code for quoting, and grant a role for each service you plan to call.

Can I track a Numark shipment by PRO number through the API?

Yes. The TrackTrace operation takes a ProNumber and returns the current status, delivery or estimated delivery date, signer and movement history.

How do I download a Numark POD through the API?

Call TIMAGEAPI with your login, the PRO number, doctype=POD and format=PDF or MTIFF. The document is returned base64-encoded in the ImageData element.

Does the Numark quote API return transit time?

Yes. Each GetQuote response includes a SERVICE block with the number of service days, origin and destination terminal details, and estimated delivery dates for upcoming ship dates.

On FreightAPIs

Freight class calculator →Density and estimated class before you request a quote.Accessorial codes by carrier →Liftgate, residential, limited access — each carrier’s code.

Official resources

Written from Numark Transportation’s published API documentation and last checked 2026-10-09. FreightAPIs is not affiliated with Numark Transportation; 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