Set up MachShip

Account requirements

Ask your MachShip administrator for API access, a token with the required permissions and the numeric company ID. The selected company must appear in the token’s accessible-company list. Use a vendor test account or test token before live operations. The account type and carrier configuration determine what happens when a pending record is later converted.

• MachShip API overview
• MachShip fundamentals

Configure and test

1. Open company TMS connections, choose MachShip and enter a connection name, company ID and API token.
2. Confirm the provider environment and save. HaulMatch sends a read-only authentication check and verifies that the token can access the chosen company.
3. Import a known unallocated pending consignment by numeric ID. Review and publish its draft separately.

• Open company TMS connections
• Review, security and recovery guide

Pending exports and tracking

Confirmed job transfers use createPendingConsignment with the selected company and a stable HaulMatch customer reference. No carrier, manifest, rate selection or label generation is requested. Weight is per item in MachShip, so row totals are divided by quantity; metres are converted to centimetres.

Your dispatcher reviews and completes the pending record in MachShip. This does not configure HaulMatch as a MachShip carrier. Once converted, polling follows the consignment via its pending-record ID. No MachShip webhook receiver is enabled in this version.

• Create pending consignments
• Tracking and PODs

Before live use

• Confirm the correct company and token environment.
• Validate one import, publication and confirmed pending export in the vendor test account.
• Check multi-item weight and dimension conversion, then convert the pending record and verify tracking.
• Exercise revoked tokens, rate limits and reconciliation after an uncertain creation.