serpapi
[Google Local API] `serpapi_pagination` links in the response adds a UULE
A customer reported that serpapi_pagination.next_link in the response adds a UULE, which was not the case before. If the location is already added in the request, this results in an error because for Google Local API the location and UULE cannot be used together.
Initial request (No UULE, only location specified):
The next page links (UULE and location specified which result in error):
Documentation:
Public links: Playground 1 | Documentation
Internal links: Intercom | Search Inspect 1
I'm experiencing a similar error when using Google Local Search through SerpApi module in Make.com platform
The module works as expected when pagination limit is set to 1, but when pagination limit is set to any value above 1, the uule parameter seems to be submitted in background even though the uule/encoded location field in module is left blank
Thank you very much @marcup for your report, and we apologize for the issue.
As a temporary solution, you can remove one of the values (UULE or location) when performing a pagination. Assuming it's possible on Make.
@hilmanski with Make being a no/low-code platform, you can only control the fields that Make provides, the whole issue here is that UULE gets added (in background, when pagination > 1) even though no explicit value is set for it in the form. So if you set the module like in screenshots below it will result in error (as in screenshot in my earlier post).
scroll down...
removing location isn't a real workaround when the goal is to search in a specific location. The only workaround would be to use the offset field (which does work), however this would require extra automation complexity in make to create multiple calls with different offsets depending on desired result amount and then aggregate results from multiple calls.
Thanks for clarifying this @marcup! This indeed looks like the issue with serpapi_pagination keys, including the uule parameter. We're yet to address this, unfortunately. We'll get back to you as soon as possible.
In the meantime, I'll play around with Make to see if there is an easy workaround that doesn't include much complexity.
Thank you for your patience.
@andypple83, can you unassign yourself if you do not plan to work on this in the next month?
FYI @andypple83 @marm123 The Google Local Search option is no longer available in the Make.com SerpAPI module. Meaning that users can no longer see it when you add the SerpAPI module to a scenario. It is however still usable in scenarios that have added it while it was still available, or when you create a new make scenario by using a scenario blueprint that contains the SerpAPI module with Google Local Search option.
Thank you for the note @duativ. We'll check why it's not available and will get back to you once we have any updates.
@marm123 sorry I didn't didn't mean to report this as an issue, more as an FYI. It's unavailable because make.com decided to make it unavailable / no longer offer it (but still support for users like myself that still have it in their scenarios. for now at least). Which means for make.com users it's probably less urgent for you to fix this now. It could potentially be used, through generic API call route in Make, but I haven't looked into that yet.
Makes sense, thanks @duativ! In any case, we'd expect Make not to remove our official integrations without prior notice or explanation. We'll investigate this nonetheless. Appreciate bringing this up to our attention!