Every API here is available over the APIs.io API and to AI agents over MCP.
openapi: 3.2.0
info:
title: Microsoft Azure Client Entity Search API
description: The Entity Search API lets you send a search query to Bing and get back search results that include entities and places. Place results include restaurants, hotel, or other local businesses. For places, the query can specify the name of the local business or it can ask for a list (for example, restaurants near me). Entity results include persons, places, or things. Place in this context is tourist attractions, states, countries, etc.
version: '1.0'
servers:
- url: https://api.cognitive.microsoft.com/bing/v7.0
security:
- apiKeyHeader: []
tags:
- name: Entity Search
paths:
/entities:
get:
summary: Microsoft Azure The Entity Search Api Lets You Send A Search Query To Bing And…
operationId: microsoftAzureEntitiesSearch
tags:
- Entity Search
parameters:
- $ref: '#/components/parameters/x-bingapis-sdk'
- name: Accept
in: header
description: The default media type is application/json. To specify that the response use [JSON-LD](http://json-ld.org/), set the Accept header to application/ld+json.
required: false
schema:
type: string
- name: Accept-Language
x-ms-client-name: AcceptLanguage
in: header
description: A comma-delimited list of one or more languages to use for user interface strings. The list is in decreasing order of preference. For additional information, including expected format, see [RFC2616](http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html). This header and the setLang query parameter are mutually exclusive; do not specify both. If you set this header, you must also specify the cc query parameter. Bing will use the first supported language it finds from the list, and combine that language with the cc parameter value to determine the market to return results for. If the list does not include a supported language, Bing will find the closest language and market that supports the request, and may use an aggregated or default market for the results instead of a specified one. You should use this header and the cc query parameter only if you specify multiple languages; otherwise, you should use the mkt and setLang query parameters. A user interface string is a string that's used as a label in a user interface. There are very few user interface strings in the JSON response objects. Any links in the response objects to Bing.com properties will apply the specified language.
required: false
schema:
type: string
- name: Pragma
in: header
description: 'By default, Bing returns cached content, if available. To prevent Bing from returning cached content, set the Pragma header to no-cache (for example, Pragma: no-cache).'
required: false
schema:
type: string
- name: User-Agent
x-ms-client-name: UserAgent
in: header
description: The user agent originating the request. Bing uses the user agent to provide mobile users with an optimized experience. Although optional, you are strongly encouraged to always specify this header. The user-agent should be the same string that any commonly used browser would send. For information about user agents, see [RFC 2616](http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html).
required: false
schema:
type: string
- name: X-MSEdge-ClientID
x-ms-client-name: ClientId
in: header
description: 'Bing uses this header to provide users with consistent behavior across Bing API calls. Bing often flights new features and improvements, and it uses the client ID as a key for assigning traffic on different flights. If you do not use the same client ID for a user across multiple requests, then Bing may assign the user to multiple conflicting flights. Being assigned to multiple conflicting flights can lead to an inconsistent user experience. For example, if the second request has a different flight assignment than the first, the experience may be unexpected. Also, Bing can use the client ID to tailor web results to that client ID’s search history, providing a richer experience for the user. Bing also uses this header to help improve result rankings by analyzing the activity generated by a client ID. The relevance improvements help with better quality of results delivered by Bing APIs and in turn enables higher click-through rates for the API consumer. IMPORTANT: Although optional, you should consider this header required. Persisting the client ID across multiple requests for the same end user and device combination enables 1) the API consumer to receive a consistent user experience, and 2) higher click-through rates via better quality of results from the Bing APIs. Each user that uses your application on the device must have a unique, Bing generated client ID. If you do not include this header in the request, Bing generates an ID and returns it in the X-MSEdge-ClientID response header. The only time that you should NOT include this header in a request is the first time the user uses your app on that device. Use the client ID for each Bing API request that your app makes for this user on the device. Persist the client ID. To persist the ID in a browser app, use a persistent HTTP cookie to ensure the ID is used across all sessions. Do not use a session cookie. For other apps such as mobile apps, use the device''s persistent storage to persist the ID. The next time the user uses your app on that device, get the client ID that you persisted. Bing responses may or may not include this header. If the response includes this header, capture the client ID and use it for all subsequent Bing requests for the user on that device. If you include the X-MSEdge-ClientID, you must not include cookies in the request.'
required: false
schema:
type: string
- name: X-MSEdge-ClientIP
x-ms-client-name: ClientIp
in: header
description: The IPv4 or IPv6 address of the client device. The IP address is used to discover the user's location. Bing uses the location information to determine safe search behavior. Although optional, you are encouraged to always specify this header and the X-Search-Location header. Do not obfuscate the address (for example, by changing the last octet to 0). Obfuscating the address results in the location not being anywhere near the device's actual location, which may result in Bing serving erroneous results.
required: false
schema:
type: string
- name: X-Search-Location
x-ms-client-name: Location
in: header
description: 'A semicolon-delimited list of key/value pairs that describe the client''s geographical location. Bing uses the location information to determine safe search behavior and to return relevant local content. Specify the key/value pair as <key>:<value>. The following are the keys that you use to specify the user''s location. lat (required): The latitude of the client''s location, in degrees. The latitude must be greater than or equal to -90.0 and less than or equal to +90.0. Negative values indicate southern latitudes and positive values indicate northern latitudes. long (required): The longitude of the client''s location, in degrees. The longitude must be greater than or equal to -180.0 and less than or equal to +180.0. Negative values indicate western longitudes and positive values indicate eastern longitudes. re (required): The radius, in meters, which specifies the horizontal accuracy of the coordinates. Pass the value returned by the device''s location service. Typical values might be 22m for GPS/Wi-Fi, 380m for cell tower triangulation, and 18,000m for reverse IP lookup. ts (optional): The UTC UNIX timestamp of when the client was at the location. (The UNIX timestamp is the number of seconds since January 1, 1970.) head (optional): The client''s relative heading or direction of travel. Specify the direction of travel as degrees from 0 through 360, counting clockwise relative to true north. Specify this key only if the sp key is nonzero. sp (optional): The horizontal velocity (speed), in meters per second, that the client device is traveling. alt (optional): The altitude of the client device, in meters. are (optional): The radius, in meters, that specifies the vertical accuracy of the coordinates. Specify this key only if you specify the alt key. Although many of the keys are optional, the more information that you provide, the more accurate the location results are. Although optional, you are encouraged to always specify the user''s geographical location. Providing the location is especially important if the client''s IP address does not accurately reflect the user''s physical location (for example, if the client uses VPN). For optimal results, you should include this header and the X-MSEdge-ClientIP header, but at a minimum, you should include this header.'
required: false
schema:
type: string
- name: cc
x-ms-client-name: CountryCode
in: query
description: A 2-character country code of the country where the results come from. This API supports only the United States market. If you specify this query parameter, it must be set to us. If you set this parameter, you must also specify the Accept-Language header. Bing uses the first supported language it finds from the languages list, and combine that language with the country code that you specify to determine the market to return results for. If the languages list does not include a supported language, Bing finds the closest language and market that supports the request, or it may use an aggregated or default market for the results instead of a specified one. You should use this query parameter and the Accept-Language query parameter only if you specify multiple languages; otherwise, you should use the mkt and setLang query parameters. This parameter and the mkt query parameter are mutually exclusive—do not specify both.
required: false
schema:
type: string
- name: mkt
x-ms-client-name: Market
in: query
description: The market where the results come from. You are strongly encouraged to always specify the market, if known. Specifying the market helps Bing route the request and return an appropriate and optimal response. This parameter and the cc query parameter are mutually exclusive—do not specify both.
required: false
schema:
type: string
default: en-us
- name: q
x-ms-client-name: Query
in: query
description: The user's search term.
required: true
schema:
type: string
- name: ResponseFilter
in: query
description: A comma-delimited list of answers to include in the response. If you do not specify this parameter, the response includes all search answers for which there's relevant data.
required: false
style: form
explode: false
schema:
type: array
items:
type: string
enum:
- Entities
- Places
x-ms-enum:
name: AnswerType
modelAsString: true
- name: ResponseFormat
in: query
description: 'The media type to use for the response. The following are the possible case-insensitive values: JSON, JSONLD. The default is JSON. If you specify JSONLD, the response body includes JSON-LD objects that contain the search results.'
required: false
style: form
explode: false
schema:
type: array
items:
type: string
enum:
- Json
- JsonLd
x-ms-enum:
name: ResponseFormat
modelAsString: true
- name: SafeSearch
in: query
description: 'A filter used to filter adult content. Off: Return webpages with adult text, images, or videos. Moderate: Return webpages with adult text, but not adult images or videos. Strict: Do not return webpages with adult text, images, or videos. The default is Moderate. If the request comes from a market that Bing''s adult policy requires that safeSearch is set to Strict, Bing ignores the safeSearch value and uses Strict. If you use the site: query operator, there is the chance that the response may contain adult content regardless of what the safeSearch query parameter is set to. Use site: only if you are aware of the content on the site and your scenario supports the possibility of adult content.'
required: false
x-ms-enum:
name: SafeSearch
modelAsString: true
schema:
type: string
enum:
- 'Off'
- Moderate
- Strict
- name: SetLang
in: query
description: The language to use for user interface strings. Specify the language using the ISO 639-1 2-letter language code. For example, the language code for English is EN. The default is EN (English). Although optional, you should always specify the language. Typically, you set setLang to the same language specified by mkt unless the user wants the user interface strings displayed in a different language. This parameter and the Accept-Language header are mutually exclusive; do not specify both. A user interface string is a string that's used as a label in a user interface. There are few user interface strings in the JSON response objects. Also, any links to Bing.com properties in the response objects apply the specified language.
required: false
schema:
type: string
responses:
'200':
description: Success.
content:
application/json:
schema:
$ref: '#/components/schemas/SearchResponse'
default:
description: An error has occurred. Check the response type and/or status code for more details.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
x-ms-examples:
Successful query:
$ref: ./examples//SuccessfulQueryRequest.json
description: Needs a more full description created.
components:
schemas:
SearchResponse:
description: Defines the top-level object that the response includes when the request succeeds.
allOf:
- $ref: '#/components/schemas/Response'
type: object
properties:
queryContext:
description: An object that contains the query string that Bing used for the request. This object contains the query string as entered by the user. It may also contain an altered query string that Bing used for the query if the query string contained a spelling mistake.
$ref: '#/components/schemas/QueryContext'
readOnly: true
entities:
description: A list of entities that are relevant to the search query.
$ref: '#/components/schemas/Entities'
readOnly: true
places:
description: A list of local entities such as restaurants or hotels that are relevant to the query.
$ref: '#/components/schemas/Places'
readOnly: true
ResponseBase:
discriminator:
propertyName: _type
type: object
required:
- _type
properties:
_type:
type: string
Response:
description: Defines a response. All schemas that could be returned at the root of a response should inherit from this
allOf:
- $ref: '#/components/schemas/Identifiable'
type: object
properties:
contractualRules:
description: A list of rules that you must adhere to if you display the item.
readOnly: true
type: array
items:
$ref: '#/components/schemas/ContractualRulesContractualRule'
webSearchUrl:
description: The URL To Bing's search result for this item.
readOnly: true
type: string
Identifiable:
description: Defines the identity of a resource.
allOf:
- $ref: '#/components/schemas/ResponseBase'
type: object
properties:
id:
description: A String identifier.
readOnly: true
type: string
CreativeWork:
allOf:
- $ref: '#/components/schemas/Thing'
type: object
properties:
thumbnailUrl:
description: The URL to a thumbnail of the item.
readOnly: true
type: string
provider:
description: The source of the creative work.
readOnly: true
type: array
items:
$ref: '#/components/schemas/Thing'
text:
readOnly: true
type: string
Error:
description: Defines the error that occurred.
type: object
required:
- code
- message
properties:
code:
description: The error code that identifies the category of error.
type: string
default: None
enum:
- None
- ServerError
- InvalidRequest
- RateLimitExceeded
- InvalidAuthorization
- InsufficientAuthorization
x-ms-enum:
name: ErrorCode
modelAsString: true
subCode:
description: The error code that further helps to identify the error.
readOnly: true
type: string
enum:
- UnexpectedError
- ResourceError
- NotImplemented
- ParameterMissing
- ParameterInvalidValue
- HttpNotAllowed
- Blocked
- AuthorizationMissing
- AuthorizationRedundancy
- AuthorizationDisabled
- AuthorizationExpired
x-ms-enum:
name: ErrorSubCode
modelAsString: true
message:
description: A description of the error.
type: string
moreDetails:
description: A description that provides additional information about the error.
readOnly: true
type: string
parameter:
description: The parameter in the request that caused the error.
readOnly: true
type: string
value:
description: The parameter's value in the request that was not valid.
readOnly: true
type: string
ImageObject:
description: Defines an image
allOf:
- $ref: '#/components/schemas/MediaObject'
type: object
properties:
thumbnail:
description: The URL to a thumbnail of the image
$ref: '#/components/schemas/ImageObject'
readOnly: true
MediaObject:
allOf:
- $ref: '#/components/schemas/CreativeWork'
type: object
properties:
contentUrl:
description: Original URL to retrieve the source (file) for the media object (e.g the source URL for the image).
readOnly: true
type: string
hostPageUrl:
description: URL of the page that hosts the media object.
readOnly: true
type: string
width:
description: The width of the source media object, in pixels.
readOnly: true
type: integer
format: int32
height:
description: The height of the source media object, in pixels.
readOnly: true
type: integer
format: int32
EntitiesEntityPresentationInfo:
description: Defines additional information about an entity such as type hints.
x-ms-discriminator-value: Entities/EntityPresentationInfo
type: object
required:
- entityScenario
properties:
entityScenario:
description: The supported scenario.
type: string
default: DominantEntity
enum:
- DominantEntity
- DisambiguationItem
- ListItem
x-ms-enum:
name: EntityScenario
modelAsString: true
entityTypeHints:
description: A list of hints that indicate the entity's type. The list could contain a single hint such as Movie or a list of hints such as Place, LocalBusiness, Restaurant. Each successive hint in the array narrows the entity's type.
readOnly: true
type: array
items:
type: string
enum:
- Generic
- Person
- Place
- Media
- Organization
- LocalBusiness
- Restaurant
- Hotel
- TouristAttraction
- Travel
- City
- Country
- Attraction
- House
- State
- RadioStation
- StreetAddress
- Neighborhood
- Locality
- PostalCode
- Region
- SubRegion
- MinorRegion
- Continent
- PointOfInterest
- Other
- Movie
- Book
- TelevisionShow
- TelevisionSeason
- VideoGame
- MusicAlbum
- MusicRecording
- MusicGroup
- Composition
- TheaterPlay
- Event
- Actor
- Artist
- Attorney
- Speciality
- CollegeOrUniversity
- School
- Food
- Drug
- Animal
- SportsTeam
- Product
- Car
x-ms-enum:
name: EntityType
modelAsString: true
entityTypeDisplayHint:
description: A display version of the entity hint. For example, if entityTypeHints is Artist, this field may be set to American Singer.
readOnly: true
type: string
ContractualRulesContractualRule:
x-ms-discriminator-value: ContractualRules/ContractualRule
discriminator:
propertyName: _type
type: object
required:
- _type
properties:
targetPropertyName:
description: The name of the field that the rule applies to.
readOnly: true
type: string
_type:
type: string
Entities:
description: Defines an entity answer.
allOf:
- $ref: '#/components/schemas/SearchResultsAnswer'
type: object
required:
- value
properties:
queryScenario:
description: The supported query scenario. This field is set to DominantEntity or DisambiguationItem. The field is set to DominantEntity if Bing determines that only a single entity satisfies the request. For example, a book, movie, person, or attraction. If multiple entities could satisfy the request, the field is set to DisambiguationItem. For example, if the request uses the generic title of a movie franchise, the entity's type would likely be DisambiguationItem. But, if the request specifies a specific title from the franchise, the entity's type would likely be DominantEntity.
readOnly: true
type: string
default: DominantEntity
enum:
- DominantEntity
- DominantEntityWithDisambiguation
- Disambiguation
- List
- ListWithPivot
x-ms-enum:
name: EntityQueryScenario
modelAsString: true
value:
description: A list of entities.
type: array
items:
$ref: '#/components/schemas/Thing'
Thing:
allOf:
- $ref: '#/components/schemas/Response'
type: object
properties:
name:
description: The name of the thing represented by this object.
readOnly: true
type: string
url:
description: The URL to get more information about the thing represented by this object.
readOnly: true
type: string
image:
$ref: '#/components/schemas/ImageObject'
readOnly: true
description:
description: A short description of the item.
readOnly: true
type: string
entityPresentationInfo:
description: Additional information about the entity such as hints that you can use to determine the entity's type. To determine the entity's type, use the entityScenario and entityTypeHint fields.
$ref: '#/components/schemas/EntitiesEntityPresentationInfo'
readOnly: true
bingId:
description: An ID that uniquely identifies this item.
readOnly: true
type: string
SearchResultsAnswer:
allOf:
- $ref: '#/components/schemas/Answer'
type: object
properties:
queryContext:
$ref: '#/components/schemas/QueryContext'
readOnly: true
Answer:
allOf:
- $ref: '#/components/schemas/Response'
type: object
properties: {}
Places:
description: Defines a local entity answer.
allOf:
- $ref: '#/components/schemas/SearchResultsAnswer'
type: object
required:
- value
properties:
value:
description: A list of local entities, such as restaurants or hotels.
type: array
items:
$ref: '#/components/schemas/Thing'
ErrorResponse:
description: The top-level response that represents a failed request.
allOf:
- $ref: '#/components/schemas/Response'
type: object
required:
- errors
properties:
errors:
description: A list of errors that describe the reasons why the request failed.
type: array
items:
$ref: '#/components/schemas/Error'
QueryContext:
description: Defines the query context that Bing used for the request.
type: object
required:
- originalQuery
properties:
originalQuery:
description: The query string as specified in the request.
type: string
alteredQuery:
description: The query string used by Bing to perform the query. Bing uses the altered query string if the original query string contained spelling mistakes. For example, if the query string is "saling downwind", the altered query string will be "sailing downwind". This field is included only if the original query string contains a spelling mistake.
readOnly: true
type: string
alterationOverrideQuery:
description: The query string to use to force Bing to use the original string. For example, if the query string is "saling downwind", the override query string will be "+saling downwind". Remember to encode the query string which results in "%2Bsaling+downwind". This field is included only if the original query string contains a spelling mistake.
readOnly: true
type: string
adultIntent:
description: A Boolean value that indicates whether the specified query has adult intent. The value is true if the query has adult intent; otherwise, false.
readOnly: true
type: boolean
askUserForLocation:
description: A Boolean value that indicates whether Bing requires the user's location to provide accurate results. If you specified the user's location by using the X-MSEdge-ClientIP and X-Search-Location headers, you can ignore this field. For location aware queries, such as "today's weather" or "restaurants near me" that need the user's location to provide accurate results, this field is set to true. For location aware queries that include the location (for example, "Seattle weather"), this field is set to false. This field is also set to false for queries that are not location aware, such as "best sellers".
readOnly: true
type: boolean
parameters:
x-bingapis-sdk:
name: X-BingApis-SDK
description: Activate swagger compliance
x-ms-parameter-location: method
required: true
in: header
x-ms-enum:
name: XBingApisSDK
modelAsString: true
schema:
type: string
enum:
- 'true'
securitySchemes:
apiKeyHeader:
name: Ocp-Apim-Subscription-Key
type: apiKey
in: header
x-ms-parameterized-host:
hostTemplate: '{Endpoint}'
useSchemePrefix: false
parameters:
- $ref: ../../../Common/Parameters.json#/parameters/GlobalEndpoint