Required Scopes
This API requires one of the following scopes:content
Query Parameters
The ID of the portal the contact search should be performed against.
The term to be used in the content search.
Specifies the type of content to search. Can be one or more of SITE_PAGE, LANDING_PAGE, BLOG_POST, LISTING_PAGE, and KNOWLEDGE_ARTICLE. Defaults to all content types except LANDING_PAGE and KNOWLEDGE_ARTICLE.
Specifies the domain(s) to be searched. Can be one or more of the portal's connected domains. Defaults to all domains.
Specifies the language of content to be searched. This parameter should obey the ISO639-1 format (e.g. es for Spanish).
Specifies which properties to search for (defaulting to all properties). Options are title, description, and html. For blog posts, additional search properties are author_full_name, author_handle, and tag.
Specifies which blog(s) to be searched by blog ID. Can be used multiple times to search more than one blog.
Specifies a specific HubDB table to search. Only returns results from the specified table. Can be used in tandem with the hubdbQuery parameter to further filter results.
Specify a HubDB query to further filter the search results. Used in tandem with the tableId parameter above.
Specifies a path prefix to filter search results. Will only return results with URL paths that start with the specified parameter. Can be used multiple times. Has a limit of 30 characters.
Inverts the behavior of the pathPrefix filter when set to 'false'. (Defaults to true)
Specifies the length of the search results. Can be set to LONG or SHORT. Setting this parameter to SHORT will return a short highlight of the meta description. Setting this parameter to LONG will build the snippet based on the html/content of the page.
LONG
, SHORT
Specifies whether or not to enable tracking links. Defaults to false. When set to true, the content's URL will be replaced with a tracking link.
Specifies whether or not you are showing autocomplete results. Defaults to false. If you're not showing autocomplete results, this parameter should be excluded.
Specifies how strongly a result is boosted based on its view count. Defaults to 1.0.
Specifies the maximum amount a result will be boosted based on its view count. Defaults to 5.0.
Specifies a relative time window where scores of documents published outside this time window decay. This can only be used for blog posts. For example, boostRecent=10d will boost documents published within the last 10 days. Supported timeunits are ms (milliseconds), s (seconds), m (minutes), h (hours), d (days).
Used to page through the results. If there are more results than specified by the limit= parameter, you will need to use the offset returned in the first request to get the next set of results.
Specifies the number of results to be returned in a single response. Defaults to 10, maximum limit is 100.
x <= 100
Response
successful operation
The response is of type object
.