Scrape Google search results at an insanely fast speed and hassle-free.
Free Plan $0.00 Monthly Subscribe
1,000 Requests / Monthly
Free for Lifetime
No Credit Card Required
Starter Plan $49.99 Monthly Subscribe
25,000 Requests / Monthly
Standard Support
Geo-specific Targets
Accurate Results
Pro Plan $799.99 Monthly Subscribe
1,000,000 Requests / Monthly
Standard Support
Geo-specific Targets
Accurate Results
Enterprise Plan $3,499.99 Monthly Subscribe
5,000,000 Requests / Monthly
Standard Support
Geo-specific Targets
Accurate Results
Custom Plan Volume Monthly Contact Us
Any requests volume you need
Geo-specific Targets
Accurate Results

Scraping Google is a big challenge, especially if you need to track a large amount of keywords periodically. You need a big proxy pool that was not flagged by Google before, and a captcha solver service in order to bypass certain blockers. All these requirements are not only time consuming, but also costly. On the other hand, AvesAPI, the most powerful and blazing fast SERP API service, offers you real-time Google search result data as raw-html or structured json. By using AvesAPI you will no longer need to use any proxy or captcha solver service.

SERP API Reference

This API is organized around REST. Our API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.

Just Getting Started?

Check out our development quickstart guide.


SERP API uses API keys to authenticate requests. You can view and manage your API keys in the Accounts page.

Your API keys carry many privileges, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth.

All requests made to the API must hold a custom HTTP header named "apikey". Implementation differs with each programming language. Below are some samples.

All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API requests without authentication will also fail.


To query the API for search results, simply append the query parameter to the APIs base URL and set it to a search query of your choice.


query (required)

Specify any query to search for.

Location: Query, Data Type: string

type (required)

Type of search.

Location: Query, Data Type: string

device (optional)

Specify which device to use: desktop, or mobile.

Location: Query, Data Type: string

gl (optional)

Specify a country code to use for your query. Download a list of supported 2-letter country codes:

Location: Query, Data Type: string

google_domain (optional)

Specify a Google domain to use for your query. Download a list of supported google domains:

Location: Query, Data Type: string

hl (optional)

Specify a language to use for your query. Download a list of all supported languages:

Location: Query, Data Type: string

location (optional)

Adding a location parameter to your API request helps to gather location-based search results. Download list of our supported places resources.places.json which contains thousands of places as JSON array. If you want to gather local-based results you should use the value of "place_slug" key in the file. For example, "place_slug": "london" Adding location=london parameter to API URL means that you will get search results for London city.

Location: Query, Data Type: string

num (optional)

Specify the number of results to show per page.

Location: Query, Data Type: string

output (optional)

Specify which API response format to return: json or html.

Location: Query, Data Type: string

page (optional)

Specify the number of page between 1-10.

Location: Query, Data Type: string

uule (optional)

Returns the location-based search results.

Location: Query, Data Type: string

** A word enclosed with curly brackets "{ }" in the code means that it is a parameter and it should be replaced with your own values when executing. (also overwriting the curly brackets).

Below is a sample response from the endpoint

If you wish to play around interactively with real values and run code, see...

Rate Limiting

Each subscription has its own rate limit. When you become a member, you start by choosing a rate limit that suits your usage needs. Do not worry; You can upgrade or downgrade your plan at any time. For this reason, instead of starting with a larger plan that you do not need, we can offer you to upgrade your plan after you start with "free" or "gold plan" options and start using the API.

When you reach a rate limit (both daily and monthly), the service will stop responding and returning the HTTP 429 response status code (Too many requests) for each request with the following JSON string body text.

"message":"You have exceeded your daily\/monthly API rate limit. Please review and upgrade your subscription plan at https:\/\/\/subscriptions to continue."

A reminder email will be sent to you when your API usage reaches both 80% and 90%, so that you can take immediate actions such as upgrading your plan in order to prevent your application using the API from being interrupted.

You can also programmatically check your rate limit yourself. As a result of each request made to the APILayer, the following 4 fields provide you with all the necessary information within the HTTP Headers.

x-ratelimit-limit-month: Request limit per month
x-ratelimit-remaining-month: Request limit remaining this month
x-ratelimit-limit-day: Request limit per day
x-ratelimit-remaining-day: Request limit remaining today

You can contact our support unit if you need any assistance with your application regarding to handle the returned result by looking at the header information.

Error Codes

APILayer uses standard HTTP response codes to indicate the success or failure of an API request. In general: Codes in the 2xx range indicate success. Codes in the 4xx range indicate a clientside error, which means that failed given the information provided (e.g., a missing parameter, unauthorized access etc.). Codes in the 5xx range indicate an error with APILayer's servers (normally this should'nt happen at all).

If the response code is not 200, it means the operation failed somehow and you may need to take an action accordingly. You can check the response (which will be in JSON format) for a field called 'message' that briefly explains the error reported.

Status Code Explanation
400 - Bad Request The request was unacceptable, often due to missing a required parameter.
401 - Unauthorized No valid API key provided.
404 - Not Found The requested resource doesn't exist.
429 - Too many requests API request limit exceeded. See section Rate Limiting for more info.
5xx - Server Error We have failed to process your request. (You can contact us anytime)

You can always contact for support and ask for more assistance. We'll be glad to assist you with building your product.