Skip to main content
GET
Get Setup Status
GET /v1/dealers/setup/{setup_id}
v1.0 schema lock. The response shape on this page is the locked v1.0 contract. We will never remove a documented field, never rename a field, and never change a field’s type without bumping to v2 (see Versioning). The response shape varies by status: pending and running responses are subsets of the completed response; failed responses include an additional error field.
Poll the status of a dealer setup job created by Setup Dealership. Setup is async-only: every setup request returns a setup_id, and this endpoint is how you retrieve the result. Recommended polling interval: 5 seconds.

Parameters

Status Values

status — Setup Lifecycle

inventory_status — Inventory Availability

This field tells you whether inventory data is ready to fetch. It is null until setup completes, then progresses through these states:
When is inventory ready? status: "completed" means the dealership is configured, NOT that inventory is available. You must wait for inventory_status: "available" before calling the fetch endpoint.For real-time notification instead of polling, subscribe to the import.complete webhook event — it fires as soon as the first inventory import finishes.

Example

Response — Pending / Running

While the job is in flight, the response carries the lifecycle status and timestamps. When status is "running", an elapsed_seconds field reports how long detection has been running — typical jobs finish in 60 seconds; heavily bot-protected sites can take up to ~10 minutes.

Response — Setup Complete, Importing

Response — Inventory Available

Response — Failed

Completed Response Fields

Errors

Path Parameters

setup_id
integer
required

Query Parameters

api_key
string
required

Response

Successful Response