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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
AutoLeadStar

AutoLeadStar Shoppers API

Operations related to shoppers

Documentation Provider Profile APIs.io OpenAPI GitHub

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

Tagged areas include Shoppers. 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 7 operations across 7 paths, and defines 37 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.

7 operations 7 paths 37 schemas 7 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
Contact
API Support
Terms of Service
View terms
Resource Areas
1

Authentication & Security 2

AutoLeadStar Shoppers 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 7

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

shoppers 7

Operations related to shoppers

GET
/dealerships/{dealershipId}/shoppers
List shoppers
listShoppers 6 params → 200204400401500
GET
/dealerships/{dealershipId}/shoppers/{id}
Get a single shopper
getShopperById 3 params → 200401404500
GET
/dealerships/{dealershipId}/shoppers/{id}/audiences
List audiences for a shopper
listShopperAudiences 5 params → 200204401404500
GET
/dealerships/{dealershipId}/shoppers/{id}/events
List events for a shopper
listShopperEvents 5 params → 200204401404500
GET
/dealerships/{dealershipId}/shoppers/{id}/emails
List emails for a shopper
listShopperEmails 5 params → 200204401404500
GET
/dealerships/{dealershipId}/shoppers/{id}/phones
List phones for a shopper
listShopperPhones 5 params → 200204401404500
GET
/dealerships/{dealershipId}/audiences/{id}/shoppers
List shoppers in an audience
listAudienceShoppers 5 params → 200204401404500

Schemas 37

The contract defines 37 schemas that model the data the API accepts and returns. The most detailed are SaleEvent (64 properties), LeadEvent (59 properties), PageViewEvent (37 properties), PrimaryContact (24 properties). Each schema is shown below with its type and property counts.

AppointmentEvent
object
Appointment event
11 properties 3 required
EnrichmentEvent
object
Enrichment event
9 properties 3 required
PrimaryContact
objectnull
Primary contact information for a shopper. Extended version available in single shopper responses.
24 properties
Location
objectnull
Location information for a shopper
7 properties
Vehicle
objectnull
Vehicle information
6 properties
PageViewEvent
object
Page view event
37 properties 3 required
AdClickEvent
object
Ad click event
15 properties 3 required
ShopperPhone
object
Represents a phone number associated with a shopper
5 properties 3 required
Shopper
object
Represents a shopper. Additional fields are available via the embed parameter. Some fields (contacts, location, score, publiclink, customerlifetimevalue, lates…
23 properties 1 required
AudienceShoppersResponse
object
Response containing shoppers in an audience with pagination info
2 properties 2 required
LeadEvent
object
Lead event
59 properties 3 required
SMSSentEvent
object
SMS sent event
16 properties 3 required
AudiencesResponse
object
Response containing multiple audiences with pagination info
2 properties 2 required
Audience
object
Represents an audience (saved shopper filter). Additional fields are available via the embed parameter.
12 properties 10 required
ErrorResponse
object
Standard structure for API error responses
3 properties 2 required
ContactDetail
objectnull
Contact information for a shopper
22 properties
ServiceLeadEvent
object
Service lead event
22 properties 3 required
ServiceAppointmentEvent
object
Service appointment event
5 properties 3 required
SalesServices
object
Sales or services summary
3 properties
ShoppersResponse
object
Response containing multiple shoppers with pagination info
2 properties 2 required
EmailOpenEvent
object
Email open event
16 properties 3 required
SaleEvent
object
Sale event
64 properties 3 required
LatestSale
objectnull
Latest sale information for a shopper. Structure similar to LatestLead.
SMSClickEvent
object
SMS click event
16 properties 3 required
LeadHandlingSMSSentEvent
object
Lead handling SMS sent event
16 properties 3 required
EmailSentEvent
object
Email sent event
16 properties 3 required
ServiceROEvent
object
Service repair order event
23 properties 3 required
ShopperEvent
Represents an event associated with a shopper. Events are returned ungrouped in a flat array.
InputTrackingEvent
object
Input tracking event
6 properties 3 required
CustomerLifetimeValue
objectnull
Customer lifetime value information
3 properties
SMSRepliedEvent
object
SMS replied event
16 properties 3 required
LatestLead
objectnull
Latest lead information for a shopper
8 properties
ConversionEvent
object
Conversion event
9 properties 3 required
ADFLead
objectnull
ADF lead information
ShopperEmail
object
Represents an email address associated with a shopper
5 properties 3 required
Pagination
object
Pagination metadata
4 properties 4 required
EmailClickEvent
object
Email click event
16 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

autoleadstar-shoppers-api-openapi.yml Raw ↑

Other APIs AutoLeadStar publishes across the network.

Fullpath MCP Tools
AE Profile APIs.io
AutoLeadStar Activities API
AE Profile APIs.io
AutoLeadStar Appointments API
AE Profile APIs.io
AutoLeadStar Audiences API
AE Profile APIs.io
AutoLeadStar Consents API
AE Profile APIs.io
AutoLeadStar Leads API
AE Profile APIs.io
AutoLeadStar Tasks API
AE Profile APIs.io
#Shoppers
← Back to A APIs
API Details
ID
autoleadstar:autoleadstar-shoppers-api
Base URL
https://api.fullpath.com/v1
Docs
https://developers.fullpath.com/
Provider
AutoLeadStar
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=autoleadstar-shoppers-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/autoleadstar-shoppers-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of AutoLeadStar Shoppers 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.