Most agencies hit the same wall with Local Services Ads (LSA). One client is easy to watch in Google’s interface. Fifteen clients means fifteen logins, fifteen lead lists to rate, and a monthly report built by copy and paste.
The Google Ads API, which exposes Local Services Ads data, is how you get past that wall, and it does more for LSA than most agencies realise. It also has gaps that matter, and the move to Performance Max changed how LSA data shows up in it. This guide is for agency owners deciding whether to build on the API, and for the developer they’ll hand it to. Everything below comes from Google’s Google Ads API documentation, last updated October 30, 2026, unless we say otherwise. Source: Google Ads API documentation
Which LSA API, exactly
“The LSA API” can mean two things:
- The Google Ads API. This is where Google is putting its LSA development. LSA campaigns, leads and lead conversations are exposed as resources you query alongside the rest of a Google Ads account, and the newest LSA changes (Performance Max campaigns, coupon leads) are documented here.
- The older Local Services API (
localservices.googleapis.com), which offers account-level and detailed lead reports for linked LSA accounts. Some older reporting tools still run on it. Google’s client library documentation marks at least one of its lead ID fields as deprecated in favour of the Google Ads lead ID.
If you’re starting a new LSA API project, start with the Google Ads API. The rest of this guide is about that one.
What you can read with the Local Services Ads API
Google exposes four read-only LSA resources. They only return data if the client account has an LSA campaign (standard or Performance Max).
| Resource | What it gives you | Agency use |
|---|---|---|
local_services_lead | Lead type, category and service, contact details, status, creation time, whether the lead was charged, credit details, any note, and whether feedback was submitted | Lead counts, charged vs. credited, unrated leads per client |
local_services_lead_conversation | Every call and message on a lead: channel, who spoke (advertiser or consumer), time, call duration, recording URL, message text | Answer-rate and response-time reporting, call review |
local_services_verification_artifact | Business-level verification requests: licenses, insurance, background checks, registration, status and rejection reasons | Catch an expiring license or rejected insurance certificate before ads pause |
local_services_employee | Employee profile data the advertiser uploaded | Keep field-staff records in sync |
A starting query for a monthly lead report looks like this. You query it with GoogleAdsService.Search for each client account:
SELECT local_services_lead.id,
local_services_lead.lead_type,
local_services_lead.lead_status,
local_services_lead.lead_charged,
local_services_lead.lead_feedback_submitted,
local_services_lead.creation_date_time,
local_services_lead.campaign
FROM local_services_lead
WHERE local_services_lead.creation_date_time > '2026-10-01 00:00:00'
Lead and conversation times come back in the client account’s time zone, which matters when you compare clients across states.
What you can change
The API isn’t read-only. For LSA you can also:
- Rate leads.
LocalServicesLeadService.ProvideLeadFeedbacksubmits lead feedback, the same kind of survey behind “Rate this lead” in the interface: a survey answer plus a satisfied or dissatisfied reason, with a free-text comment required when the reason is “other.” The response tells you whether a bonus credit was issued or rejected, and Google says an issued bonus credit becomes usable in about two months. - Add to a lead’s conversation history with
AppendLeadConversation. - Change campaign status and budget.
- Set bidding on standard LSA campaigns: manual cost per lead by category, or Maximize Conversions.
- Set ad schedules, location targeting and service types.
- Check eligibility.
LocalServicesEligibilityService.CheckLocalServicesEligibilitytakes a customer ID and a Business Profile listing ID.
Lead rating is the one agencies should care about most. Google reassesses charged leads and issues credits automatically when it later judges a lead low quality, and it asks advertisers to rate leads so it can send better-matched ones. Source: Google Local Services Help Across a client book, “rate every lead” is a job a person won’t do consistently and a script will. The lead_feedback_submitted field gives you the to-do list.
What the Local Services Ads API can’t do
Plan around these before you promise a client anything:
- No creating or removing standard LSA campaigns. New pay-per-lead accounts still start through Google’s LSA sign-up. Ad groups, ads and most criteria inside standard LSA campaigns can’t be created, changed or read.
- No health care leads. Google says leads in health care categories aren’t available through the API. Dental, chiropractic and other health care clients need another reporting method. Our LSA categories guide lists which categories that covers.
- Contact details disappear on wiped-out leads. When a lead’s status is
WIPED_OUT, its contact details come back empty. - Email moved out. From API version 25, the lead contact email field was removed; a phone number extension field is available instead.
- Call recordings need a signed-in user. Opening a recording URL requires a Google login with at least read-only access to the client account, so you can’t just paste the link into a client report.
- Pull conversations per lead. Google warns that requesting all conversations at once can be slow, and recommends filtering by lead.
The Performance Max change that breaks old reports
Google is moving LSA into Google Ads as Performance Max campaigns with pay-per-lead goals, in waves through 2027. Source: Google Ads Help In the API, that’s a different campaign type.
- Standard LSA campaigns have the channel type
LOCAL_SERVICES. - Migrated campaigns are
PERFORMANCE_MAXcampaigns withpmax_campaign_settings.local_services_enabledset to true.
Any report, dashboard or notification that finds LSA campaigns by filtering on advertising_channel_type = 'LOCAL_SERVICES' will miss every client that has migrated. Leads still come through local_services_lead for both types, and Google’s documentation shows how to separate them with the lead’s campaign field.
The version timeline matters if you maintain code:
| API version | Local Services Performance Max support |
|---|---|
| v24 and v25 | Read and update existing LSA Performance Max campaigns created in the interface (allowlisted accounts) |
| v26 | Create new LSA Performance Max campaigns through the API (US only), using a linked Business Profile location; coupon leads supported |
Two migration side effects also land on whoever owns the data:
- History doesn’t move. Google says past performance reports (impressions, clicks, spend and ad-level data) won’t carry over into Google Ads, though past leads, message history and recordings do move to the new Leads page.
- Recordings expire. After migration, Google stores call recordings and sensitive conversation history for up to 30 days. Source: Google Ads Help If call review or dispute evidence matters to your clients, archive recordings on a schedule.
Our agency migration playbook covers the non-technical side of the move.
Getting LSA API access
Access changed in 2026. Google says developer tokens were sunset on September 9, 2026, and API access levels are now managed per Google Cloud project. Source: Google Ads API access levels
| Access level | Can reach | Daily operations |
|---|---|---|
| Test | Test accounts only | 15,000 |
| Explorer | Test and production accounts | 2,880 on production accounts |
| Basic | Test and production accounts | 15,000 |
| Standard | Test and production accounts | Unlimited |
Enabling the Google Ads API on a Cloud project grants Test access, and Google says it may upgrade a project to Explorer automatically after you apply. Calls need the adwords OAuth scope and a Google login that can reach the client accounts, which for an agency means your manager account.
Check Google’s current quota rules against your plan before you build: daily lead pulls, per-lead conversation queries and lead ratings across a large client book all count, and frequent polling or bulk backfills are what push a project past Explorer.
Build it, or use a tool built on it
Building on the LSA API makes sense if you have a developer on staff, want LSA data inside a reporting stack you already run, and are ready to maintain it through the migration and Google’s regular version releases.
What usually goes wrong with in-house builds:
- Reports filtered on the old channel type go quiet as clients migrate, and nobody notices for a month.
- Lead rating gets built, then breaks on a version change, and leads go unrated.
- The API tells you a call was missed. It doesn’t answer the call. The business still needs someone, or something, to pick up.
That last point is why we built LSA Command the way we did. The data is only useful if the lead gets answered. For every client account, calls ring the client’s team first and AI answers within 30 seconds if nobody picks up, message leads get answered, robocalls get blocked, every lead is rated back to Google, and you and the client get a text and email notification for every lead.
If you’re comparing tools, our guides to LSA reporting software and connecting LSA to client management software give you the questions to ask. Add one: “Does it find leads on migrated Performance Max accounts?”
Frequently asked questions
Is there an API for Google Local Services Ads?
Yes. LSA leads, lead conversations, verification records and campaign settings are available through the Google Ads API. An older, separate Local Services API also offers account and lead reports.
Can you rate or dispute LSA leads through the API?
You can rate them. The ProvideLeadFeedback method submits the lead survey, and the response tells you whether a bonus credit was issued. Google now issues most credits automatically, so rating every lead is the part to automate.
Can I pull call recordings from the Local Services Ads API?
The lead conversation resource includes a recording URL, but opening it requires a Google login with at least read-only access to the client account. After migration, Google stores recordings for up to 30 days, so archive the ones you need.
Why did my LSA report stop showing leads after migration?
Migrated LSA campaigns are Performance Max campaigns with local services enabled, not the old Local Services campaign type. Reports that filter on the old channel type will miss them. Query leads through the local_services_lead resource and use its campaign field instead.
Do I need a developer token for the Google Ads API?
Not anymore. Google says developer tokens were sunset on September 9, 2026. Access levels are now managed per Google Cloud project, starting with Test access and moving up to Explorer, Basic or Standard.
Want a second set of eyes on a client’s LSA account?
100% of calls answered within 30 seconds. Your client's team gets the first 10 to 15 seconds, then AI answers. AI messaging replies instantly. Every lead gets notes and notifications, with High-value leads identified.
Bring one client's Google LSA account to a 30-minute walkthrough and the LSA Command team audits it live. No passwords change hands, and you keep what the audit finds whether or not you go ahead.
From 28% to 100% of leads answered within 30 seconds, across three pool contractor accounts, December 2025 to April 2026 (case studies).
Google Local Services Ads is all LSA Command does. Built for agencies only. $200 per month per client.
Black Friday offer: get 5 client locations live on LSA Command by December 15, 2026, and the first month is free on every location you add before December 15.
Book my 30-minute walkthrough Call 989-712-4370 Text 989-712-4370