> ## Documentation Index > Fetch the complete documentation index at: https://www.conductor.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Conductor Monitoring Reporting API > Extract data and metrics from your Conductor Monitoring account with the Reporting API. ## Getting Started ### Overview Our Reporting API is used for extracting data and metrics from your Conductor Monitoring account. Typical use-cases include connecting several software solutions together to streamline your reporting tasks and integrating Conductor Monitoring in your client portal. ### Important This support article is covering the current 2.0 version of Conductor Monitoring's Reporting API. We recommend using the Reporting API v2.0 for your reporting tasks and integrations as all new endpoints will be only supported on this version. The legacy Conductor Monitoring Reporting API version is still available. You can find the relevant support documentation and our migration guide in the [Conductor Monitoring Reporting API V1.0](/docs/other-apis/conductor-monitoring-reporting-api-v10-legacy/) article. Please note that while the legacy Reporting API v1.0 remains available at the moment, it will likely be deprecated in the future. Therefore we highly recommend using (and migrating to) the Reporting API v2.0. Note! Conductor provides APIs for several different uses across its Conductor Monitoring and Conductor Intelligence products. This article describes Conductor Monitoring's Reporting API. If you are looking for information about a different API offering, consider the following articles: * [Conductor's Data API](/docs/api/introduction/) * [Conductor Intelligence's User Management API](/docs/other-apis/user-management/conductors-user-management-api/) * [Conductor Monitoring's CMS API](/docs/other-apis/cms-api/) * [Conductor Monitoring's Data Enrichment API](/docs/other-apis/data-enrichment-api/) ### Reporting API Terms of Use By using the Reporting API you agree to the [Terms of Use](https://www.contentkingapp.com/legal/terms-of-use/). ### Authentication #### Get your API integration token To use Conductor Monitoring's Reporting API you need to get your account's Reporting API token. You'll find it in the **Integration Tokens** section under the **Account** tab in the main **Account** section.

#### Configure your request headers To authenticate your requests, you need to include the following request headers: ``` Authorization: token {place-your-API-token-here} Content-Type: application/json ``` ### Note! The value for the **Authorization** header must be the string "token" followed by a space and then your actual API token. ### Rate limits The Reporting API uses rate limits to ensure API request traffic can be handled efficiently. Rate limits define the maximum number of requests which can be made in a given time range. Conductor Monitoring’s Reporting API has the following rate limits: * 6 requests/second/requester IP address * When the limit is hit the API returns a `429` status code for 1 minute Note that there is no maximum number of calls you can make to this API. ## Using the Conductor Monitoring Reporting API ### Base URL Conductor Monitoring Reporting API is available on the following URL: ``` https://api.cm.conductor.com/ ``` ### Retrieving a list of websites in your account #### /v2/entities/websites #### Request Body None #### Responses

200	Successful query execution Schema: See below Example \{ "data": \[ \{ "id": "1-234", "app\_url": "[https://app.cm.conductor.com/websites/1-234/dashboard](https://app.cm.conductor.com/websites/1-234/dashboard)", "domain": "[https://www.conductor.com](https://www.conductor.com)", "name": "null", "page\_capacity": 1000 }, \{ "id": "1-2345", "app\_url": "[https://app.cm.conductor.com/websites/1-2345/dashboard](https://app.cm.conductor.com/websites/1-2345/dashboard)", "domain": "[https://www.conductor.de](https://www.conductor.de)", "name": "Conductor Monitoring - DE", "page\_capacity": 1000 }, ] }
401	Unauthorized: Missing authentication token. The request was received but it's lacking an authorization token and can therefore not be processed. Make sure to correctly set the Authorization header. Authentication failed. The request could not be processed because the supplied API token is invalid or expired. Examples `\{ "code": "auth\_missing\_token", "message": "Authentication token must be passed in Authorization HTTP header.", "errors": \[] } or \{ "code": "auth\_failed", "message": "Authentication token is expired or invalid.", "errors": \[] }`
403	Forbidden: Terms of use not accepted. You have not accepted Reporting API Terms of Use yet. You need to accept them in Account Settings before you start using Conductor Monitoring Reporting API. Our CDN is blocking your user agent, which might be a generic or default user agent like Python urllib3. Changing the user agent to something less generic or more closely resembling a browser often bypasses these restrictions. Example `\{ "code": "terms\_of\_use\_not\_accepted", "message": "Reporting API Terms of Use have not been accepted yet. Please accept Terms of Use in Account Settings.", "errors": \[] }`
404	Not found Example `\{ "error": "Requested website ID was not found" }`
422	Unprocessable Entity. The request was received, but the authorization wasn't formatted correctly. Make sure to correctly configure the Authorization header as described in the Authentication section above.

#### Schema data types for this endpoint

Property	Data Type
`id`	string
`app\_url`	string (absolute URL)
`domain`	string (absolute URL)
`name`	string
`page\_capacity`	integer

### Retrieving a list of segments for a website #### /v2/entities/segments?website\_id=\{website\_id} Send this request—using a website ID—to get a list of segments for a specific website in your account. #### Request Path Parameters `website_id` (Required). Can be inferred from the `GET /v2/entities/websites` endpoint described above. #### Request Response

200	Successful query execution Schema: See below Example \{ "data": \[ \{ "id": "1", "color": "bf86d5", "label": "Important pages", "shortcode": null }, \{ "id": "2", "color": "72c035", "label": "Indexable", "shortcode": null }, ] }
401	Unauthorized: Missing authentication token. The request was received but it's lacking an authorization token and can therefore not be processed. Make sure to correctly set the Authorization header. Authentication failed. The request could not be processed because the supplied API token is invalid or expired. Examples `\{ "code": "auth\_missing\_token", "message": "Authentication token must be passed in Authorization HTTP header.", "errors": \[] } or \{ "code": "auth\_failed", "message": "Authentication token is expired or invalid.", "errors": \[] }`
403	Forbidden: Terms of use not accepted. You have not accepted Reporting API Terms of Use yet. You need to accept them in Account Settings before you start using Conductor Monitoring Reporting API. Our CDN is blocking your user agent, which might be a generic or default user agent like Python urllib3. Changing the user agent to something less generic or more closely resembling a browser often bypasses these restrictions. Example `\{ "code": "terms\_of\_use\_not\_accepted", "message": "Reporting API Terms of Use have not been accepted yet. Please accept Terms of Use in Account Settings.", "errors": \[] }`
404	Not found Example `\{ "error": "Requested website ID was not found" }`
422	Unprocessable Entity. The request was received, but the authorization wasn't formatted correctly. Make sure to correctly configure the Authorization header as described in the Authentication section above.

#### Schema data types for this endpoint

Property	Data Type
`id`	string
`color`	string
`label`	string
`shortcode`	string

### Retrieving statistics for a website or website's segment #### /v2/data/statistics?website\_id=\{website\_id} Use this endpoint to pull data for one of your tracked websites or for a part of a tracked website. #### Request Path Parameters `website_id` (Required). Can be inferred from the `GET /v2/entities/websites` endpoint described above. #### Query Parameters `scope` (Required). Determines whether data for the whole website is returned or specific parts. Potential values: * `website`. Retrieves data for the whole website. * `segment:{segment_id}`. Retrieves data for a specific segment. Segment IDs can be inferred with the `GET /v2/entities/segments` endpoint described above. * `segment_label:{segment_label}`. Retrieves data for a specific segment. Segment label can be inferred from the `GET /v2/entities/segments` endpoint described above. #### Request Responses

200	Successful query execution Schema: See below Example \{ "data": \{ "health": 916, "number\_of\_issues": 1234, "number\_of\_urls": \{ "missing": 0, "page": 123, "redirect": 0, "server\_error": 0, "unreachable": 0 }, "number\_of\_urls\_per\_property": \{ "h1": \{ "available": 123, "empty": 0, "missing": 0 }, "health": \{ "0-100": 0, "100-200": 0, "200-300": 0, "300-400": 0, "400-500": 0, "500-600": 0, "600-700": 0, "700-800": 0, "800-900": 0, "900-1000": 1234 }, "hreflang\_language": \{ "en": 1234, "missing": 0, "others": 0 }, "is\_disallowed\_in\_robots\_txt": \{ "true": 0, "false": 1234 }, "is\_in\_sitemap": \{ "true": 1234, "false": 0 }, "is\_indexable": \{ "true": 1234, "false": 0 }, "is\_indexable\_due\_to\_meta\_robots": \{ "no": 0, "not\_applicable": 0, "yes": 1234 }, "is\_indexable\_due\_to\_x\_robots\_tag": \{ "no": 0, "not\_applicable": 0, "yes": 1234 }, "is\_linked": \{ "true": 1234, "false": 0 }, "meta\_description": \{ "available": 1234, "empty": 0, "missing": 0 }, "open\_graph\_description": \{ "available": 1234, "empty": 0, "missing": 0 }, "open\_graph\_image": \{ "available": 1234, "empty": 0, "missing": 0 }, "open\_graph\_title": \{ "available": 1234, "empty": 0, "missing": 0 }, "open\_graph\_type": \{ "empty": 0, "missing": 0, "others": 0, "values": \{ "article": 1230, "website": 2, "object": 2 } }, "open\_graph\_url": \{ "available": 1234, "empty": 0, "missing": 0 }, "importance": \{ "0-1": 0, "1-2": 0, "2-3": 0, "3-4": 109, "4-5": 109, "5-6": 103, "6-7": 43, "7-8": 28, "8-9": 16, "9-10": 800 }, "status\_code": \{ "200": 1234 }, "title": \{ "available": 1234, "empty": 0, "missing": 0 }, "twitter\_card": \{ "empty": 0, "missing": 0, "others": 0, "values": \{ "summary\_large\_image": 1234 } }, "twitter\_description": \{ "available": 1234, "empty": 0, "missing": 0 }, "twitter\_image": \{ "available": 1234, "empty": 0, "missing": 0 }, "twitter\_site": \{ "empty": 0, "missing": 0, "others": 0, "values": \{ "@conductor": 1234 } }, "twitter\_title": \{ "available": 1234, "empty": 0, "missing": 0 }, "is\_https": \{ "true": 1234, "false": 0 }, "url\_depth": \{ "0": 1, "1": 15, "2": 399, "3": 29, "4": 1000, "5": 0, "6": 0, "7": 0, "8": 0, "9": 0, "10+": 0 }, "domain": \{ "[www.conductor.de](http://www.conductor.de)": 1234 }, "lighthouse\_cls": \{ "good": 1234, "needsImprovement": 0, "bad": 0 }, "lighthouse\_fcp": \{ "good": 1234, "needsImprovement": 0, "bad": 0 }, "lighthouse\_lcp": \{ "good": 1234, "needsImprovement": 0, "bad": 0 }, "lighthouse\_performance": \{ "good": 1234, "needsImprovement": 0, "bad": 0 }, "lighthouse\_si": \{ "good": 1234, "needsImprovement": 0, "bad": 0 }, "lighthouse\_tbt": \{ "good": 1234, "needsImprovement": 0, "bad": 0 }, "lighthouse\_tti": \{ "good": 1234, "needsImprovement": 0, "bad": 0 } } }, "data\_captured\_at": "2022-08-04T15:23:01+02:00", "is\_data\_golden": false }
401	Unauthorized: Missing authentication token. The request was received but it's lacking an authorization token and can therefore not be processed. Make sure to correctly set the Authorization header. Authentication failed. The request could not be processed because the supplied API token is invalid or expired. Examples `\{ "code": "auth\_missing\_token", "message": "Authentication token must be passed in Authorization HTTP header.", "errors": \[] } or \{ "code": "auth\_failed", "message": "Authentication token is expired or invalid.", "errors": \[] }`
403	Forbidden: Terms of use not accepted. You have not accepted Reporting API Terms of Use yet. You need to accept them in Account Settings before you start using Conductor Monitoring Reporting API. Our CDN is blocking your user agent, which might be a generic or default user agent like Python urllib3. Changing the user agent to something less generic or more closely resembling a browser often bypasses these restrictions. Example `\{ "code": "terms\_of\_use\_not\_accepted", "message": "Reporting API Terms of Use have not been accepted yet. Please accept Terms of Use in Account Settings.", "errors": \[] }`
404	Not found Example `\{ "error": "Requested website ID was not found" }`
422	Unprocessable Entity. The request was received, but the authorization wasn't formatted correctly. Make sure to correctly configure the Authorization header as described in the Authentication section above.

#### Schema data types for this endpoint

Property	Data Type
`health`	integer
`number\_of\_issues`	integer
`number\_of\_urls`	array
`number\_of\_urls.page`	integer
`number\_of\_urls.missing`	integer
`number\_of\_urls.redirect`	integer
`number\_of\_urls.server\_error`	integer
`number\_of\_urls.unreachable`	integer
`number\_of\_urls\_per\_property`	array
`h1`	array
`h1.available`	integer
`h1.empty`	integer
`h1.missing`	integer
`health`	array
`health.0-100`	integer
`health.100-200`	integer
`health.200-300`	integer
`health.300-400`	integer
`health.400-500`	integer
`health.600-700`	integer
`health.800-900`	integer
`health.900-1000`	integer
`hreflang\_language`	array
`hreflang\_language.hreflang\_attribute`	string
`hreflang\_language.missing`	integer
`hreflang\_language.other`	integer
`is\_disallowed\_in\_robots\_txt`	array
`is\_disallowed\_in\_robots\_txt.true`	integer
`is\_disallowed\_in\_robots\_txt.false`	integer
`is\_in\_sitemap`	array
`is\_in\_sitemap.true`	integer
`is\_in\_sitemap.false`	integer
`is\_indexable`	array
`is\_indexable.true`	integer
`is\_indexable.false`	integer
`is\_indexable\_due\_to\_meta\_robots`	array
`is\_indexable\_due\_to\_meta\_robots.no`	integer
`is\_indexable\_due\_to\_meta\_robots.not\_applicable`	integer
`is\_indexable\_due\_to\_meta\_robots.yes`	integer
`is\_indexable\_due\_to\_x\_robots\_tag`	array
`is\_indexable\_due\_to\_x\_robots\_tag.no`	integer
`is\_linked`	array
`is\_linked.true`	integer
`is\_linked.false`	integer
`meta\_description`	array
`meta\_description.available`	integer
`meta\_description.empty`	integer
`meta\_description.missing`	integer
`open\_graph\_description`	array
`open\_graph\_description.available`	integer
`open\_graph\_description.empty`	integer
`open\_graph\_description.missing`	integer
`open\_graph\_image`	array
`open\_graph\_image.available`	integer
`open\_graph\_image.empty`	integer
`open\_graph\_image.missing`	integer
`open\_graph\_title`	array
`open\_graph\_title.available`	integer
`open\_graph\_title.empty`	integer
`open\_graph\_title.missing`	integer
`open\_graph\_type`	array
`open\_graph\_type.empty`	integer
`open\_graph\_type.missing`	integer
`open\_graph\_type.others`	integer
`open\_graph\_type.values`	array
`open\_graph\_type.values.name`	integer
`open\_graph\_URL`	array
`open\_graph\_URL.available`	integer
`open\_graph\_URL.empty`	integer
`open\_graph\_URL.missing`	integer
`importance`	array
`importance.0-1`	integer
`importance.1-2`	integer
`importance.2-3`	integer
`importance.3-4`	integer
`importance.4-5`	integer
`importance.6-7`	integer
`importance.8-9`	integer
`importance.9-10`	integer
`status\_code`	array
`status\_code.value`	integer
`title`	array
`title.available`	integer
`title.empty`	integer
`title.missing`	integer
`twitter\_card`	array
`twitter\_card.empty`	integer
`twitter\_card.missing`	integer
`twitter\_card.others`	integer
`twitter\_card.values`	array
`twitter\_card.values\_name`	integer
`twitter\_description`	array
`twitter\_description.available`	integer
`twitter\_description.empty`	integer
`twitter\_description.missing`	integer
`twitter\_image`	array
`twitter\_image.available`	integer
`twitter\_image.empty`	integer
`twitter\_image.missing`	integer
`twitter\_site`	array
`twitter\_site.empty`	integer
`twitter\_site.missing`	integer
`twitter\_site.others`	integer
`twitter\_site.values`	array
`twitter\_site.values.name`	integer
`twitter\_title`	array
`twitter\_title.available`	integer
`twitter\_title.empty`	integer
`twitter\_title.missing`	integer
`is\_https`	array
`is\_https.true`	boolean
`is\_https.false`	boolean
`url\_depth`	array
`url\_depth.0`	integer
`url\_depth.1`	integer
`url\_depth.2`	integer
`url\_depth.3`	integer
`url\_depth.4`	integer
`url\_depth.6`	integer
`url\_depth.7`	integer
`url\_depth.8`	integer
`url\_depth.9`	integer
`url\_depth.10+`	integer
`domain`	array
`domain\_name`	string
`data\_captured\_at`	datetime (ISO-8601 format)
`is\_data\_golden`	boolean

#### Specific errors when requesting statistics ``` 404 Not found { "error": "No statistics found for given scope" } ``` This response means that the statistics for the given scope (website or segment) are not available at this time. They may or may not become available at a later time, depending on the actual content of the scope. ### Retrieving list of pages for a website #### /v2/data/pages Use this endpoint to pull a list of pages belonging to one of your tracked websites or for a part of a tracked website. #### Query Parameters `website_id` (Required). Can be inferred from the `GET /v2/entities/websites` endpoint described above. *** `per_page` (Required). Can be used with `page` and `page_cursor` for pagination. Value can be in range from `1` to `1000`. *** `page` (Optional) Can be used with `per_page` and `page_cursor` for pagination. Value can be `1` up to `ceil`(total / `per_page`). If `page` is higher than the maximum value, the `urls` array will be empty. *** `page_cursor` (Optional). Can be used with `page` and `per_page` for pagination. Value should be a string retrieved from the `next_page_cursor` object in the request response for the previous page. *** `sort` and `direction` (Optional). Can be used to determine sort order. * `sort` should be set to `url` * `direction` can be either `asc` or `desc` ### Important Make sure to use the `page_cursor` parameter when retrieving large paginated datasets to ensure smooth performance of the API. The `page_cursor` parameter allows you to specify the exact point in the dataset where the previous page (response) ended and the next page should start, optimizing the process of retrieving large paginated datasets. The `page_cursor` parameter takes precedence over the page parameter. This means that if the `page_cursor` parameter is used in the request URL, the page parameter should not be used at the same time. #### Request Responses

200	Successful query execution. Each successful response contains 2 main keys: `total` count of URLs in result set for given query `urls` paginated URLs based on query parameters `per\_page`, `page`, and `page\_cursor` Schema: See below Example \{ "data": \{ "next\_page\_cursor": "WyIvencvY3NoZWxwL2FydGljbGUv2YPZit", "total": 1, "urls": \[ \{ "aa\_average\_time\_spent\_on\_site": null, "aa\_bounce\_rate": null, "aa\_page\_views": null, "aa\_revenue": null, "aa\_unique\_visitors": null, "analytics\_services": \[ "google\_analytics" ], "app\_url": "[https://app.cm.conductor.com/websites/1-2345/pages/123456](https://app.cm.conductor.com/websites/1-2345/pages/123456)", "canonical": null, "canonical\_type": "none", "custom\_elements": \[], "ga\_average\_time": null, "ga\_bounce\_rate": null, "ga\_page\_value": null, "ga\_page\_views": null, "ga\_unique\_page\_views": null, "ga\_v4\_active\_users": null, "ga\_v4\_average\_engagement\_time": null, "ga\_v4\_engagement\_rate": null, "ga\_v4\_screen\_page\_views": null, "gsc\_clicks": null, "gsc\_ctr": null, "gsc\_impressions": null, "gsc\_position": null, "h1": "null", "health": 920, "hreflang\_language": null, "is\_disallowed\_in\_robots\_txt": false, "is\_https": false, "is\_in\_sitemap": false, "is\_indexable": false, "is\_indexable\_due\_to\_meta\_robots": false, "is\_indexable\_due\_to\_x\_robots\_tag": true, "is\_linked": true, "lfa\_bing\_desktop\_frequency": null, "lfa\_bing\_desktop\_last\_visit": null, "lfa\_bing\_frequency": null, "lfa\_bing\_last\_visit": null, "lfa\_bing\_mobile\_frequency": null, "lfa\_bing\_mobile\_last\_visit": null, "lfa\_google\_desktop\_frequency": null, "lfa\_google\_desktop\_last\_visit": null, "lfa\_google\_frequency": null, "lfa\_google\_last\_visit": null, "lfa\_google\_mobile\_frequency": null, "lfa\_google\_mobile\_last\_visit": null, "lfa\_openai\_bot\_frequency": null, "lfa\_openai\_bot\_last\_visit": null, "lfa\_openai\_desktop\_frequency": null, "lfa\_openai\_desktop\_last\_visit": null, "lfa\_openai\_frequency": null, "lfa\_openai\_last\_visit": null, "lfa\_openai\_search\_frequency": null, "lfa\_openai\_search\_last\_visit": null, "lfa\_openai\_user\_frequency": null, "lfa\_openai\_user\_last\_visit": null, "lfa\_perplexity\_bot\_frequency": null, "lfa\_perplexity\_bot\_last\_visit": null, "lfa\_perplexity\_desktop\_frequency": null, "lfa\_perplexity\_desktop\_last\_visit": null, "lfa\_perplexity\_frequency": null, "lfa\_perplexity\_last\_visit": null, "lfa\_perplexity\_user\_frequency": null, "lfa\_perplexity\_user\_last\_visit": null, "lighthouse\_cls": null, "lighthouse\_fcp": null, "lighthouse\_lcp": null, "lighthouse\_performance": null, "lighthouse\_si": null, "lighthouse\_tbt": null, "lighthouse\_tti": null, "link\_amp": null, "link\_next": null, "link\_prev": null, "meta\_description": "null", "mobile\_variant": null, "number\_of\_hreflangs": 0, "number\_of\_incoming\_internal\_canonicals": 0, "number\_of\_incoming\_internal\_links": 0, "number\_of\_incoming\_internal\_redirects": 0, "number\_of\_outgoing\_external\_links": 5, "number\_of\_outgoing\_internal\_links": 147, "open\_graph\_description": null, "open\_graph\_image": null, "open\_graph\_title": null, "open\_graph\_type": null, "open\_graph\_url": null, "redirect": null, "relevance": 3, "schema\_org\_number\_of\_types": 0, "schema\_org\_types": \[], "segments": \[], "status\_code": 200, "tag\_managers": null, "time\_document\_download": 12, "title": "null", "twitter\_card": null, "twitter\_description": null, "twitter\_image": null, "twitter\_site": null, "twitter\_title": null, "type": "page", "url": "[https://www.conductor.com/](https://www.conductor.com/)", "url\_depth": 0, "url\_path": "/", "visual\_analytics\_services": null } ] }, "data\_captured\_at": "2022-08-16T11:24:27+02:00", "is\_data\_golden": false }
401	Unauthorized: Missing authentication token. The request was received but it's lacking an authorization token and can therefore not be processed. Make sure to correctly set the Authorization header. Authentication failed. The request could not be processed because the supplied API token is invalid or expired. Examples `\{ "code": "auth\_missing\_token", "message": "Authentication token must be passed in Authorization HTTP header.", "errors": \[] } or \{ "code": "auth\_failed", "message": "Authentication token is expired or invalid.", "errors": \[] }`
403	Forbidden: Terms of use not accepted. You have not accepted Reporting API Terms of Use yet. You need to accept them in Account Settings before you start using Conductor Monitoring Reporting API. Our CDN is blocking your user agent, which might be a generic or default user agent like Python urllib3. Changing the user agent to something less generic or more closely resembling a browser often bypasses these restrictions. Example `\{ "code": "terms\_of\_use\_not\_accepted", "message": "Reporting API Terms of Use have not been accepted yet. Please accept Terms of Use in Account Settings.", "errors": \[] }`
404	Not found Example `\{ "error": "Requested website ID was not found" }`
422	Unprocessable Entity. The request was received, but the authorization wasn't formatted correctly. Make sure to correctly configure the Authorization header as described in the Authentication section above.

#### Schema data types for this endpoint

Property	Data Type
`next\_page\_cursor`	string
`urls`	array
`urls.aa\_average\_time\_spent\_on\_site`	integer (seconds)
`urls.aa\_bounce\_rate`	float (percentage)
`urls.aa\_page\_views`	integer
`urls.aa\_unique\_visitors`	integer
`urls.aa\_revenue`	float
`urls.analytics\_services`	string
`urls.app\_url`	string
`urls.canonical`	string
`urls.canonical\_type`	string
`urls.custom\_elements`	array
`urls.custom\_elements.custom\_element\_name`	string/number/boolean/date (depending on configuration)
`urls.ga\_average\_time`	integer (seconds)
`urls.ga\_bounce\_rate`	float (percentage)
`urls.ga\_page\_views`	integer
`urls.ga\_unique\_page\_views`	integer
`urls.ga\_page\_value`	float
`urls.ga\_v4\_active\_users`	integer
`urls.ga\_v4\_average\_engagement\_time`	integer (seconds)
`urls.ga\_v4\_engagement\_rate`	float (percentage)
`urls.ga\_v4\_screen\_page\_views`	integer
`urls.gsc\_clicks`	integer
`urls.gsc\_impressions`	integer
`urls.gsc\_ctr`	float (percentage)
`urls.gsc\_position`	float
`urls.gsc\_date\_range`	array
`urls.gsc\_date\_range.since`	date (YYYY-MM-DD)
`urls.gsc\_date\_range.until`	date (YYYY-MM-DD)
`urls.health`	number
`urls.hreflang\_language`	string
`urls.is\_disallowed\_in\_robots\_txt`	boolean
`urls.is\_https`	boolean
`urls.is\_in\_sitemap`	boolean
`urls.is\_indexable`	boolean
`urls.is\_indexable\_due\_to\_meta\_robots`	boolean
`urls.is\_indexable\_due\_to\_x\_robots\_tag`	boolean
`urls.is\_linked`	boolean
`urls.legacy\_id\_fallback`	string
`urls.lfa\_bing\_desktop\_frequency`	array
`urls.lfa\_bing\_desktop\_frequency.value`	float
`urls.lfa\_bing\_desktop\_frequency.unit`	string
`urls.lfa\_bing\_desktop\_last\_visit`	datetime (ISO-8601 format)
`urls.lfa\_bing\_frequency`	array
`urls.lfa\_bing\_frequency.value`	float
`urls.lfa\_bing\_frequency.unit`	string
`urls.lfa\_bing\_last\_visit`	datetime (ISO-8601 format)
`urls.lfa\_bing\_mobile\_frequency`	array
`urls.lfa\_bing\_mobile\_frequency.value`	float
`urls.lfa\_bing\_mobile\_frequency.unit`	string
`urls.lfa\_bing\_mobile\_last\_visit`	datetime (ISO-8601 format)
`urls.lfa\_google\_desktop\_frequency`	array
`urls.lfa\_google\_desktop\_frequency.value`	float
`urls.lfa\_google\_desktop\_frequency.unit`	string
`urls.lfa\_google\_desktop\_last\_visit`	datetime (ISO-8601 format)
`urls.lfa\_google\_frequency`	array
`urls.lfa\_google\_frequency.value`	float
`urls.lfa\_google\_frequency.unit`	string
`urls.lfa\_google\_last\_visit`	datetime (ISO-8601 format)
`urls.lfa\_google\_mobile\_frequency`	array
`urls.lfa\_google\_mobile\_frequency.value`	float
`urls.lfa\_google\_mobile\_frequency.unit`	string
`urls.lfa\_google\_mobile\_last\_visit`	datetime (ISO-8601 format)
`urls.lfa\_openai\_bot\_frequency`	array
`urls.lfa\_openai\_bot\_frequency.value`	float
`urls.lfa\_openai\_bot\_frequency.unit`	string
`urls.lfa\_openai\_bot\_last\_visit`	datetime (ISO-8601 format)
`urls.lfa\_openai\_desktop\_frequency`	array
`urls.lfa\_openai\_desktop\_frequency.value`	float
`urls.lfa\_openai\_desktop\_frequency.unit`	string
`urls.lfa\_openai\_desktop\_last\_visit`	datetime (ISO-8601 format)
`urls.lfa\_openai\_frequency`	array
`urls.lfa\_openai\_frequency.value`	float
`urls.lfa\_openai\_frequency.unit`	string
`urls.lfa\_openai\_last\_visit`	datetime (ISO-8601 format)
`urls.lfa\_openai\_search\_frequency`	array
`urls.lfa\_openai\_search\_frequency.value`	float
`urls.lfa\_openai\_search\_frequency.unit`	string
`urls.lfa\_openai\_search\_last\_visit`	datetime (ISO-8601 format)
`urls.lfa\_openai\_user\_frequency`	array
`urls.lfa\_openai\_user\_frequency.value`	float
`urls.lfa\_openai\_user\_frequency.unit`	string
`urls.lfa\_openai\_user\_last\_visit`	datetime (ISO-8601 format)
`urls.lfa\_perplexity\_bot\_frequency`	array
`urls.lfa\_perplexity\_bot\_frequency.value`	float
`urls.lfa\_perplexity\_bot\_frequency.unit`	string
`urls.lfa\_perplexity\_bot\_last\_visit`	datetime (ISO-8601 format)
`urls.lfa\_perplexity\_desktop\_frequency`	array
`urls.lfa\_perplexity\_desktop\_frequency.value`	float
`urls.lfa\_perplexity\_desktop\_frequency.unit`	string
`urls.lfa\_perplexity\_desktop\_last\_visit`	datetime (ISO-8601 format)
`urls.lfa\_perplexity\_frequency`	array
`urls.lfa\_perplexity\_frequency.value`	float
`urls.lfa\_perplexity\_frequency.unit`	string
`urls.lfa\_perplexity\_last\_visit`	datetime (ISO-8601 format)
`urls.lfa\_perplexity\_user\_frequency`	array
`urls.lfa\_perplexity\_user\_frequency.value`	float
`urls.lfa\_perplexity\_user\_frequency.unit`	string
`urls.lfa\_perplexity\_user\_last\_visit`	datetime (ISO-8601 format)
`urls.lighthouse\_performance`	array
`urls.lighthouse\_performance.value`	integer
`urls.lighthouse\_performance.range`	string
`urls.lighthouse\_cls`	array
`urls.lighthouse\_cls.value`	float
`urls.lighthouse\_cls.range`	string
`urls.lighthouse\_fcp`	array
`urls.lighthouse\_fcp.value`	integer (milliseconds)
`urls.lighthouse\_fcp.range`	string
`urls.lighthouse\_lcp`	array
`urls.lighthouse\_lcp.value`	integer (milliseconds)
`urls.lighthouse\_lcp.range`	string
`urls.lighthouse\_si`	array
`urls.lighthouse\_si.value`	integer (milliseconds)
`urls.lighthouse\_si.range`	string
`urls.lighthouse\_tbt`	array
`urls.lighthouse\_tbt.value`	integer (milliseconds)
`urls.lighthouse\_tbt.range`	string
`urls.lighthouse\_tti`	array
`urls.lighthouse\_tti.value`	integer (milliseconds)
`urls.lighthouse\_tti.range`	string
`urls.link\_amp`	string (absolute URL)
`urls.link\_next`	string (absolute URL)
`urls.link\_prev`	string (absolute URL)
`urls.mobile\_variant`	string (absolute URL)
`urls.title`	string
`urls.url\_id`	string
`urls.is\_video`	boolean
`urls.video\_duration`	float (seconds)
`urls.video\_title`	string
`urls.webp`	string (absolute URL)
`urls.watched\_events`	array
`urls.watched\_events.watched\_event\_name`	string
`data\_captured\_at`	datetime (ISO-8601 format)
`is\_data\_golden`	boolean

### Retrieving data for a specific page within a website #### /v2/data/page Use this endpoint to get data for a specific page belonging to a website in your account. #### Query Parameters `website_id` (Required). Can be inferred from the `GET /v2/entities/websites` endpoint described above. *** `url` (Required). Can be inferred from the value of the `url` object for a specific page returned in the `urls` array called by the `GET /v2/data/pages` endpoint described above #### Response for a page

200	Successful query execution Schema: See below Examples Successful response for a page with a 2xx HTTP response code (Successful) \{ "data": \{ "url": "[https://www.conductor.com](https://www.conductor.com)", "url\_unique\_id": "1-234", "is\_https": true, "ga\_v4\_active\_users": 10, "ga\_v4\_average\_engagement\_time": 10, "ga\_v4\_date\_range": \{ "since": "2022-05-16", "until": "2022-08-14" }, "ga\_v4\_engagement\_rate": 10, "ga\_v4\_screen\_page\_views": 10, "gsc\_clicks": 10, "gsc\_ctr": 10, "gsc\_date\_range": \{ "since": "2022-05-16", "until": "2022-08-14" }, "gsc\_impressions": 10, "gsc\_position": 10, "health": 881, "is\_disallowed\_in\_robots\_txt": false, "is\_indexable": true, "is\_indexable\_due\_to\_meta\_robots": "yes", "is\_indexable\_due\_to\_x\_robots\_tag": "yes", "is\_in\_sitemap": true, "lfa\_bing\_desktop\_frequency": null, "lfa\_bing\_desktop\_last\_visit": null, "lfa\_bing\_frequency": null, "lfa\_bing\_last\_visit": null, "lfa\_bing\_mobile\_frequency": null, "lfa\_bing\_mobile\_last\_visit": null, "lfa\_google\_desktop\_frequency": null, "lfa\_google\_desktop\_last\_visit": null, "lfa\_google\_frequency": null, "lfa\_google\_last\_visit": null, "lfa\_google\_mobile\_frequency": null, "lfa\_google\_mobile\_last\_visit": null, "lfa\_openai\_desktop\_frequency": null, "lfa\_openai\_desktop\_last\_visit": null, "lfa\_openai\_search\_last\_visit": null, "lfa\_openai\_search\_frequency": null, "lfa\_openai\_user\_last\_visit": null, "lfa\_openai\_user\_frequency": null, "lfa\_openai\_bot\_last\_visit": null, "lfa\_openai\_bot\_frequency": null, "lfa\_openai\_frequency": null, "lfa\_openai\_last\_visit": null, "lfa\_perplexity\_desktop\_frequency": null, "lfa\_perplexity\_desktop\_last\_visit": null, "lfa\_perplexity\_user\_last\_visit": null, "lfa\_perplexity\_user\_frequency": null, "lfa\_perplexity\_bot\_last\_visit": null, "lfa\_perplexity\_bot\_frequency": null, "lfa\_perplexity\_frequency": null, "lfa\_perplexity\_last\_visit": null, "lighthouse\_cls": \{ "value": 0, "range": "good" }, "lighthouse\_fcp": \{ "value": 1000, "range": "good" }, "lighthouse\_lcp": \{ "value": 2000, "range": "good" }, "lighthouse\_performance": \{ "value": 95, "range": "good" }, "lighthouse\_si": \{ "value": 3700, "range": "needsImprovement" }, "lighthouse\_tbt": \{ "value": 669, "range": "bad" }, "lighthouse\_tti": \{ "value": 2000, "range": "good" }, "relevance": 9.33, "status\_code": 200, "type": "page", "enrichment\_fields\_data": \{}, "content": \[ \{ "type": "canonical", "content": "null" }, \{ "type": "link\_alternate\_hreflang", "content": "null", "hreflang": "en" }, \{ "type": "link\_alternate\_hreflang", "content": "null", "hreflang": "x-default" }, \{ "type": "title", "content": "Some Title" }, \{ "type": "meta\_description", "content": "Some Meta Description" }, \{ "type": "h1", "content": "null" }, \{ "type": "open\_graph\_description", "content": "null" }, \{ "type": "open\_graph\_image", "content": "null" }, \{ "type": "open\_graph\_title", "content": "null" }, \{ "type": "open\_graph\_type", "content": "null" }, \{ "type": "open\_graph\_url", "content": "null" }, \{ "type": "twitter\_card", "content": "null" }, \{ "type": "twitter\_site", "content": "null" }, \{ "type": "twitter\_title", "content": "null" }, \{ "type": "twitter\_description", "content": "null" }, \{ "type": "twitter\_image", "content": "null" }, \{ "type": "google\_analytics", "content": "UA-12345678-1" }, \{ "type": "google\_tag\_manager", "content": "GTM-AB12345" } ], "schema\_org": \[], "segments": \[ "1111111" ], "app\_url": "[https://app.cm.conductor.com/websites/1-12345/pages/123456789](https://app.cm.conductor.com/websites/1-12345/pages/123456789)", "time\_document\_download": 123, "open\_issues": \[ \{ "name": "analytics/visual\_analytics\_missing" }, \{ "name": "open\_graph/description\_incorrect\_length" }, \{ "name": "open\_graph/title\_incorrect\_length" } ], "custom\_elements": \{}, "unstable\_last\_checked\_at": "2022-08-15T13:32:12+02:00" }, "data\_captured\_at": "2022-08-15T13:32:29+02:00", "is\_data\_golden": false } Successful response for a page with a 3xx HTTP response code (Redirects) \{ "data": \{ "url": "[https://cm.conductor.com/](https://cm.conductor.com/)", "url\_unique\_id": "123345", "is\_https": true, "is\_disallowed\_in\_robots\_txt": false, "is\_indexable": false, "is\_indexable\_due\_to\_meta\_robots": "not\_applicable", "is\_indexable\_due\_to\_x\_robots\_tag": "not\_applicable", "is\_in\_sitemap": false, "redirect": \{ "location": "[https://www.conductor.com/](https://www.conductor.com/)", "url": "[https://www.conductor.com/](https://www.conductor.com/)" }, "status\_code": 301, "type": "redirect", "enrichment\_fields\_data": \{}, "segments": \[], "app\_url": "[https://app.cm.conductor.com/websites/5-2457491/pages/12334563485638745638465837465836](https://app.cm.conductor.com/websites/5-2457491/pages/12334563485638745638465837465836)", "time\_document\_download": 123, "unstable\_last\_checked\_at": "2022-08-15T06:28:42+02:00" }, "data\_captured\_at": "2022-08-15T13:55:35+02:00", "is\_data\_golden": false } Successful response for a page with a 4xx HTTP response code (Missing) \{ "data": \{ "url": "[https://cm.conductor.com/this-page-does-not-exist/](https://cm.conductor.com/this-page-does-not-exist/)", "url\_unique\_id": "123345", "is\_https": true, "is\_disallowed\_in\_robots\_txt": false, "is\_indexable": false, "is\_indexable\_due\_to\_meta\_robots": "not\_applicable", "is\_indexable\_due\_to\_x\_robots\_tag": "not\_applicable", "is\_in\_sitemap": false, "status\_code": 404, "type": "missing", "enrichment\_fields\_data": \{}, "segments": \[], "app\_url": "[https://app.cm.conductor.com/websites/5-2457491/pages/12334563485638745638465837465836](https://app.cm.conductor.com/websites/5-2457491/pages/12334563485638745638465837465836)", "time\_document\_download": 123, "unstable\_last\_checked\_at": "2022-08-15T06:28:42+02:00" }, "data\_captured\_at": "2022-08-15T13:55:35+02:00", "is\_data\_golden": false }
401	Unauthorized: Missing authentication token. The request was received but it's lacking an authorization token and can therefore not be processed. Make sure to correctly set the Authorization header. Authentication failed. The request could not be processed because the supplied API token is invalid or expired. Examples `\{ "code": "auth\_missing\_token", "message": "Authentication token must be passed in Authorization HTTP header.", "errors": \[] } or \{ "code": "auth\_failed", "message": "Authentication token is expired or invalid.", "errors": \[] }`
403	Forbidden: Terms of use not accepted. You have not accepted Reporting API Terms of Use yet. You need to accept them in Account Settings before you start using Conductor Monitoring Reporting API. Our CDN is blocking your user agent, which might be a generic or default user agent like Python urllib3. Changing the user agent to something less generic or more closely resembling a browser often bypasses these restrictions. Example `\{ "code": "terms\_of\_use\_not\_accepted", "message": "Reporting API Terms of Use have not been accepted yet. Please accept Terms of Use in Account Settings.", "errors": \[] }`
404	Not found Examples `\{ "error": "Requested website ID was not found" }` \{ "error": "Requested URL was not found" } This response means that the URL passed in the request is not monitored by Conductor Monitoring. \{ "error": "Requested URL cannot be provided via Reporting API" } This response means that data for the URL passed in the request is not available via the Reporting API.
422	Unprocessable Entity. The request was received, but the authorization wasn't formatted correctly. Make sure to correctly configure the Authorization header as described in the Authentication section above.

#### Schema data types for this endpoint

Property	Data Type
`url`	string (absolute URL)
`is\_https`	boolean
`ga\_average\_time`	integer (seconds)
`ga\_bounce\_rate`	float (percentage)
`ga\_page\_views`	integer
`ga\_unique\_page\_views`	integer
`ga\_page\_value`	float
`ga\_date\_range`	array
`ga\_date\_range.since`	date (YYYY-MM-DD)
`ga\_date\_range.until`	date (YYYY-MM-DD)
`ga\_v4\_active\_users`	integer
`ga\_v4\_average\_engagement\_time`	integer (seconds)
`ga\_v4\_engagement\_rate`	float (percentage)
`ga\_v4\_screen\_page\_views`	integer
`ga\_v4\_date\_range`	array
`ga\_v4\_date\_range.since`	date (YYYY-MM-DD)
`ga\_v4\_date\_range.until`	date (YYYY-MM-DD)
`gsc\_clicks`	integer
`gsc\_impressions`	integer
`gsc\_ctr`	float (percentage)
`gsc\_position`	float
`gsc\_date\_range`	array
`gsc\_date\_range.since`	date (YYYY-MM-DD)
`gsc\_date\_range.until`	date (YYYY-MM-DD)
`health`	number
`relevance`	float
`is\_disallowed\_in\_robots\_txt`	boolean
`is\_indexable`	boolean
`is\_indexable\_due\_to\_meta\_robots`	boolean
`is\_indexable\_due\_to\_x\_robots\_tag`	boolean
`is\_in\_sitemap`	boolean
`status\_code`	integer
`time\_document\_download`	number
`type`	string
`content`	array
`content.type`	string
`content.content`	string
`custom\_elements`	array
`custom\_elements.custom\_element\_name`	string/number/boolean/date (depending on configuration)
`schema\_org`	array (containing different Schema properties as defined by schema.org)
`segments`	array of strings (containing Segment IDs)
`app\_url`	string (absolute URL)
`open\_issues`	array
`open\_issues.name`	string (see List of issues)
`lfa\_bing\_desktop\_frequency`	array
`lfa\_bing\_desktop\_frequency.value`	float
`lfa\_bing\_desktop\_frequency.unit`	string
`lfa\_bing\_desktop\_last\_visit`	datetime (ISO-8601 format)
`lfa\_bing\_frequency`	array
`lfa\_bing\_frequency.value`	float
`lfa\_bing\_frequency.unit`	string
`lfa\_bing\_last\_visit`	datetime (ISO-8601 format)
`lfa\_bing\_mobile\_frequency`	array
`lfa\_bing\_mobile\_frequency.value`	float
`lfa\_bing\_mobile\_frequency.unit`	string
`lfa\_bing\_mobile\_last\_visit`	datetime (ISO-8601 format)
`lfa\_google\_desktop\_frequency`	array
`lfa\_google\_desktop\_frequency.value`	float
`lfa\_google\_desktop\_frequency.unit`	string
`lfa\_google\_desktop\_last\_visit`	datetime (ISO-8601 format)
`lfa\_google\_frequency`	array
`lfa\_google\_frequency.value`	float
`lfa\_google\_frequency.unit`	string
`lfa\_google\_last\_visit`	datetime (ISO-8601 format)
`lfa\_google\_mobile\_frequency`	array
`lfa\_google\_mobile\_frequency.value`	float
`lfa\_google\_mobile\_frequency.unit`	string
`lfa\_google\_mobile\_last\_visit`	datetime (ISO-8601 format)
`lfa\_openai\_bot\_frequency`	array
`lfa\_openai\_bot\_frequency.value`	float
`lfa\_openai\_bot\_frequency.unit`	string
`lfa\_openai\_bot\_last\_visit`	datetime (ISO-8601 format)
`lfa\_openai\_desktop\_frequency`	array
`lfa\_openai\_desktop\_frequency.value`	float
`lfa\_openai\_desktop\_frequency.unit`	string
`lfa\_openai\_desktop\_last\_visit`	datetime (ISO-8601 format)
`lfa\_openai\_frequency`	array
`lfa\_openai\_frequency.value`	float
`lfa\_openai\_frequency.unit`	string
`lfa\_openai\_last\_visit`	datetime (ISO-8601 format)
`lfa\_openai\_search\_frequency`	array
`lfa\_openai\_search\_frequency.value`	float
`lfa\_openai\_search\_frequency.unit`	string
`lfa\_openai\_search\_last\_visit`	datetime (ISO-8601 format)
`lfa\_openai\_user\_frequency`	array
`lfa\_openai\_user\_frequency.value`	float
`lfa\_openai\_user\_frequency.unit`	string
`lfa\_openai\_user\_last\_visit`	datetime (ISO-8601 format)
`lfa\_perplexity\_bot\_frequency`	array
`lfa\_perplexity\_bot\_frequency.value`	float
`lfa\_perplexity\_bot\_frequency.unit`	string
`lfa\_perplexity\_bot\_last\_visit`	datetime (ISO-8601 format)
`lfa\_perplexity\_desktop\_frequency`	array
`lfa\_perplexity\_desktop\_frequency.value`	float
`lfa\_perplexity\_desktop\_frequency.unit`	string
`lfa\_perplexity\_desktop\_last\_visit`	datetime (ISO-8601 format)
`lfa\_perplexity\_frequency`	array
`lfa\_perplexity\_frequency.value`	float
`lfa\_perplexity\_frequency.unit`	string
`lfa\_perplexity\_last\_visit`	datetime (ISO-8601 format)
`lfa\_perplexity\_user\_frequency`	array
`lfa\_perplexity\_user\_frequency.value`	float
`lfa\_perplexity\_user\_frequency.unit`	string
`lfa\_perplexity\_user\_last\_visit`	datetime (ISO-8601 format)
`lighthouse\_performance`	array
`lighthouse\_performance.value`	integer
`lighthouse\_performance.range`	string
`lighthouse\_cls`	array
`lighthouse\_cls.value`	float
`lighthouse\_cls.range`	string
`lighthouse\_fcp`	array
`lighthouse\_fcp.value`	integer (milliseconds)
`lighthouse\_fcp.range`	string
`lighthouse\_lcp`	array
`lighthouse\_lcp.value`	integer (milliseconds)
`lighthouse\_lcp.range`	string
`lighthouse\_si`	array
`lighthouse\_si.value`	integer (milliseconds)
`lighthouse\_si.range`	string
`lighthouse\_tbt`	array
`lighthouse\_tbt.value`	integer (milliseconds)
`lighthouse\_tbt.range`	string
`lighthouse\_tti`	array
`lighthouse\_tti.value`	integer (milliseconds)
`lighthouse\_tti.range`	string
`unstable\_last\_checked\_at`	datetime (ISO-8601 format)
`data\_captured\_at`	datetime (ISO-8601 format)
`is\_data\_golden`	boolean

### Retrieving log file data for a website #### /v2/data/page\_lfa Use this endpoint to return log file data from Conductor Monitoring's [Log File Analysis](/docs/monitoring/log-file-analysis/) feature for your monitored pages. Log File Analysis data gives AEO and SEO professionals a better understanding of what search engines and AI bot crawlers are actually doing on their websites. Values returned for each day through this endpoint represent the number of times each crawler visited the page or pages for which you are querying data. #### Query Parameters `website_id` (Required). Can be inferred from the `GET /v2/entities/websites` endpoint described above. *** `urls` (Required). A list of up to 50 valid URL strings from your website. Note: if any of these URLs are unknown, the endpoint returns a 404 error. This list can be added using repeated query parameters as follows: `urls[]=https://example.com/page1&urls[]=https://example.com/page2&urls[]=https://example.com/page3…` *** `date_range` (Optional). This two-field parameter represents the range for which you want to query data. By default, when this parameter is not included in the request, the endpoint returns data for the most recent 30 days. Both of the following fields must be included for the `date_range` parameter to work: * `date_range[start_date]`. Enter the start date from which to query data. * `date_range[end_date]`. Enter an end date up to which you want to query data. This parameter must be formatted as follows: `date_range[start_date]=YYYY-MM-DD&date_range[end_date]=YYYY-MM-DD` #### Request Responses

200	Successful query execution Schema: See below Example \{ "data": \{ "urls": \[ \{ "url": "[https://www.example.com/](https://www.example.com/)", "visits\_per\_day": \{ "lfa\_bing\_desktop": \{ "2025-08-28": 2, "2025-08-29": 1, "2025-08-30": 2, ... }, "lfa\_bing\_mobile": \{...}, "lfa\_google\_desktop": \{...}, "lfa\_google\_mobile": \{...}, "lfa\_openai\_bot": \{...}, "lfa\_openai\_search": \{...}, "lfa\_openai\_user": \{...}, "lfa\_perplexity\_bot": \{...}, "lfa\_perplexity\_user": \{...} } }, \{ "url": "[https://www.example.com/about-us/](https://www.example.com/about-us/)", "visits\_per\_day": \{...} }, \{...} ] }, "data\_captured\_at": "2026-01-06T16:07:41+01:00" }
400	Log File Analysis is not enabled for this website in Conductor Monitoring. Examples `\{ "error": "Log File Analysis is not enabled" }`
403	Not all URLs are one of the following types: Page Redirect Server error Missing Our CDN is blocking your user agent, which might be a generic or default user agent like Python urllib3. Changing the user agent to something less generic or more closely resembling a browser often bypasses these restrictions. Example `\{ "error": "Requested URL cannot be provided via Reporting API (url)" }`
404	Not found Example `\{ "error": "Requested URL was not found (url)" }`

#### Schema data types for this endpoint

Property	Data Type
`urls`	array
`urls.url`	string (absolute URL)
`urls.visits\_per\_day`	array
`urls.visits\_per\_day.lfa\_bing\_desktop`	array
`urls.visits\_per\_day.lfa\_bing\_desktop.YYYY-MM-DD`	integer
`urls.visits\_per\_day.lfa\_bing\_mobile`	array
`urls.visits\_per\_day.lfa\_bing\_mobile.YYYY-MM-DD`	integer
`urls.visits\_per\_day.lfa\_google\_desktop`	array
`urls.visits\_per\_day.lfa\_google\_desktop.YYYY-MM-DD`	integer
`urls.visits\_per\_day.lfa\_google\_mobile`	array
`urls.visits\_per\_day.lfa\_google\_mobile.YYYY-MM-DD`	integer
`urls.visits\_per\_day.lfa\_openai\_bot`	array
`urls.visits\_per\_day.lfa\_openai\_bot.YYYY-MM-DD`	integer
`url.visits\_per\_day.lfa\_openai\_search`	array
`url.visits\_per\_day.lfa\_openai\_search.YYYY-MM-DD`	integer
`url.visits\_per\_day.lfa\_openai\_user`	array
`url.visits\_per\_day.lfa\_openai\_user.YYYY-MM-DD`	integer
`url.visits\_per\_day.lfa\_perplexity\_bot`	array
`url.visits\_per\_day.lfa\_perplexity\_bot.YYYY-MM-DD`	integer
`url.visits\_per\_day.lfa\_perplexity\_user`	array
`url.visits\_per\_day.lfa\_perplexity\_user.YYYY-MM-DD`	integer
`data\_captured\_at`	datetime (ISO-8601 format)

### Retrieving list of alerts for a website #### /v2/alerts Use this endpoint to get a list of alerts for a website monitored in your account. #### Query Parameters `website_id` (Required). Can be inferred from the `GET /v2/entities/websites` endpoint described above. #### Request Responses

200	Successful query execution Schema: See below Example \{ "data": \[ \{ "id": "1", "app\_url": "[https://app.cm.conductor.com/websites/1-234/alerts?alert=1](https://app.cm.conductor.com/websites/1-234/alerts?alert=1)", "date\_last\_updated": "2022-08-04T13:40:50+02:00", "date\_opened": "2022-07-27T09:34:44+02:00", "scope": "website", "type": "content\_change.meta\_description" }, \{ "id": "2", "app\_url": "[https://app.cm.conductor.com/websites/1-234/alerts?alert=2](https://app.cm.conductor.com/websites/1-234/alerts?alert=2)", "date\_last\_updated": "2022-08-04T13:40:50+02:00", "date\_opened": "2022-07-26T07:03:25+02:00", "scope": "website", "type": "pages\_became\_non\_indexable" } ] }
401	Unauthorized: Missing authentication token. The request was received but it's lacking an authorization token and can therefore not be processed. Make sure to correctly set the Authorization header. Authentication failed. The request could not be processed because the supplied API token is invalid or expired. Examples `\{ "code": "auth\_missing\_token", "message": "Authentication token must be passed in Authorization HTTP header.", "errors": \[] } or \{ "code": "auth\_failed", "message": "Authentication token is expired or invalid.", "errors": \[] }`
403	Forbidden: Terms of use not accepted. You have not accepted Reporting API Terms of Use yet. You need to accept them in Account Settings before you start using Conductor Monitoring Reporting API. Our CDN is blocking your user agent, which might be a generic or default user agent like Python urllib3. Changing the user agent to something less generic or more closely resembling a browser often bypasses these restrictions. Example `\{ "code": "terms\_of\_use\_not\_accepted", "message": "Reporting API Terms of Use have not been accepted yet. Please accept Terms of Use in Account Settings.", "errors": \[] }`
404	Not found Example `\{ "error": "Requested website ID was not found" }`
422	Unprocessable Entity. The request was received, but the authorization wasn't formatted correctly. Make sure to correctly configure the Authorization header as described in the Authentication section above.

#### Schema data types for this endpoint

Property	Data Type
`id`	string
`app\_url`	string (absolute URL)
`date\_last\_updated`	datetime (ISO 8601 format)
`date\_opened`	datetime (ISO 8601 format)
`scope`	string
`type`	string

### Retrieving list of pages for a website alert #### /v2/alerts/alert\_pages Use this endpoint to get a list of pages for a specific website alert. ``` GET /v2/alerts/alert_pages?website_id=&alert_id=&page=1&per_page=100 ``` #### Query Parameters `website_id` (Required). Can be inferred from the `GET /v2/entities/websites` endpoint described above. *** `alert_id` (Required). Can be inferred from the `GET /v2/alerts` endpoint described above. *** `page` and `per_page` (Optional). Can be used for pagination. #### Request Responses

200	Successful query execution Schema: See below Example \{ "data": \{ "total": 1, "urls": \[ \{ "app\_url": "[https://app.cm.conductor.com/websites/1-2/pages/3](https://app.cm.conductor.com/websites/1-2/pages/3)", "relevance": 6.05, "segments": \[], "status": "entered", "url": "[https://www.conductor.com/](https://www.conductor.com/)", }, ] } }
401	Unauthorized: Missing authentication token. The request was received but it's lacking an authorization token and can therefore not be processed. Make sure to correctly set the Authorization header. Authentication failed. The request could not be processed because the supplied API token is invalid or expired. Examples `\{ "code": "auth\_missing\_token", "message": "Authentication token must be passed in Authorization HTTP header.", "errors": \[] } or \{ "code": "auth\_failed", "message": "Authentication token is expired or invalid.", "errors": \[] }`
403	Forbidden: Terms of use not accepted. You have not accepted Reporting API Terms of Use yet. You need to accept them in Account Settings before you start using Conductor Monitoring Reporting API. Our CDN is blocking your user agent, which might be a generic or default user agent like Python urllib3. Changing the user agent to something less generic or more closely resembling a browser often bypasses these restrictions. Example `\{ "code": "terms\_of\_use\_not\_accepted", "message": "Reporting API Terms of Use have not been accepted yet. Please accept Terms of Use in Account Settings.", "errors": \[] }`
404	Not found Example `\{ "error": "Requested website ID was not found" }`
422	Unprocessable Entity. The request was received, but the authorization wasn't formatted correctly. Make sure to correctly configure the Authorization header as described in the Authentication section above.

#### Schema data types for this endpoint

Property	Data Type
`total`	integer
`urls`	array
`urls.app\_url`	string (absolute URL)
`urls.relevance`	float
`segments`	array of strings (containing Segment IDs, see Retrieving a list of segments)
`status`	string
`urls.url`	string (absolute URL)

## Retrieving a list of issues for a website or segment #### /v2/data/issues Use this endpoint to get a list of issues for a specific website in your account. ``` GET /v2/data/issues?website_id= ``` #### Query Parameters `website_id` (Required). Can be inferred from the `GET /v2/entities/websites` endpoint described above. *** `scope` (Required). Determines whether data for the whole website is returned or specific parts. Potential values: * `website`. Retrieves data for the whole website. * `segment:{segment_id}`. Retrieves data for a specific segment. Segment IDs can be inferred with the `GET /v2/entities/segments` endpoint described above. * `segment_label:{segment_label}`. Retrieves data for a specific segment. Segment label can be inferred from the `GET /v2/entities/segments` endpoint described above. #### Request Responses

200	Successful query execution Schema: See below Example \{ "data": \[ \{ "name": "analytics/analytics\_missing", "points\_gained": 79, "points\_to\_gain": 0, "scope": "pages", "type": "opportunity", "tags": "seo", "pages\_per\_issue\_state": \{ "absolute\_number": \{ "open": 0, "closed": 0, "ignored": 527, "not\_applicable": 0, "not\_required": 0, "unknown": 0 }, "percentage": \{ "open": 0, "closed": 0, "ignored": 100, "not\_applicable": 0, "not\_required": 0, "unknown": 0 } } }, ], "data\_captured\_at": "2022-08-04T14:03:19+02:00", "is\_data\_golden": false }
401	Unauthorized: Missing authentication token. The request was received but it's lacking an authorization token and can therefore not be processed. Make sure to correctly set the Authorization header. Authentication failed. The request could not be processed because the supplied API token is invalid or expired. Examples `\{ "code": "auth\_missing\_token", "message": "Authentication token must be passed in Authorization HTTP header.", "errors": \[] } or \{ "code": "auth\_failed", "message": "Authentication token is expired or invalid.", "errors": \[] }`
403	Forbidden: Terms of use not accepted. You have not accepted Reporting API Terms of Use yet. You need to accept them in Account Settings before you start using Conductor Monitoring Reporting API. Our CDN is blocking your user agent, which might be a generic or default user agent like Python urllib3. Changing the user agent to something less generic or more closely resembling a browser often bypasses these restrictions. Example `\{ "code": "terms\_of\_use\_not\_accepted", "message": "Reporting API Terms of Use have not been accepted yet. Please accept Terms of Use in Account Settings.", "errors": \[] }`
404	Not found Example `\{ "error": "Requested website ID was not found" }`
422	Unprocessable Entity. The request was received, but the authorization wasn't formatted correctly. Make sure to correctly configure the Authorization header as described in the Authentication section above.

#### Schema data types for this endpoint

Property	Data Type
`name`	string
`points\_gained`	integer
`points\_to\_gain`	integer
`type`	string (enum: `critical`, `fix`, `opportunity`)
`tags`	array (enum: `aeo`, `seo`)
`scope`	string
`pages\_per\_issue\_state`	array
`pages\_per\_issue\_state.absolute\_number.open`	integer
`pages\_per\_issue\_state.absolute\_number.closed`	integer
`pages\_per\_issue\_state.absolute\_number.ignored`	integer
`pages\_per\_issue\_state.absolute\_number.not\_applicable`	integer
`pages\_per\_issue\_state.absolute\_number.not\_required`	integer
`pages\_per\_issue\_state.absolute\_number.unknown`	integer
`pages\_per\_issue\_state.percentage.open`	integer
`pages\_per\_issue\_state.percentage.closed`	integer
`pages\_per\_issue\_state.percentage.ignored`	integer
`pages\_per\_issue\_state.percentage.not\_applicable`	integer
`pages\_per\_issue\_state.percentage.not\_required`	integer
`pages\_per\_issue\_state.percentage.unknown`	integer
`data\_captured\_at`	datetime (ISO-8601 format)
`is\_data\_golden`	boolean

### Retrieving list of pages for a website issue #### /v2/data/affected\_pages Use this endpoint to get list of pages for a specific website issue. #### Query Parameters `website_id` (Required). Can be inferred from the `GET /v2/entities/websites` endpoint described above. *** `issue` (Required). Can be inferred from the `GET /v2/data/issues` endpoint described above. *** `page` and `per_page` (Optional). Can be used for pagination. #### Request Responses

200	Successful query execution Schema: See below Example \{ "data": \{ "total": 1, "urls": \[ \{ "app\_url": "[https://app.cm.conductor.com/websites/1-123455/pages/123455678](https://app.cm.conductor.com/websites/1-123455/pages/123455678)", "relevance": 9.33, "segments": \[ "88611", ], "url": "[https://www.conductor.com/](https://www.conductor.com/)", "url\_path": "/" }, ] }, "data\_captured\_at": "2022-08-16T12:42:35+02:00", "is\_data\_golden": false }
401	Unauthorized: Missing authentication token. The request was received but it's lacking an authorization token and can therefore not be processed. Make sure to correctly set the Authorization header. Authentication failed. The request could not be processed because the supplied API token is invalid or expired. Examples `\{ "code": "auth\_missing\_token", "message": "Authentication token must be passed in Authorization HTTP header.", "errors": \[] } or \{ "code": "auth\_failed", "message": "Authentication token is expired or invalid.", "errors": \[] }`
403	Forbidden: Terms of use not accepted. You have not accepted Reporting API Terms of Use yet. You need to accept them in Account Settings before you start using Conductor Monitoring Reporting API. Our CDN is blocking your user agent, which might be a generic or default user agent like Python urllib3. Changing the user agent to something less generic or more closely resembling a browser often bypasses these restrictions. Example `\{ "code": "terms\_of\_use\_not\_accepted", "message": "Reporting API Terms of Use have not been accepted yet. Please accept Terms of Use in Account Settings.", "errors": \[] }`
404	Not found Example `\{ "error": "Requested website ID was not found" }`
422	Unprocessable Entity. The request was received, but the authorization wasn't formatted correctly. Make sure to correctly configure the Authorization header as described in the Authentication section above.

#### Schema data types for this endpoint

Property	Data Type
`total`	integer
`urls`	array
`urls.app\_url`	string (absolute URL)
`urls.relevance`	float
`segments`	array of strings (containing Segment IDs)
`urls.url`	string (absolute URL)
`urls.path`	string (absolute URL)
`data\_captured\_at`	datetime (ISO-8601 format)
`is\_data\_golden`	boolean

### List of issues

Issue	Issue Tag	Type	Description
`analytics/analytics\_missing`	seo	opportunity	No analytics installed
`analytics/visual\_analytics\_missing`	seo	opportunity	No visual analytics installed
`h1/duplicate`	aeo, seo	fix	H1 heading is not unique
`h1/incorrect\_length`	aeo, seo	fix	H1 heading has incorrect length
`h1/missing`	aeo, seo	fix	H1 heading is missing
`h1/too\_many`	aeo, seo	fix	More than one H1 heading
`canonical\_link/incorrectly\_canonicalized`	aeo, seo	fix	Canonical link to other page present on non-indexable page
`canonical\_link/missing`	aeo, seo	fix	Canonical link is missing
`canonical\_link/points\_to\_unindexable`	aeo, seo	critical	Canonical link is pointing to non-indexable page
`canonical\_link/too\_many`	aeo, seo	fix	More than one canonical link
`content\_depth/html\_size\_too\_big`	aeo, seo	opportunity	Content size greater than 2,097,152 bytes
`content\_depth/body\_empty`	aeo, seo	critical	No content in \
`content\_depth/body\_size\_too\_big`	aeo, seo	opportunity	Word count in \ greater than 5000 words
`content\_depth/body\_size\_too\_small`	aeo, seo	critical	Word count in \ fewer than 600 words
`content\_depth/text\_to\_code\_ratio`	aeo, seo	fix	Text-to-code ratio less than 10%
`content\_depth/rich\_text\_elements\_are\_missing`	aeo, seo	fix	Rich text elements (lists/quotes/tables ) not present in \
`images/alt\_attribute`	aeo, seo	fix	Images are missing alt-attribute
`links/broken`	aeo, seo	critical	Page contains broken links
`links/redirected`	aeo, seo	fix	Page contains links to redirects
`links/to\_canonicalized`	aeo, seo	fix	Page contains links to canonicalized URLs
`meta\_description/duplicate`	aeo, seo	fix	Meta description is not unique
`meta\_description/incorrect\_length`	aeo, seo	fix	Meta description has incorrect length
`meta\_description/missing`	aeo, seo	fix	Meta description is missing
`meta\_description/too\_many`	aeo, seo	fix	There are multiple meta descriptions on the page
`title/duplicate`	aeo, seo	fix	Page title is not unique
`title/incorrect\_length`	aeo, seo	fix	Page title has incorrect length
`title/missing`	aeo, seo	critical	Title is missing
`title/too\_many`	aeo, seo	fix	There are multiple titles on pages
`open\_graph/description\_incorrect\_length`	seo	opportunity	Open Graph description has incorrect length
`open\_graph/description\_missing`	seo	opportunity	Open Graph description is missing
`open\_graph/image\_missing`	seo	opportunity	Open Graph image is missing
`open\_graph/title\_incorrect\_length`	seo	opportunity	Open Graph title has incorrect length
`open\_graph/title\_missing`	seo	opportunity	Open Graph title is missing
`open\_graph/url\_missing`	seo	opportunity	Open Graph URL is missing
`twitter\_cards/description\_incorrect\_length`	seo	opportunity	Twitter Cards description has incorrect length
`twitter\_cards/description\_missing`	seo	opportunity	Twitter Cards description is missing
`twitter\_cards/image\_missing`	seo	opportunity	Twitter Cards image is missing
`twitter\_cards/site\_missing`	seo	opportunity	Twitter Cards site property is missing
`twitter\_cards/title\_incorrect\_length`	seo	opportunity	Twitter Cards title has incorrect length
`twitter\_cards/title\_missing`	seo	opportunity	Twitter Cards title is missing
`twitter\_cards/type\_invalid`	seo	opportunity	Twitter Cards type value is not valid
`twitter\_cards/type\_missing`	seo	opportunity	Twitter Cards type is not present
`xml\_sitemap/incorrectly\_missing`	aeo, seo	critical	Page is not included in XML sitemap
`xml\_sitemap/incorrectly\_present`	aeo, seo	fix	Pages incorrectly present in XML sitemap
`hreflang/conflicting\_targets`	seo	fix	Hreflang attribute value is pointed to multiple targets
`hreflang/invalid\_target`	seo	fix	Invalid hreflang target present
`hreflang/invalid\_value`	seo	fix	Invalid hreflang attribute value present
`hreflang/missing\_self\_reference`	seo	fix	Self-referencing hreflang not present
`hreflang/missing\_specific\_audience`	seo	fix	Hreflang implementation does not contain any hreflang attribute specifying a language and/or region
`hreflang/missing\_x\_default`	seo	fix	Hreflang attribute with x-default value is missing
`robot\_directives/conflicting`	aeo, seo	critical	Valid robot directives give conflicting directives to search engines
`robot\_directives/invalid`	aeo, seo	critical	Valid robot directives give conflicting directives to search engines
`robot\_directives/unsupported`	aeo, seo	critical	Valid but unsupported robot directives to a search engine present
`lighthouse/performance`	aeo, seo	opportunity	Performance score is too low
`lighthouse/fcp`	aeo, seo	opportunity	First Contentful Paint takes too long
`lighthouse/lcp`	aeo, seo	opportunity	Largest Contentful Paint takes too long
`lighthouse/tti`	aeo, seo	opportunity	Time To Interactive takes too long
`lighthouse/si`	aeo, seo	opportunity	Speed Index is too high
`lighthouse/tbt`	aeo, seo	opportunity	Total Blocking Time is too long
`lighthouse/cls`	aeo, seo	opportunity	Cumulative Layout Shift is too large
`semantic\_html/core\_layout\_missing`	aeo, seo	critical	Core semantic HTML structure is present
`semantic\_html/multiple\_main\_elements`	aeo, seo	critical	Single \ element is present
`js\_rendering/title\_changed`	aeo, seo	critical	Page title matches between raw HTML and rendered DOM
`js\_rendering/canonical\_changed`	aeo, seo	critical	Canonical link matches between raw HTML and rendered DOM
`js\_rendering/h1\_changed`	aeo, seo	critical	H1 heading matches between raw HTML and rendered DOM
`js\_rendering/word\_count\_changed`	aeo, seo	fix	Main content word count matches between raw HTML and rendered DOM
`js\_rendering/outgoing\_links\_changed`	aeo, seo	fix	Outgoing links match between raw HTML and rendered DOM
`schema\_org/errors`	aeo, seo	fix	Schema.org implementation has an invalid structure
`schema\_org/invalid\_json`	aeo, seo	fix	Schema element with invalid JSON-LD object present
`schema\_org/invalid\_property`	aeo, seo	fix	All schema properties are valid for their declared types
`schema\_org/invalid\_property\_value`	aeo, seo	fix	All schema property values have correct format
`schema\_org/invalid\_type`	aeo, seo	fix	All schema @type values are recognized
`schema\_org/mandatory\_schema\_missing`	aeo, seo	critical	Required schema types are present
`schema\_org/missing\_required\_property`	aeo, seo	fix	All required schema properties are present
`schema\_org/missing\_recommended\_property`	aeo, seo	opportunity	All recommended schema properties are present

## Retrieving historical data Certain endpoints support retrieving historical data using the `captured_at` query parameter. The `captured_at` parameter is a timestamp indicating when the data was collected by Conductor Monitoring and supports the [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) datetime format. The `captured_at` parameter is supported by the following endpoints: * [Retrieving statistics for a website or segment](/docs/other-apis/conductor-monitoring-reporting-api/#retrieving-statistics-for-a-website-or-websites-segment) * [Retrieving a list of issues for a website or segment](/docs/other-apis/conductor-monitoring-reporting-api/#retrieving-a-list-of-issues-for-a-website-or-segment) For example, to retrieve the statistics for a website from June 1st, 2022 at 05:00, you can send the following request: ``` GET /v2/data/statistics?website_id={website_id}&captured_at=2022-06-01T05:00:00+00:00 ``` ### Data is golden The `is_data_golden` property indicates whether the response to this request is golden or not. When the data is golden, it means that when the same request is made at a later point in time, the retrieved data will always be exactly the same. In context of Conductor Monitoring’s data, this applies to retrieving data historically. The historical data retrieved from Conductor Monitoring will always be golden as the data cannot change anymore, as opposed to retrieving current data which is subject to change.