Local Services API

Name: Local Services API API
Brand: Local Services API
Availability: InStock

✓ Official Vendor SpecMarketingAdvertisingoauth22 EndpointsREST

For Agents

Pull Local Services Ads account performance reports and detailed lead reports for billing, dispute tracking, and lead quality analysis.

Quickstart

Get started with Local Services API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"pull local services ads lead reports"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Local Services API 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

GET STARTED

Start building with Local Services API API

Explore with Jentic

View OpenAPI Document

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.

Use Cases

Patterns agents use Local Services API 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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Google Ads OAuth credentials and developer tokens are stored encrypted in the Jentic vault. Agents receive a short-lived access token scoped to https://www.googleapis.com/auth/adwords; the refresh token and developer token never enter the agent context.

Intent-based discovery

Agents search Jentic with phrases like 'pull lsa account reports' or 'list disputed local services leads' and Jentic returns the matching v1 search operation with the right query parameter list already documented.

Time to first call

Direct integration: 4-8 hours to wire OAuth, set up the developer token, and parse the report rows. Through Jentic: under 20 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

AdSense Management API

AdSense reports on display ad earnings; Local Services reports specifically on LSA lead-based ads

Choose AdSense for publisher display revenue reporting; choose Local Services for LSA lead and dispute reporting.

Complementary

My Business Business Information API

Business Information manages a service location's profile; Local Services reports on the ads run for that location

Pair them: keep the business profile fresh with Business Information, then pull LSA performance for that location with Local Services.

Alternative

Search Ads 360 Reporting API

Search Ads 360 reports on cross-platform paid search performance; Local Services reports specifically on LSA

Choose Search Ads 360 for unified cross-platform reporting; choose Local Services API for LSA-specific lead and dispute detail.

FAQs

Specific to using Local Services API 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.