Google Local Services API
Browse all Google APIs39
AI ReadinessNon-Ready (F)39/100
Official vendor OpenAPI document · agent-readyMarketingAdvertisingoauth22 EndpointsREST
For Agents
Pull Local Services Ads account performance reports and detailed lead reports for billing, dispute tracking, and lead quality analysis.
Use for: Get LSA account performance for the last 30 days, Search detailed lead reports filtered by manager account, List all disputed leads in a date range, I want to reconcile LSA charges with our billing data
Not supported: Does not create or edit ads, manage budgets, or change service-area settings - use only to pull account-level and detailed lead reporting data.
The Local Services API gives Local Services Ads providers and their agencies programmatic access to two reporting datasets: account-level performance reports summarising spend, leads, and impressions, and detailed lead reports showing per-lead metadata such as charge amount, lead type, and dispute status. It is a read-only API designed for billing reconciliation, lead quality analysis, and feeding LSA performance data into business intelligence systems.
Install Jentic One Beta
Connect the Local Services API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Local Services API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Flocalservices" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Flocalservices" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Local Services API.
Search Local Services Ads account-level performance reports across one or more accounts
Search detailed lead reports for individual lead events with charge and category data
Filter reports by start date, end date, and manager customer ID
Identify disputed leads and track their resolution status
Reconcile LSA charges against an internal billing system
Aggregate spend and lead counts by category for a service area
Use Cases
Patterns agents use Local Services API for, with concrete tasks.
★ LSA billing reconciliation
Multi-location service businesses reconcile their Local Services Ads invoices by pulling detailed lead reports and matching each charged lead to a CRM record. Calling /v1/detailedLeadReports:search with a date range returns charge amount, lead category, and dispute status for every lead, which an agent can compare against expected internal data.
Search detailedLeadReports for the last invoice period and join each charged lead to the CRM by phone number.
Lead dispute tracking
When a Local Services Ads lead is invalid (spam, wrong service area, duplicate) advertisers can dispute the charge inside the LSA console. Detailed lead reports include the dispute status of every lead so an agency agent can list pending or resolved disputes and chase them up without logging into the UI.
Filter detailedLeadReports.search results to those with disputeStatus=DISPUTED and produce a CSV grouped by service category.
Performance analytics for an agency
Agencies managing many LSA accounts feed daily account performance into BI tools to compare spend efficiency across clients. /v1/accountReports:search returns daily metrics - leads, impressions, spend - by account ID, which a scheduled agent can pull into BigQuery or a sheet.
Search accountReports for all child customer IDs of a manager account for the last 7 days and load the result into BigQuery.
Agent-driven LSA performance brief via Jentic
A weekly performance agent can query both account and lead reports through Jentic and produce a natural-language brief for the account manager. Jentic surfaces the two search operations with their full filter parameter sets, so the agent can ask for date ranges and account IDs without learning the LSA API.
Run google_localservices_search_account_reports for the last 7 days and write a 5-bullet performance summary.
Key Endpoints
2 endpoints — the local services api gives local services ads providers and their agencies programmatic access to two reporting datasets: account-level performance reports summarising spend, leads, and impressions, and detailed lead reports showing per-lead metadata such as charge amount, lead type, and dispute status.
METHOD
PATH
DESCRIPTION
GET
/v1/accountReports:search
Search account-level Local Services Ads performance reports
GET
/v1/detailedLeadReports:search
Search detailed per-lead reports
GET
/v1/accountReports:search
Search account-level Local Services Ads performance reports
GET
/v1/detailedLeadReports:search
Search detailed per-lead reports
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
L
Local Services API
- Non-Ready (F)39/100
51
Foundational Compliance56
Developer Experience & Jentic Compatibility18
AI-Readiness & Agent Experience94
Agent Usability63
Security63
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
51
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: C-Signals: 4
92%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
10%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
18
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
72%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
63
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
62%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
63
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B-Signals: 1
62%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Local Services API by hand means configuring Google Ads OAuth2, managing the adwords scope and a developer token, refreshing access tokens, and shaping its report search queries yourself. Through Jentic you install once, import the Local Services API from the API Directory, store the credential once, and your agent calls it.
Permission scoping
This API exposes only account-level and detailed lead reporting, passing its filters as query parameters rather than a resource in the URL path, so scope the agent to the operations it needs, such as searching account reports or detailed lead reports. Both endpoints are read-only, so the agent can pull reporting data but never edit ads or budgets.
Credential isolation
Your Google Ads OAuth credential and developer token are stored once, encrypted, by your own Jentic One instance and injected at execution time as a short-lived adwords access token. The refresh token and developer token never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'pull local services account reports' or 'list detailed lead reports', and Jentic returns the matching v1 search operation with its query parameters so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Local Services API through Jentic.
What authentication does the Local Services API use?
OAuth 2.0 with the https://www.googleapis.com/auth/adwords scope, the same scope used by the Google Ads API. The calling user must have access to the LSA account or its manager account. Through Jentic the credentials sit in the encrypted vault and only a short-lived access token reaches the agent.
Can I create or edit Local Services Ads with this API?
No. The v1 API is read-only and exposes only accountReports:search and detailedLeadReports:search. Ad and budget changes must still be made through the LSA console or the underlying Google Ads API.
What are the rate limits for the Local Services API?
Quota is shared with the Google Ads API service in the same Google Cloud project - 15,000 operations per day by default with a burst limit of 1 query per second per user. Agencies pulling many accounts should batch with backoff on 429 responses.
How do I pull lead reports through Jentic?
Run jentic search 'pull local services ad lead reports' to find GET /v1/detailedLeadReports:search, jentic load to retrieve its query parameters, then jentic execute with managerCustomerId, startDate, and endDate. Jentic returns the paginated lead list.
Does this API include lead phone numbers?
Detailed lead reports include the phone call duration, lead type, and consumer phone number for phone leads, plus the message body for message leads, subject to Google's privacy policies. Use the data only for the purposes the customer consented to.
Is the Local Services API free?
Yes. The reporting API has no per-call charge - you only pay for the underlying Local Services Ads charges that the reports describe.
Can I limit what my agent is allowed to do with the Local Services API?
Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent can use, so you can allow it to search account-level performance reports while withholding detailed lead reports, or grant only the operation it needs. Both operations are read-only, passing their filters as query parameters, so the agent can pull reporting data but can never create or edit ads, change budgets, or alter service-area settings. Your Google Ads credential stays with your instance and reaches the agent only as a short-lived token at execution time.
GET STARTED