> ## Documentation Index > Fetch the complete documentation index at: https://docs.didit.me/llms.txt > Use this file to discover all available pages before exploring further. # 今日每小时验证数 API > 通过 Didit 获取您所在时区内今日每小时的用户验证数据，并与上周同一天进行对比，同时查看已通过、审核中和已拒绝的数量。 按小时获取今日验证数 API 提示词 将提示词复制到剪贴板 \

\`Read today's verifications of my Didit application hour by hour.

Endpoint:
GET https://verification.didit.me/v3/organization/{organization_id}/application/{application_id}/analytics/today/

Authentication:
Use the x-api-key header with my Didit API key. Only a full-access key works: any scoped key gets 403 "This API key has no access to this endpoint.". application_id must be the application the key belongs to.

Goal:
\- Show today's verification volume by hour against the same weekday last week, and today's outcomes, in my own dashboard.

Query parameters:
\- tz - IANA time zone whose midnight starts today, for example Europe/Madrid. Omit it for UTC.

Behavior:
\- hours - 24 counts: today's user verification (KYC) sessions by the local hour they were created in. The hours still to come are 0.
\- previous_hours - the same 24 counts for previous_date, the same weekday one week before.
\- total - today's verifications so far. previous_total_so_far - the comparison day's up to the same local time, so (total - previous_total_so_far) / previous_total_so_far compares the same part of both days.
\- outcomes - of today's verifications, how many are approved, in review and declined now. The rest are not finished yet.
\- current_hour - the local hour it is now. A day on which the clocks change has 23 or 25 hours: the missing hour stays 0 and the repeated hour holds both.

Example call:
curl -X GET "https://verification.didit.me/v3/organization/11111111-2222-3333-4444-555555555555/application/aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee/analytics/today/?tz=Europe%2FMadrid" \
-H "x-api-key: YOUR_API_KEY"

Failure modes:
\- 400 - {"tz": ["Unknown time zone: Europe/Atlantis."]} for a name the time zone database does not know.
\- 401 - the API key has expired.
\- 403 - missing or invalid key ({"detail": "Authentication credentials were not provided or are invalid."}), a key of another application ({"detail": "You do not have permission to perform this action."}), any scoped key, or a request from outside the key's IP list.
\- 429 - more than 600 GET requests per minute with this key.

Side effects: none. Not billed.

For the full integration shape, see /integration/integration-prompt.`

\
粘贴到 Didit 的按小时获取今日验证数 API 会返回今日每个小时的用户验证数，起点为您所传时区的当地午夜，并与上周同一星期几的相同时段并排显示。它是 Business Console 首页数量卡片背后的数据。| 字段 | 含义 | | - | - | | `hours` | 今日每个当地小时的验证数，从 00:00 开始。尚未到达的时段为 `0`。 | | `previous_hours` | `previous_date` 当天相同时段的验证数，即一周前的同一星期几。 | | `total`, `previous_total_so_far` | 今日截至目前的总数，以及对比日截至相同当地时间的总数。 | | `outcomes` | 今日验证中，当前为 `approved`、`in_review` 和 `declined` 的数量。 |这些数据是实时从您的验证记录中读取的，因此刚刚创建的验证已经计入其中。如需查看日期范围及其他仪表板数据，请使用 [获取应用分析](https://docs.didit.me/zh/management-api/analytics/get.md)。> [!NOTE] > > 只有具有完整访问权限的 API 密钥才能调用此 endpoint。受限权限的密钥无论拥有何种访问权限，都会收到 `403`，其他应用的密钥同样如此。详见 [API 密钥](https://docs.didit.me/zh/console/api-keys.md)。## 相关内容- [获取应用分析](https://docs.didit.me/zh/management-api/analytics/get.md) - [分析仪表板](https://docs.didit.me/zh/console/analytics.md) - [API 密钥与受限访问](https://docs.didit.me/zh/console/api-keys.md) ## OpenAPI ````yaml zh/openapi-25.json GET /v3/organization/{organization_id}/application/{application_id}/analytics/today/ openapi: 3.0.0 info: version: 3.0.0 title: Didit Verification API description: 身份证件验证 API。使用 x-api-key 请求头进行身份验证。 servers: - url: https://verification.didit.me security: [] tags: [] paths: /v3/organization/{organization_id}/application/{application_id}/analytics/today/: get: tags: - Analytics summary: 获取今日按小时统计的验证量 description: >- 今天的用户验证（KYC）会话，从 `tz` 中的本地午夜开始，按创建的本地小时计数，与一周前同一工作日的相同小时并列展示，并按每个会话当前的结果进行划分：已通过、审核中或已拒绝。这是 Business Console 首页的业务量卡片。 `total` 为今天截至目前的总量。`previous_total_so_far` 仅统计对比日截至相同本地时间的数据，因此两者之间的变化对比了两个日期的相同时间段。今天尚未到来的小时为 `0`。发生夏令时时钟调整的日子有 23 或 25 个小时：缺失的小时保持为 `0`，重复的小时则包含这两个小时的数据。 operationId: get_application_analytics_today parameters: - name: organization_id in: path required: true schema: type: string format: uuid description: 组织 UUID。 example: 11111111-2222-3333-4444-555555555555 - name: application_id in: path required: true schema: type: string format: uuid description: 应用 UUID。必须是该 API 密钥所属的应用：在任何其他应用上使用该密钥都会返回 `403`。 example: aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee - name: tz in: query required: false schema: type: string default: UTC example: Europe/Madrid description: >- 午夜即代表今天开始的 IANA 时区，例如 `Europe/Madrid` 或 `America/Mexico_City`。省略则默认为 UTC。 responses: '200': description: 今天按本地小时划分的验证量、对比日的数据以及今天的结果。 content: application/json: schema: $ref: '#/components/schemas/ApplicationAnalyticsToday' examples: Madrid, 14:00: value: time_zone: Europe/Madrid date: '2026-10-30' current_hour: 14 previous_date: '2026-10-23' hours: - 3 - 1 - 0 - 0 - 1 - 2 - 4 - 9 - 14 - 18 - 21 - 19 - 22 - 24 - 27 - 0 - 0 - 0 - 0 - 0 - 0 - 0 - 0 - 0 previous_hours: - 2 - 1 - 1 - 0 - 1 - 3 - 5 - 8 - 12 - 16 - 19 - 18 - 20 - 22 - 24 - 26 - 23 - 19 - 15 - 12 - 9 - 7 - 5 - 3 total: 165 previous_total_so_far: 151 outcomes: approved: 139 in_review: 6 declined: 18 '400': description: 未知的时区。响应体以参数为键，包含消息列表。 content: application/json: schema: type: object additionalProperties: type: array items: type: string examples: Unknown time zone: value: tz: - 'Unknown time zone: Europe/Atlantis.' '401': description: API 密钥已过期。仅创建时设置了到期日期的密钥才会过期；超过该日期后，使用它的每次请求都会返回 `401`。 content: application/json: schema: type: object properties: detail: type: string examples: Expired key: value: detail: This API key has expired. '403': description: >- 该请求不被允许。请查看 `detail`：缺失或无效的 API 密钥（绝不会返回 `401`）、属于其他应用的密钥、任何限定作用域的密钥，或来自密钥 IP 列表之外的请求。 content: application/json: schema: type: object properties: detail: type: string examples: Missing or invalid key: value: detail: >- Authentication credentials were not provided or are invalid. Another application: value: detail: You do not have permission to perform this action. Scoped key: value: detail: This API key has no access to this endpoint. Outside the key's IP list: value: detail: This API key can't be used from this IP address. '429': description: 使用此 API 密钥的 GET 请求每分钟超过 600 次。请等待 `Retry-After` 中指定的秒数，然后再重试。 content: application/json: schema: type: object properties: detail: type: string examples: Throttled: value: detail: >- GET request rate limit exceeded. You can make up to 600 requests per minute. headers: Retry-After: description: 距离当前一分钟窗口重置的秒数。 schema: type: integer example: 23 X-RateLimit-Limit: description: 在此预算中每分钟允许的请求数。 schema: type: integer X-RateLimit-Remaining: description: 当前时间窗口内剩余的请求数。 schema: type: integer X-RateLimit-Reset: description: 窗口重置的 Unix 时间。 schema: type: integer security: - ApiKeyAuth: [] x-codeSamples: - lang: curl label: curl source: >- curl -X GET 'https://verification.didit.me/v3/organization/11111111-2222-3333-4444-555555555555/application/aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee/analytics/today/?tz=Europe%2FMadrid' \ -H 'x-api-key: YOUR_API_KEY' components: schemas: ApplicationAnalyticsToday: type: object description: 今天按本地小时划分的验证量与上周同工作日对比。 required: - time_zone - date - current_hour - previous_date - hours - previous_hours - total - previous_total_so_far - outcomes properties: time_zone: type: string description: 日期及其时间所处的 IANA 时区。 example: Europe/Madrid date: type: string format: date description: 该时区下的今天。 example: '2026-10-30' current_hour: type: integer minimum: 0 maximum: 23 description: 当前的本地小时数。 example: 14 previous_date: type: string format: date description: 对比基准日：一周前的同一个工作日/周几。 example: '2026-10-23' hours: type: array items: type: integer minimum: 0 minItems: 24 maxItems: 24 description: 今日自 00:00 起按本地时间每小时创建的验证数。尚未到来的小时数为 0。 previous_hours: type: array items: type: integer minimum: 0 minItems: 24 maxItems: 24 description: 对比日自 00:00 起按本地时间每小时创建的验证数。 total: type: integer minimum: 0 description: 今日截至目前创建的验证数。 example: 165 previous_total_so_far: type: integer minimum: 0 description: 对比日截至相同本地时间所创建的验证数。 example: 151 outcomes: type: object description: 在今天的验证中，当前已通过、等待人工审核以及已拒绝的数量。其余尚未完成。 required: - approved - in_review - declined properties: approved: type: integer minimum: 0 in_review: type: integer minimum: 0 declined: type: integer minimum: 0 securitySchemes: ApiKeyAuth: type: apiKey in: header name: x-api-key description: >- 您的应用 API 密钥，可在 Business Console 的“开发者 -> API 密钥”中获取。主密钥拥有完整访问权限。指定名称的密钥可设置作用域：针对每个资源设为无权限、只读或读写，限定于特定工作流或已通过的会话、限定于 IP 地址列表，以及设置到期日期。401 表示密钥错误、已撤销或已过期；403 表示未发送密钥、密钥无权访问该资源或操作，或请求来自其 IP 列表之外的地址；在会话路由上返回 404 表示该会话不在该密钥允许的工作流或状态范围内。没有媒体访问权限的密钥获取到的图片、视频和 PDF URL 将为 null；没有会话写入权限的密钥获取到的会话链接和 token 将为 null。请参阅 https://docs.didit.me/console/api-keys。 ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.