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 Audiences API

Operations related to audiences

Documentation Provider Profile APIs.io OpenAPI GitHub

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

Tagged areas include Audiences. 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 4 operations across 4 paths, and defines 15 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.

4 operations 4 paths 15 schemas 4 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 Audiences 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 4

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

audiences 4

Operations related to audiences

GET
/dealerships/{dealershipId}/shoppers/{id}/audiences
List audiences for a shopper
listShopperAudiences 5 params → 200204401404500
GET
/dealerships/{dealershipId}/audiences
List audiences
listAudiences 4 params → 200204401500
GET
/dealerships/{dealershipId}/audiences/{id}
Get a single audience
getAudienceById 3 params → 200401404500
GET
/dealerships/{dealershipId}/audiences/{id}/shoppers
List shoppers in an audience
listAudienceShoppers 5 params → 200204401404500

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are PrimaryContact (24 properties), Shopper (23 properties), ContactDetail (22 properties), Audience (12 properties). Each schema is shown below with its type and property counts.

LatestLead
objectnull
Latest lead information for a shopper
8 properties
PrimaryContact
objectnull
Primary contact information for a shopper. Extended version available in single shopper responses.
24 properties
Audience
object
Represents an audience (saved shopper filter). Additional fields are available via the embed parameter.
12 properties 10 required
AudiencesResponse
object
Response containing multiple audiences with pagination info
2 properties 2 required
Location
objectnull
Location information for a shopper
7 properties
ADFLead
objectnull
ADF lead information
LatestSale
objectnull
Latest sale information for a shopper. Structure similar to LatestLead.
ContactDetail
objectnull
Contact information for a shopper
22 properties
Vehicle
objectnull
Vehicle information
6 properties
ErrorResponse
object
Standard structure for API error responses
3 properties 2 required
AudienceShoppersResponse
object
Response containing shoppers in an audience with pagination info
2 properties 2 required
Pagination
object
Pagination metadata
4 properties 4 required
SalesServices
object
Sales or services summary
3 properties
CustomerLifetimeValue
objectnull
Customer lifetime value information
3 properties
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

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

autoleadstar-audiences-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 Consents API
AE Profile APIs.io
AutoLeadStar Leads API
AE Profile APIs.io
AutoLeadStar Shoppers API
AE Profile APIs.io
AutoLeadStar Tasks API
AE Profile APIs.io
#Audiences
← Back to A APIs
API Details
ID
autoleadstar:autoleadstar-audiences-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-audiences-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/autoleadstar-audiences-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 Audiences 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.