Supported public integration
Submit buyer vehicle demand
The supported public endpoint is POST /api/public-query. It submits a buyer's vehicle criteria to a participating broker. The request requires the broker's six-character public team code and is rate limited. Obtain the buyer's authorization before sending their name, email, or vehicle preferences.
curl --request POST \
--url https://www.therunslist.com/api/public-query \
--header 'Content-Type: application/json' \
--data '{
"shortId": "H7K2M9",
"name": "Jane Buyer",
"email": "jane@example.com",
"vehicles": [{
"make": "Toyota",
"model": "Camry",
"minYear": 2020,
"maxYear": 2025,
"maxMileage": 60000,
"condition": "clean",
"maxBudget": 25000
}]
}'Authentication
The public-query endpoint has no secret API key. Its public team code identifies the destination broker; it does not authenticate an account and must not be guessed. Chrome extension tokens are created by signed-in customers and are reserved for the official extension capture workflow. Session-cookie and mobile-token application endpoints are not a supported public API contract.
Webhooks
The Runs List does not currently offer customer-configurable outbound webhooks. Billing and messaging provider callbacks are private infrastructure endpoints and must not be called by customer integrations.
MCP server
The Runs List does not currently publish an MCP server. Agents should use the public site, the AI-readable files, the OpenAPI-described endpoint, or the human product interface as appropriate.
Integration support
Email support@therunslist.com with integration questions. Never email credentials, session cookies, extension tokens, or buyer data.