> ## 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 Live ‘Bing Keyword Performance’ Tasks
> How a list of keywords performs in Bing Ads for a given device and match type.
How a list of `keywords` performs in Bing Ads for a given `device` and `match` type. ⚠️ **`language_name` is required and its absence is reported as `Invalid Field: 'language_name'` inside an HTTP 200** - the message means missing as well as wrong. Wrapped in DataForSEO's envelope: data in `tasks[0].result`, outcome in `tasks[0].status_code` - a rejected request still returns HTTP 200. Valid pairs come from `get_dataforseo_keywords_bing_kw_performance_locales`. The submit and fetch twins of this endpoint do the same work asynchronously, at the same price, for batches too large to wait on.
## Example
```bash REST theme={null}
curl -X POST "https://api.aisa.one/apis/v1/dataforseo/keywords_data/bing/keyword_performance/live" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d '[{"keywords": "...", "device": "...", "match": "..."}]'
```
```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_keywords_bing_kw_performance_live",
"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-keywords-data-bing-keyword-performance-live.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-keywords-data-bing-keyword-performance-live)
## OpenAPI
````yaml openapi/dataforseo.json POST /dataforseo/keywords_data/bing/keyword_performance/live
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/keywords_data/bing/keyword_performance/live:
post:
summary: Setting Live ‘Bing Keyword Performance’ Tasks
description: >-
You can receive a set of keyword performance stats for a group of
keywords depending on the specified match type, location and language
parameters. Ad position, clicks, impressions, and other keyword metrics
are aggregated for the last month for one or all of the following device
types: mobile, desktop, tablet.
operationId: post_dataforseo_keywords_bing_kw_performance_live
requestBody:
required: true
content:
application/json:
schema:
type: array
items:
type: object
properties:
keywords:
type: array
items:
type: string
description: >-
keywords required field The maximum number of keywords you
can specify: 1000 The maximum number of characters for
each keyword: 80 The maximum number of words for each
keyword phrase: 10 the specified keywords will be
converted to lowercase, data will be provided in a
separate array learn more about rules and limitations of
keyword and keywords fields in DataForSEO APIs in this
Help Center article
device:
type: string
description: >-
device type optional field specify this field if you want
to get the data for a particular device typepossible
values: desktop, mobile, tablet, all default value: all
match:
type: string
description: >-
keywords match type optional field can take the following
values: aggregate returns data across all match types;
broad returns data for all user queries containing the
specified keyword with varying word order; phrase returns
data for all user queries containing the specified keyword
with identical word order; exact returns data for user
query that matches the specified keyword;Note: the
aggregate match type is applied by default
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 and languages by making a separate request to
https://api.dataforseo.com/v3/keywords_data/bing/keyword_performance/locations_and_languages
example: "United States"
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 and languages by making a separate request to
https://api.dataforseo.com/v3/keywords_data/bing/keyword_performance/locations_and_languages
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” format the data will
be provided for the country the specified coordinates
belong to example: 52.6178549,-155.352142
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 locations and languages by making a
separate request to
https://api.dataforseo.com/v3/keywords_data/bing/keyword_performance/locations_and_languages
example: English
language_code:
type: string
description: >-
search engine language code required field if you don’t
specify language_name you can receive the list of
available locations and languages by making a separate
request to
https://api.dataforseo.com/v3/keywords_data/bing/keyword_performance/locations_and_languages
example: "en"
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
required:
- keywords
allOf:
- anyOf:
- required:
- location_name
- required:
- location_code
- required:
- location_coordinate
- anyOf:
- required:
- language_name
- required:
- language_code
responses:
'200':
description: Successful operation
content:
application/json:
schema:
type: object
properties:
version:
type: string
description: the current version of the API
status_code:
type: integer
description: >-
general status code you can find the full list of the
response codes here
status_message:
type: string
description: >-
general informational message you can find the full list
of general informational messages here
time:
type: string
description: total execution time, seconds
cost:
type: number
description: total tasks cost, USD
tasks_count:
type: integer
description: the number of tasks in the tasks array
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 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
tasks.result:
type: array
items:
type: string
description: array of results
tasks.result.keyword:
type: string
description: keyword in a POST array
tasks.result.location_code:
type: integer
description: >-
location code in a POST array if there is no data, then
the value is_nulln
tasks.result.language_code:
type: string
description: >-
language code in a POST array if there is no data, then
the value is_nulln
tasks.result.year:
type: integer
description: >-
indicates the year for which the data is provided for
example: 2020
tasks.result.month:
type: integer
description: >-
indicates the month for which the data is provided for
example: 10
tasks.result.keyword_kpi:
type: object
description: >-
object containing keyword metrics if there is no data,
then the value is_nulln
tasks.result.keyword_kpi.desktop:
type: array
items:
type: string
description: >-
keyword data aggregated for desktop devices if there is no
data, then the value is_nulln
tasks.result.keyword_kpi.desktop.ad_position:
type: string
description: >-
represents the position of the relevant ad in SERP can
take the following values: FirstPage1: The first ad to
appear on the right side of the first search results page
FirstPage2: The second ad to appear on the right side of
the first search results page FirstPage3: The third ad to
appear on the right side of the first search results page
FirstPage4: The fourth ad to appear on the right side of
the first search results page FirstPage5: The fifth ad to
appear on the right side of the first search results page
FirstPage6: The sixth ad to appear on the right side of
the first search results page FirstPage7: The seventh ad
to appear on the right side of the first search results
page FirstPage8: The eighth ad to appear on the right side
of the first search results page FirstPage9: The ninth ad
to appear on the right side of the first search results
page FirstPage10: The tenth ad to appear on the right side
of the first search results page MainLine1: The first ad
to appear at the top of the search results page MainLine2:
The second ad to appear at the top of the search results
page MainLine3: The third ad to appear at the top of the
search results page MainLine4: The fourth ad to appear at
the top of the search results page
tasks.result.keyword_kpi.desktop.clicks:
type: integer
description: >-
ad clicks the number of clicks that the keyword and match
type generated during the last month
tasks.result.keyword_kpi.desktop.impressions:
type: integer
description: >-
ad impressions the number of impressions that the keyword
and match type generated during the last month
tasks.result.keyword_kpi.desktop.average_cpc:
type: integer
description: >-
average cost per click, USD calculated by dividing the
cost of all clicks by the number of clicks
tasks.result.keyword_kpi.desktop.ctr:
type: integer
description: >-
click-through rate as a percentage calculated by dividing
the number of clicks by the number of impressions and
multiplying the result by 100
tasks.result.keyword_kpi.desktop.total_cost:
type: integer
description: >-
total cost of an ad, USD the cost of using the specified
keyword and match type during the last month
tasks.result.keyword_kpi.desktop.average_bid:
type: integer
description: average bid of the keyword
tasks.result.keyword_kpi.mobile:
type: array
items:
type: string
description: >-
keyword data aggregated for mobile devices if there is no
data, then the value is_nulln
tasks.result.keyword_kpi.mobile.ad_position:
type: string
description: >-
represents the position of the relevant ad in SERP can
take the following values: FirstPage1: The first ad to
appear on the right side of the first search results page
FirstPage2: The second ad to appear on the right side of
the first search results page FirstPage3: The third ad to
appear on the right side of the first search results page
FirstPage4: The fourth ad to appear on the right side of
the first search results page FirstPage5: The fifth ad to
appear on the right side of the first search results page
FirstPage6: The sixth ad to appear on the right side of
the first search results page FirstPage7: The seventh ad
to appear on the right side of the first search results
page FirstPage8: The eighth ad to appear on the right side
of the first search results page FirstPage9: The ninth ad
to appear on the right side of the first search results
page FirstPage10: The tenth ad to appear on the right side
of the first search results page MainLine1: The first ad
to appear at the top of the search results page MainLine2:
The second ad to appear at the top of the search results
page MainLine3: The third ad to appear at the top of the
search results page MainLine4: The fourth ad to appear at
the top of the search results page
tasks.result.keyword_kpi.mobile.clicks:
type: integer
description: >-
ad clicks the number of clicks that the keyword and match
type generated during the last month
tasks.result.keyword_kpi.mobile.impressions:
type: integer
description: >-
ad impressions the number of impressions that the keyword
and match type generated during the last month
tasks.result.keyword_kpi.mobile.average_cpc:
type: integer
description: >-
average cost per click, USD calculated by dividing the
cost of all clicks by the number of clicks
tasks.result.keyword_kpi.mobile.ctr:
type: integer
description: >-
click-through rate as a percentage calculated by dividing
the number of clicks by the number of impressions and
multiplying the result by 100
tasks.result.keyword_kpi.mobile.total_cost:
type: integer
description: >-
total cost of an ad, USD the cost of using the specified
keyword and match type during the last month
tasks.result.keyword_kpi.mobile.average_bid:
type: integer
description: average bid of the keyword
tasks.result.keyword_kpi.tablet:
type: array
items:
type: string
description: >-
keyword data aggregated for tablet devices if there is no
data, then the value is_nulln
tasks.result.keyword_kpi.tablet.ad_position:
type: string
description: >-
represents the position of the relevant ad in SERP can
take the following values: FirstPage1: The first ad to
appear on the right side of the first search results page
FirstPage2: The second ad to appear on the right side of
the first search results page FirstPage3: The third ad to
appear on the right side of the first search results page
FirstPage4: The fourth ad to appear on the right side of
the first search results page FirstPage5: The fifth ad to
appear on the right side of the first search results page
FirstPage6: The sixth ad to appear on the right side of
the first search results page FirstPage7: The seventh ad
to appear on the right side of the first search results
page FirstPage8: The eighth ad to appear on the right side
of the first search results page FirstPage9: The ninth ad
to appear on the right side of the first search results
page FirstPage10: The tenth ad to appear on the right side
of the first search results page MainLine1: The first ad
to appear at the top of the search results page MainLine2:
The second ad to appear at the top of the search results
page MainLine3: The third ad to appear at the top of the
search results page MainLine4: The fourth ad to appear at
the top of the search results page
tasks.result.keyword_kpi.tablet.clicks:
type: integer
description: >-
ad clicks the number of clicks that the keyword and match
type generated during the last month
tasks.result.keyword_kpi.tablet.impressions:
type: integer
description: >-
ad impressions the number of impressions that the keyword
and match type generated during the last month
tasks.result.keyword_kpi.tablet.average_cpc:
type: integer
description: >-
average cost per click, USD calculated by dividing the
cost of all clicks by the number of clicks
tasks.result.keyword_kpi.tablet.ctr:
type: integer
description: >-
click-through rate as a percentage calculated by dividing
the number of clicks by the number of impressions and
multiplying the result by 100
tasks.result.keyword_kpi.tablet.total_cost:
type: integer
description: >-
total cost of an ad, USD the cost of using the specified
keyword and match type during the last month
tasks.result.keyword_kpi.tablet.average_bid:
type: integer
description: average bid of the keyword
'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.