Developer API

Outbounds Auto Transport accepts vehicle shipping quote requests over a simple REST endpoint. Use it to send us a customer's shipment details from your own app, website, or AI assistant. We create the quote in our system, and an Outbounds shipping specialist contacts the customer with pricing and next steps.

This API is for domestic shipments within the United States only. No account or API key is required.

Base URL

https://live.outboundstransport.com

Submit a quote request

POST /v1/leads

Send a JSON body with the pickup and delivery locations, the vehicle, and the customer's contact details.

Field	Type	Required	Description
`pickup`	string	yes	Pickup city and state, or a 5-digit ZIP code. Example: `"Seattle, WA"`
`delivery`	string	yes	Delivery city and state, or a 5-digit ZIP code
`vehicle.type`	string	yes	One of `sedan`, `suv`, `pickup`, `van`. Use `sedan` for coupes, hatchbacks, and wagons
`vehicle.year`	integer	no	Model year
`vehicle.make`	string	no	Manufacturer, for example `Honda`
`vehicle.model`	string	no	Model, for example `Civic`
`vehicle.operable`	boolean	no	Whether the vehicle runs and drives. Default `true`
`transportType`	string	no	`open` (default) or `enclosed`
`pickupTiming`	string	no	`flexible` (default) or `exact`
`pickupDate`	string	no	Requested pickup date as `YYYY-MM-DD`
`contact.name`	string	yes	Customer's full name
`contact.email`	string	yes	Customer's email address
`contact.phone`	string	yes	Customer's US phone number. Formatting is ignored; 10 digits are required, and a leading +1 is accepted
`militaryMember`	boolean	no	Active-duty military or veteran. Default `false`
`notes`	string	no	Anything the specialist should know, up to 500 characters
`dryRun`	boolean	no	When `true`, validates the request and returns a sample response without creating a quote or contacting anyone. Default `false`

Unknown fields are ignored.

Example request

This example submits a real request. Add "dryRun": true to the body to try it without creating a quote.

curl -X POST https://live.outboundstransport.com/v1/leads \
  -H "Content-Type: application/json" \
  -d '{
    "pickup": "Seattle, WA",
    "delivery": "Austin, TX",
    "vehicle": { "type": "sedan", "year": 2019, "make": "Honda", "model": "Civic", "operable": true },
    "transportType": "open",
    "pickupTiming": "flexible",
    "contact": { "name": "Jane Doe", "email": "jane@example.com", "phone": "2065550123" }
  }'

Example response

201 Created

{
  "status": "received",
  "referenceId": "OAC-4821",
  "quoteUrl": "https://www.outbounds.at/quote/OAC-4821",
  "message": "Thanks Jane! Your auto transport request OAC-4821 has been received. An Outbounds shipping specialist will contact you shortly at (206) 555-0123 or jane@example.com with your price and next steps. Questions? Call 1-855-503-0008.",
  "dryRun": false,
  "support": { "phone": "1-855-503-0008", "email": "go@outbounds.at" }
}

Show message to the customer as-is. The referenceId is the customer's quote number; they can mention it when they call us.

Errors

Status	`error`	When
400	`validation_error`	A field is missing or invalid. `details` lists each problem
422	`unsupported_location`	We could not resolve a location to a US city and state or ZIP code
500	`internal_error`	Something failed on our side. Ask the customer to call 1-855-503-0008

Example 400 response:

{
  "error": "validation_error",
  "message": "The request has invalid or missing fields.",
  "details": ["contact.phone must be a 10-digit US phone number"]
}

Every error message is written so it can be shown to the customer.

Testing your integration

Send "dryRun": true in the body. The request is validated and a sample response with reference id TEST-0000 comes back, but no quote is created and nobody is contacted. The response has referenceId TEST-0000, dryRun: true, and no quoteUrl. Dry runs skip location lookup, so they never return 422.

What happens after a request

•The customer receives a confirmation email from Outbounds.
•A shipping specialist reviews the request and contacts the customer by phone, text message, or email with pricing.
•The customer books with the specialist or on their quote page.

OpenAPI specification

A machine-readable description of this API is available at https://www.outbounds.at/openapi.json.

Contact

Questions about the API? Email go@outbounds.at. See also our terms of service and privacy policy.