Skip to main content
POST
Resume a load
Puts a paused (inactive) load back on the market. Lanesurf starts contacting carriers again (real emails and calls), with outreach as it was before the pause: a load that had no outreach still has none.
  • Calling it again is safe.
  • 409 invalid_state: the load is covered (use /reopen), deleted, or its first pickup has passed (change the dates in the Lanesurf dashboard, or post the load again).

Authorizations

Authorization
string
header
required

One key per broker rep or per carrier signup. Keep it secret.

Path Parameters

id
string
required

The load's load_id, or its tms_id, from POST /v1/loads.

Example:

"3f2a9c4e-1d7b-4c55-8a7e-0b9d6e5f1234"

Response

Updated status: sourcing (or stalled).

load_id
string<uuid>
required
status
enum<string>
required

sourcing: Lanesurf is reaching carriers. stalled: the load is open, but no carrier has been contacted 15 minutes after posting (sourcing may not be switched on for this brokerage), or the brokerage signed up through the API and carrier outreach starts after Lanesurf's review. status_reason says which. covered: done; see covered_by. inactive: the load is no longer active and wasn't covered through this API. deleted: the load was deleted.

Available options:
sourcing,
stalled,
covered,
inactive,
deleted
offers
object[]
required

Carriers that named a rate, cheapest first.

outreach
object
required
next_step
string
required

For the agent. Exactly what to do next and which MCP tool to call (REST path in brackets).

agreed_rate
number

Once an offer is accepted: its rate (what was booked at).

max_rate
number
status_reason
string

Why, when the status alone would mislead. Set for stalled.

Example:

"No carrier has been contacted 15 minutes after posting. Sourcing may not be switched on for this brokerage; contact Lanesurf."

covered_by
enum<string>

lanesurf: the rep accepted an offer here. rep: the rep marked it covered elsewhere.

Available options:
lanesurf,
rep
winner
object

The accepted offer, once there is one.

post_with
object

The email and phone to put on the load wherever it is advertised, so carrier replies reach Lanesurf. Only set when Lanesurf has set a posting email and phone for the key; keys made by signing in from an AI app don't have one yet.

load
object

What was posted, as stored. On GET /v1/loads/{id} and every change (edit, pause, resume, reopen, delete, accept, decline, covered).