Google Scholar Author API
Our Google Scholar Author API allows you to scrape author results from the Google Scholar Author search page. The API is accessed through the following endpoint:
A user may query the following:
https://serpapi.com/search?engine=google_scholar_author utilizing a
GET request. Head to the playground for a live and interactive demo.
Parameter defines the language to use for the Google Scholar Author search. It's a two-letter language code. (e.g.,
en for English,
es for Spanish, or
fr for French). Head to the Google languages page for a full list of supported Google languages.
Parameter defines the result offset. It skips the given number of results. It's used for pagination. (e.g.,
0 (default) is the first page of results,
20 is the 2nd page of results,
40 is the 3rd page of results, etc.).
Parameter will force SerpApi to fetch the Google Scholar Author results even if a cached version is already present. A cache is served only if the query and all parameters are exactly the same. Cache expires after 1h. Cached searches are free, and are not counted towards your searches per month. It can be set to
false (default) to allow results from the cache, or
true to disallow results from the cache. no_cache and async parameters should not be used together.
Parameter defines the way you want to submit your search to SerpApi. It can be set to
false (default) to open an HTTP connection and keep it open until you got your search results, or
true to just submit your search to SerpApi and retrieve them later. In this case, you'll need to use our Searches Archive API to retrieve your results. async and no_cache parameters should not be used together. async should not be used on accounts with Ludicrous Speed enabled.
JSON output includes structured data for articles, citation, cited by, co-authors, and more.
A search status is accessible through
search_metadata.status. It flows this way:
Error. If a search has failed,
error will contain an error message.
search_metadata.id is the search ID inside SerpApi.
HTML output is useful to debug JSON results or support features not supported yet by SerpApi.
HTML output gives you the raw HTML results from Google Scholar Author page.