Dealership APILead

Lead entity

Read dealership lead records, contact information, inquiry counts, and latest inquiry summaries.

#Endpoints

A lead is the customer identity record for a dealership. Inquiries point back to leads.

GET/v1/leads
GET/v1/leads/{id}
Auth
Send the dealership API key in the x-api-key header.
Detail IDs
Detail routes use the UUID returned by the corresponding list endpoint.
Dates
Date fields and date filters use ISO 8601 timestamps.

#Filters and Limits

List endpoints share the same pagination envelope. Query booleans use true or false.

ParameterTypeRequiredNotes
limitnumberNoNumber of records to return. Defaults to 100. Maximum is 500.
offsetnumberNoNumber of records to skip. Defaults to 0.
searchstringNoOptional text search. Searchable fields are listed on each entity.
createdAfterdatetimeNoReturn records created at or after an ISO 8601 timestamp.
createdBeforedatetimeNoReturn records created at or before an ISO 8601 timestamp.
updatedAfterdatetimeNoReturn records updated at or after an ISO 8601 timestamp.
updatedBeforedatetimeNoReturn records updated at or before an ISO 8601 timestamp.
Entity filters
Common list filters plus search.
Search fields
name, email, and phoneNumber.
Default sort
createdAt descending, then id descending.
JSON
{
  "data": [],
  "pagination": {
    "limit": 100,
    "offset": 0,
    "total": 0
  }
}

#Response

FieldTypeNullableNotes
iduuidNoLead ID.
dealershipIduuidNoDealership that owns the lead.
namestringNoLead name.
emailstringNoLead email address.
phoneNumberstringYesLead phone number.
inquiryCountnumberNoNumber of inquiries attached to this lead.
latestInquiryInquirySummaryYesMost recent inquiry summary.
createdAtdatetimeNoCreation timestamp.
updatedAtdatetimeNoLast update timestamp.
Identity
id and dealershipId.
Contact
name, email, and nullable phoneNumber.
Inquiry summary
inquiryCount and nullable latestInquiry with type, market status, service, provider, and created date.
Dates
createdAt and updatedAt ISO 8601 timestamps.

#Example Request

Shell
curl "https://api.driverseat.io/v1/leads?search=jane&limit=50" \
  -H "x-api-key: sk-driverseat-..."

#Example Response

JSON
{
  "data": [
    {
      "id": "lead-id",
      "dealershipId": "dealership-id",
      "name": "Jane Driver",
      "email": "jane@example.com",
      "phoneNumber": "5551234567",
      "inquiryCount": 2,
      "latestInquiry": {
        "id": "inquiry-id",
        "type": "SALES",
        "marketStatus": "IN_MARKET",
        "service": "vehicle",
        "provider": "driverseat.io",
        "createdAt": "2026-06-24T12:00:00.000Z"
      },
      "createdAt": "2026-06-24T12:00:00.000Z",
      "updatedAt": "2026-06-24T12:00:00.000Z"
    }
  ],
  "pagination": {
    "limit": 50,
    "offset": 0,
    "total": 1
  }
}

#Errors

400
Invalid query parameter or resource ID. Common causes include a limit above 500, an invalid UUID, an invalid datetime, or an unsupported enum value.
401
The API key is missing, invalid, or revoked.
404
The requested lead does not exist or does not belong to the dealership authorized by the API key.