How to integrate loads through a load board API

Typical integration uses

• Sync loads into a Transport Management System
• Feed internal load-matching or alerting
• Build carrier-facing load views or reports

GigFreight’s API today

• Marketplace endpoint: GET /api/v1/marketplace/loads — returns live loads (never loads past their pickup date) in the key owner’s markets.
• Company loads API: /api/v1/loads — create, update, cancel and list your company’s own loads, or upload up to 500 per bulk call, with a loads:write key.
• Authentication: Authorization: Bearer <api_key>; keys are created in the app’s API Keys section, belong to the company and carry scopes (loads:read, loads:write).
• Filters: region (one of the account’s markets: eu, uk, tr, us), origin_country, destination_country, vehicle_type.
• Each load includes its region and the currency of its rate.
• Pagination: page and limit (default 20, maximum 100 per page).
• Plans: API access is part of the Elite plan (an active Elite subscription or an Elite trial). Contact details are never available through the API.
• Errors: 401 for a missing or invalid key; 403 when the plan has no API access (Elite only) or the account is suspended; 402 when the subscription is not active (payment pending, past due, cancelled or an ended trial).

• API documentation
• Company loads API reference

Integration checklist

1. Store the API key server-side only — never in a browser or mobile app.
2. Poll on a schedule that matches how fresh you need the data — every few minutes is plenty for load data.
3. Page through results rather than requesting everything at once.
4. De-duplicate on the load id; the API already leaves out loads whose pickup date has passed.

Frequently asked questions