Google Business Profile API: What It Can and Can't Do
What the API can read and write, how access is granted, and why ranking data is the one thing it will never return.
The Google Business Profile API lets you read and write profile data programmatically. For agencies and tools managing many locations, it is the only realistic route.
But there is one thing the API does not do, and that is the point of this piece.
What the API can do
Read: location details, categories, opening hours, attributes, reviews, posts, media, and profile performance metrics (views, searches, direction requests).
Write: update location information, create and schedule posts, reply to reviews, upload photos, change opening hours.
Bulk operations: apply the same change across many locations at once. For a hundred-branch brand, the difference between entering holiday hours by hand and doing it through the API is the difference between days and minutes.
What the API cannot do
It cannot return ranking data. The API does not tell you where a business sits in map results, and it won't. The reason isn't technical, it's logical: there is no single ranking. Map results change with where the searcher is standing, so producing "your position is N" requires first answering "seen from where".
Ranking is only found by measuring it: splitting the area into a grid and searching from every point. That data doesn't come from the API; it is collected from search results.
It cannot return competitor data. The API only exposes profiles you manage.
How access is granted
You create a project in Google Cloud Console, enable the relevant APIs, configure OAuth. Then you apply to Google for quota — and that step is not instant. The form asks what your tool does, how many locations it will manage, and how the data will be used.
Approval time varies. If an application is rejected the reason is given, and you can correct it and reapply.
If you're building your own tool
Quota. There is a daily request limit, scaled to location count. Hitting it during bulk work is common.
Review reply permission. The account must genuinely hold authority over the profile; write access doesn't work until ownership transfer completes.
Data freshness. The metrics the API returns are not real time; a lag of several days is normal.
The practical conclusion
There are two separate jobs and they come from two different sources:
- Managing the profile — the API's job. Bulk edits, posts, review replies.
- Knowing where you appear — measurement's job. A grid scan, point by point.
Substituting one for the other is the most common error in this area. If a tool claims it reads rankings "from the API", either it is actually measuring them, or what it says isn't accurate.