How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

AutoLeadStar Leads API

Operations related to leads

AutoLeadStar Leads API is one of 8 APIs that AutoLeadStar publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Leads. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, and rate-limit docs.

This API exposes 1 operation across 1 path, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 3 base URLs: https://fullpath.com/api/v2/external/consent-management, https://api.fullpath.com/v1, https://staging-api.fullpath.com/v1.

1 operations 1 paths 4 schemas 1 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.fullpath.com/v1
Authentication
HTTP Bearer, HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 2

AutoLeadStar Leads API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (Bearer). It accepts HTTP bearer tokens (JWT) (bearerAuth).

  • Bearer — Platform JWT or Consent Management vendor API key. In Scalar, paste only the raw token/key (no Bearer prefix).
  • bearerAuth — Platform JWT or Consent Management vendor API key. In Scalar, paste only the raw token/key (no Bearer prefix).

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 GET. Each is listed below with its method, path, parameters, and response codes.

leads 1

Operations related to leads

GET
/dealerships/{dealershipId}/leads
List leads
listLeads 7 params → 200204400401500

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Lead (57 properties), Pagination (4 properties), ErrorResponse (3 properties), LeadsResponse (2 properties). Each schema is shown below with its type and property counts.

ErrorResponse
object
Standard structure for API error responses
3 properties 2 required
LeadsResponse
object
Response containing multiple leads with pagination info
2 properties 2 required
Lead
object
Represents a lead with comprehensive vehicle and customer information
57 properties 2 required
Pagination
object
Pagination metadata
4 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

autoleadstar-leads-api-openapi.yml Raw ↑

Other APIs AutoLeadStar publishes across the network.

Fullpath MCP Tools
AutoLeadStar Activities API
AutoLeadStar Appointments API
AutoLeadStar Audiences API
AutoLeadStar Consents API
AutoLeadStar Shoppers API
AutoLeadStar Tasks API
Where this information came from

This is an independent, third-party profile of AutoLeadStar Leads API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.