Freight load API

Authentication and keys

• Create a key in the app under API keys. Keys belong to your company; any broker of the company can list and revoke them.
• Send it on every request: Authorization: Bearer <api_key>. Keys in URLs are refused; keep keys on your server.
• Scopes: loads:read (GET) and loads:write (POST, PATCH, DELETE, bulk).
• Writes need a broker account in a verified company and an active Elite plan or Elite trial.

Company loads API

• GET /api/v1/loads — list your company’s loads; GET /api/v1/loads/{id} — one load
• POST /api/v1/loads — create one load; an optional Idempotency-Key header makes retries safe
• POST /api/v1/loads/bulk — up to 500 loads per call, each with your own external reference; a reference already used by your company is never written twice
• PATCH /api/v1/loads/{id} — edit a load or change its status; DELETE /api/v1/loads/{id} — cancel it (a soft cancel, never a hard delete)
• A load you create is placed in the market of the account that created the key, priced in that market’s currency and marked as posted through the API.

Marketplace loads (read)

• GET /api/v1/marketplace/loads with region (optional): one of your account’s markets — eu, uk, tr or us
• Filters: origin_country, destination_country (case-insensitive), vehicle_type; page (default 1) and limit (default 20, maximum 100)
• Live loads only: loads whose pickup date has passed are never returned.
• Your account’s markets only: EU and UK accounts get Europe and United Kingdom; Turkish accounts Europe, United Kingdom and Turkey; US accounts United States.
• Response: data (id, status, visibility, region, cities and countries, vehicle_type, weight_kg, distance_km, rate, currency, dates, commodity) and pagination (page, limit, total, pages).
• Contact details, addresses and notes are never available through the API.

Limits

• Per API key: 60 requests a minute and 10,000 a day; a bulk call counts as one request per 25 loads.
• Per client IP: 120 requests a minute.
• Every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset; over the limit the API answers 429 with Retry-After.

Errors

• 401 — missing or invalid API key
• 402 — the key owner’s subscription is not active (payment pending, past due, cancelled, or an ended trial)
• 403 — the plan does not include API access, the key lacks the required scope, or the account is suspended
• 404 — the load does not exist or belongs to another company; 409 — the change is not allowed in the load’s current status
• 413 — more than 500 loads in one bulk call; 422 — the load failed validation (the response lists each field)
• 429 — rate limit reached; 500 — server error, retry later

What the API does not do

• Return poster contact details
• Choose a load’s market, broker or GigFreight classification for you
• Send webhooks or push notifications

• Full API reference for developers

Frequently asked questions