Skip to main content
cloro API monitoring endpoints share a mostly consistent request and response structure. See Making requests for an overview of both request modes.

Request structure

Common parameters

Most monitoring endpoints share these core parameters:
Google Search endpoint exceptionThe Google Search endpoint uses query instead of prompt as the required parameter, since it’s designed for search queries rather than AI prompts. See the Google Search endpoint documentation for details.
Country codes must be uppercase ("US", "GB", "DK") — lowercase values return a validation error. For the full list of supported countries per provider, see the Countries endpoint.

Response structure

All successful responses follow this base structure:

Common response fields

Response headers

Every response includes an X-Request-Id header. Store it — our support team uses it to locate your request.
For rate limit, concurrency, and credit headers, see Rate & concurrency limits.

Sources array structure

Some endpoints include additional source fields. See individual endpoint documentation for endpoint-specific source fields.

Optional response formats

Most endpoints support additional response formats through the include parameter:

HTML format

  • Parameter: include.html
  • Type: boolean
  • Default: false
  • Description: Request a URL to the full HTML of the response — an array of URLs, one per page, on Google Search and Google News. URLs expire after 24 hours, so download the HTML if you need it long-term.
  • Cost: no extra charge

Markdown format

  • Parameter: include.markdown
  • Type: boolean
  • Default: false
  • Description: Include response formatted in Markdown
  • Cost: no extra charge
Individual endpoints offer their own formats and features — see the endpoint documentation for each, and Providers for endpoint costs and credit information.

Request examples