Claritymovement API
Claritymovement API as documented publicly: 2 operations. Contract generated from the documentation by API Evangelist (2026-10-08); not the provider's own document.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/claritymovement:claritymovement-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.1.0
info:
title: Claritymovement API
version: '2026-10-08'
description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-10-08: 2 operation(s) read from 3 public documentation page(s) (each operation
names its page in x-source). This is not the provider''s published contract; Claritymovement has published no machine-readable contract that
the pipeline could find. Engine: local.'
x-evidence-tiers:
code-example: 0
documentation: 2
pages-with-code: 0
pages-read: 3
x-generated-from: documentation
x-provenance: generated
x-authored-by: API Evangelist
x-generated: '2026-10-08'
x-generator: generate-contract-from-docs.py
x-engine: local
x-sources:
- https://api-docs.clarity.io/faq/whats-this-error.html
- https://api-docs.clarity.io/v2/measurements/report-request.html
- https://api-docs.clarity.io/v2/devices/alarms.html
servers:
- url: https://clarity-data-api.clarity.io
paths:
/v2/report-requests:
post:
operationId: post_v2_report_requests
tags:
- Report Requests
summary: What's this error ...? - API Guide
x-source: https://api-docs.clarity.io/faq/whats-this-error.html
responses:
'201':
description: Success (status as documented)
x-evidence:
kind: documentation
/v2/report-requests/{reportid}:
get:
operationId: get_v2_report_requests_reportid
tags:
- Report Requests
summary: If successful, returns the report request, including its status and the parameters submitted.
description: Retrieves the status and details of a previously created report request.
x-source: https://api-docs.clarity.io/v2/measurements/report-request.html
parameters:
- name: reportid
in: path
required: true
schema:
type: string
- name: x-api-key
in: header
required: true
schema:
type: string
description: the API key string.
responses:
'200':
description: Success (status as documented)
content:
application/json:
schema:
$ref: '#/components/schemas/GetV2ReportRequestsReportidResponse'
x-evidence:
kind: documentation
components:
schemas:
GetV2ReportRequestsReportidResponse:
type: object
properties:
reportId:
type: string
description: Identifier of the report request.
reportStatus:
type: string
description: Current status (e.g., "in-progress", "succeeded", "failed").
message:
type: string
description: Status message.
report:
type: string
description: The type of report requested.
urls:
type: array
description: Array of URLs to the generated files (populated when status is succeeded).
query:
type: object
description: Echo of the query parameters originally submitted.
tags:
- name: Report Requests