> ## Documentation Index
> Fetch the complete documentation index at: https://aisa.one/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Setting Business Data Google Reviews Tasks
> Queues Google Business Profile reviews, returning a task id.
Queues Google Business Profile reviews, returning a task `id`. Asynchronous: submit returns a task `id` in `tasks[0].id`, fetch returns the result once ready, and the charge lands on the submit - fetching is free, including re-fetching. Wrapped in DataForSEO's envelope: data in `tasks[0].result`, outcome in `tasks[0].status_code` - a rejected request still returns HTTP 200. Retrieve with `get_dataforseo_business_google_reviews_fetch`; the profile itself is `post_dataforseo_business_google_gmb_info_live`.
## Example
```bash REST theme={null}
curl -X POST "https://api.aisa.one/apis/v1/dataforseo/business_data/google/reviews/task_post" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d '[{"keyword": "...", "cid": "...", "place_id": "..."}]'
```
```jsonc MCP theme={null}
// Copy this whole block into Claude Code, Codex, Cursor or any coding agent.
// It carries everything needed to connect, authorize and run this example —
// no key to paste, one click of Allow in the browser.
{
"operation_id": "post_dataforseo_business_google_reviews_submit",
"arguments": {},
"max_price_usd": 0.05
}
// ── for the agent ─────────────────────────────────────────────────────────
// Register the AIsa MCP server, then call its `use` tool with the JSON above.
// name aisa
// endpoint https://mcp.aisa.one/mcp
// transport streamable-http
// auth OAuth. The server publishes RFC 9728 metadata, so open a
// browser and the user clicks Allow once — nothing to paste.
// If AISA_API_KEY is set, send it as a bearer header instead.
// Use your own MCP mechanism, not a hand-edited config file:
// Codex codex mcp add aisa --url https://mcp.aisa.one/mcp
// Claude Code claude mcp add --transport http -s user aisa https://mcp.aisa.one/mcp
// Cursor / VS Code a "url" entry for https://mcp.aisa.one/mcp in the MCP config
// The server lists five tools over https://mcp.aisa.one/servers worth of APIs:
// search, get_details, use, batch_use, list_categories. search and
// get_details are free; use is billed per call and max_price_usd refuses
// anything above the cap before spending. This operation's full contract —
// every argument, the response shape, the price and the pitfalls — is at
// https://aisa.one/docs/api-reference/dataforseo/post_dataforseo-business-data-google-reviews-task-post.md
// Then run the call and show me the result.
```
**First time?** Point any MCP client at `https://mcp.aisa.one/mcp` — Claude
Code, Codex, Cursor, VS Code and the rest. Authorization is OAuth: the client
opens a browser, you click Allow once, and there is no key to paste. The
commands per client, and what each call costs, are on
[aisa.one/mcp](https://aisa.one/mcp#connect).
[Set this endpoint up in your agent →](https://aisa.one/mcp?from=/api-reference/dataforseo/post_dataforseo-business-data-google-reviews-task-post)
## OpenAPI
````yaml openapi/dataforseo.json POST /dataforseo/business_data/google/reviews/task_post
openapi: 3.0.3
info:
title: DataForSEO API
version: 1.0.0
description: DataForSEO API endpoints exposed through the AIsa unified gateway.
servers:
- url: https://api.aisa.one/apis/v1
security:
- BearerAuth: []
paths:
/dataforseo/business_data/google/reviews/task_post:
post:
summary: Setting Business Data Google Reviews Tasks
description: >-
This endpoint provides results from the “Reviews” element of Google
SERPs. The results are specific to the selected location (see the List
of Locations) and language (see the List of Languages) parameters.
operationId: post_dataforseo_business_google_reviews_submit
requestBody:
required: true
content:
application/json:
schema:
type: array
items:
type: object
properties:
keyword:
type: string
description: >-
*keyword* **required field if you don’t specify `cid` or
`place_id`** the keyword you specify should indicate the
name of the local establishment; you can specify **up to
700 characters** in the `keyword` filed; all %## will be
decoded (plus character ‘+’ will be decoded to a space
character) if you need to use the “%” character for your
`keyword`, please specify it as “%25”; if this field
contains such parameters as ‘allinanchor:’, ‘allintext:’,
‘allintitle:’, ‘allinurl:’, ‘define:’, ‘filetype:’, ‘id:’,
‘inanchor:’, ‘info:’, ‘intext:’, ‘intitle:’, ‘inurl:’,
‘link:’, ‘related:’, ‘site:’, **the charge per task will
be multiplied by 5** Note: queries containing the ‘cache:’
parameter are not supported and will return a validation
error learn more about rules and limitations of `keyword`
and `keywords` fields in DataForSEO APIs in this [Help
Center
article](https://dataforseo.com/help-center/rules-and-limitations-of-keyword-and-keywords-fields-in-dataforseo-apis)
cid:
type: string
description: >-
*unique, google-defined id of the business entity*
**required field if you don’t specify `keyword` or
`place_id`** example: `194604053573767737` learn more
about the identifier in [this help center
article](https://dataforseo.com/help-center/what-is-cid-place-id-feature-id)
place_id:
type: string
description: >-
*identifier of the business entity in Google Maps*
**required field if you don’t specify `keyword` or `cid`**
example: `GhIJQWDl0CIeQUARxks3icF8U8A` learn more about
the identifier in [this help center
article](https://dataforseo.com/help-center/what-is-cid-place-id-feature-id)
priority:
type: integer
description: >-
*task priority* optional field can take the following
values: 1 – normal execution priority (set by default) 2 –
high execution priority You will be additionally charged
for the tasks with high execution priority.
location_name:
type: string
description: >-
*full name of search engine location* **required field if
you don’t specify** `location_code` or
`location_coordinate` **if you use this field, you don’t
need to specify `location_code` or `location_coordinate`**
you can receive the list of available locations with
`location_name` by making a separate request to the
`https://api.dataforseo.com/v3/business_data/google/locations`
example: `London,England,United Kingdom`
location_code:
type: integer
description: >-
search engine location code required field if you don't
specify location_name_or location_coordinate if you use
this field, you don't need to specify location_name or
location_coordinate you can receive the list of available
locations with location_code by making a separate request
to the
https://api.dataforseo.com/v3/business_data/google/locations
example: 2840
location_coordinate:
type: string
description: >-
GPS coordinates of a location required field if you don't
specify location_name_or location_code if you use this
field, you don't need to specify location_name or
location_code location_coordinate parameter should be
specified in the "latitude,longitude,radius" format the
maximum number of decimal digits for "latitude" and
"longitude": 7 the minimum value for "radius": 199.9
example: 53.476225,-2.243572,200
language_name:
type: string
description: >-
*full name of search engine language* **required field if
you don’t specify** `language_code` **if you use this
field, you don’t need to specify `language_code`** you can
receive the list of available languages with
`language_name` by making a separate request to the
`https://api.dataforseo.com/v3/business_data/google/languages`
example: `English`
language_code:
type: string
description: >-
search engine language code required field if you don't
specify language_name if you use this field, you don't
need to specify language_name you can receive the list of
available languages with their language_code_by making a
separate request to the
https://api.dataforseo.com/v3/business_data/google/languages
example: en
depth:
type: integer
description: >-
*parsing depth* optional field number of reviews in SERP
we strongly recommend setting the parsing depth in the
multiples of ten, because our systems processes ten
reviews in a row default value: `10` maximum value: `4490`
**Your account will be billed per each SERP containing up
to 10 results;** Setting depth above 10 may result in
additional charges if the search engine returns more than
10 results.
sort_by:
type: string
description: >-
*results sorting parameters* optional field you can use
this field to sort the results possible types of sorting:
`newest` – sort by newest first `highest_rating` – sort by
highest rating `lowest_rating` – sort by lowest rating
`relevant` – sort by relevance default value: `relevant`
tag:
type: string
description: >-
*user-defined task identifier* optional field *the
character limit is 255* you can use this parameter to
identify the task and match it with the result you will
find the specified `tag` value in the `data` object of the
response
postback_url:
type: string
description: >-
URL for sending task results optional field once the task
is completed, we will send a POST request with its results
compressed in the gzip format to the postback_url you
specified you can use the ‘$id’ string as a $id variable
and ‘$tag’ as urlencoded $tag variable. We will set the
necessary values before sending the request. example:
http://your-server.com/postbackscript?id=$id
http://your-server.com/postbackscript?id=$id&tag=$tag
Note: special characters in postback_url will be
urlencoded; i.a., the # character will be encoded into %23
learn more on our [Help
Center](https://dataforseo.com/help-center/pingbacks-postbacks-with-dataforseo-api)
pingback_url:
type: string
description: >-
*notification URL of a completed task* optional field when
a task is completed we will notify you by GET request sent
to the URL you have specified you can use the ‘$id’ string
as a `$id` variable and ‘$tag’ as urlencoded `$tag`
variable. We will set the necessary values before sending
the request. example:
`http://your-server.com/pingscript?id=$id`
`http://your-server.com/pingscript?id=$id&tag=$tag`
**Note:** special characters in `pingback_url` will be
urlencoded; i.a., the `#` character will be encoded into
`%23`learn more on our [Help
Center](https://dataforseo.com/help-center/pingbacks-postbacks-with-dataforseo-api)
allOf:
- anyOf:
- required:
- location_name
- required:
- location_code
- required:
- location_coordinate
- anyOf:
- required:
- language_name
- required:
- language_code
- anyOf:
- required:
- keyword
- required:
- cid
- required:
- place_id
responses:
'200':
description: Successful operation
content:
application/json:
schema:
type: object
properties:
version:
type: string
description: '*the current version of the API*'
version.status_code:
type: integer
description: >-
*general status code* you can find the full list of the
response codes
[here](https://docs.dataforseo.com/v3/appendix/errors.md)
**Note:** we strongly recommend designing a necessary
system for handling related exceptional or error
conditions
version.status_message:
type: string
description: >-
*general informational message* you can find the full list
of general informational messages
[here](https://docs.dataforseo.com/v3/appendix/errors.md)
version.time:
type: string
description: '*execution time, seconds*'
version.cost:
type: number
description: '*total tasks cost, USD*'
version.tasks_count:
type: integer
description: '*the number of tasks in the **`tasks`**array*'
version.tasks_error:
type: integer
description: >-
*the number of tasks in the **`tasks`** array returned
with an error*
tasks:
type: array
items:
type: string
description: '*array of tasks*'
tasks.id:
type: string
description: >-
task identifier unique task identifier in our system in
the
[UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier)
format
tasks.status_code:
type: integer
description: >-
status code of the task generated by DataForSEO, can be
within the following range: 10000-60000 you can find the
full list of the response codes here
tasks.status_message:
type: string
description: >-
informational message of the task you can find the full
list of general informational messages here
tasks.time:
type: string
description: '*execution time, seconds*'
tasks.cost:
type: number
description: total tasks cost, USD
tasks.result_count:
type: integer
description: '*number of elements in the `result` array*'
tasks.path:
type: array
items:
type: string
description: '*URL path*'
tasks.data:
type: object
description: >-
*contains the same parameters that you specified in the
POST request*
result:
type: array
items:
type: string
description: '*array of results* in this case, the value will be `null`'
'400':
description: Bad request
'401':
description: Unauthorized
'429':
description: Rate limit exceeded
'500':
description: Internal server error
components:
securitySchemes:
BearerAuth:
type: http
scheme: bearer
````
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.