> ## 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 公开状态数据

> GET /v3/status/ 是 Didit 公开且无需认证的状态数据源，提供各服务的运行状态及近 7 天的事件记录，适用于状态组件与健康检查。



服务状态提示词
        将提示词复制到剪贴板



      
      

\<pre>

\`Read Didit's public service status feed.

GET https://verification.didit.me/v3/status/

Auth: NONE. Send no auth header.

Success (HTTP 200):
\- status: worst state of any service right now: "operational" | "degraded" | "down"
\- updated_at: ISO 8601 time Didit built the response (up to 30 seconds old)
\- services[]: one { key, name, status } per service. Match on key, never on name. Keys:
service_id_verification, service_liveness_face_match, service_aml_screening, service_kyb_registries,
service_database_validation, service_phone_delivery, service_email_delivery, service_transaction_monitoring
\- incidents[]: newest started_at first. Every ongoing incident plus those resolved in the last 7 days (at most 50 resolved). Each:
\{ id, service, service_name, state ("degraded" | "down"), status ("ongoing" | "resolved"), title, body,
affected, country_name, started_at, resolved_at (null while ongoing), duration_minutes (null while ongoing) }
\- title and body are English. To translate, build your own text from service, state and country_name.

Cadence: responses are cached for 30 seconds. Poll no more than once every 30 seconds.

curl -fsS https://verification.didit.me/v3/status/

For end-to-end Didit integration, paste in the full prompt at /integration/integration-prompt.`

\</pre>



      
      

粘贴到

## 概览返回每项 Didit 服务的状态、整体状态，以及当前进行中的事件和过去 7 天内已解决的事件。
该端点为公开端点，请勿发送认证请求头。
响应不包含任何组织数据，对所有调用方都相同。## 适用场景- **状态组件**：向您的用户或支持团队展示某项 Didit 服务当前是否处于降级状态。
- **集成健康检查**：在怀疑是您自己的代码导致检查缓慢或失败之前，先查看 Didit 是否报告了您所调用服务的事件。
- **事件历史**：列出过去 7 天内发生的事件，以及每起事件持续的时长。如果只想确认 API 是否可以访问，请改用[健康检查](https://docs.didit.me/zh/api-reference/healthcheck.md)。## 轮询响应缓存 30 秒，因此轮询频率不要超过每 30 秒一次。
`updated_at` 表示 Didit 生成您所收到响应的时间。
同时适用 GET 速率限制：每个 IP 地址每分钟 600 次请求。## 服务`services` 列出所有服务，无论其是否有事件。
请按 `key` 匹配：`name` 是英文显示名称，可能会更改。| `key` | 服务 |
| - | - |
| `service_id_verification` | 身份证件验证 |
| `service_liveness_face_match` | 活体检测与人脸比对 |
| `service_aml_screening` | AML 筛查 |
| `service_kyb_registries` | KYB 企业登记库 |
| `service_database_validation` | 数据库核验 |
| `service_phone_delivery` | 电话验证投递 |
| `service_email_delivery` | 邮箱验证投递 |
| `service_transaction_monitoring` | 交易监控 |每项服务的 `status` 为 `operational`、`degraded` 或 `down`。
当服务没有进行中的事件时为 `operational`，否则为其进行中事件中最严重的状态。
顶层 `status` 为所有服务中最严重的状态。## 事件`incidents` 列出所有进行中的事件，以及过去 7 天内已解决的事件，按 `started_at` 从新到旧排列。
最多列出 50 个已解决的事件。- `state` 为 `degraded` 或 `down`。已解决的事件保留其最后的状态。
- `status` 在服务恢复之前为 `ongoing`，恢复后变为 `resolved`。
- 事件进行中时，`resolved_at` 和 `duration_minutes` 为 `null`。
- `affected` 和 `country_name` 说明受影响的国家或登记库，例如 `Brazil (CPF)` 和 `Brazil`。事件与某个国家或登记库无关时，这两个字段为空。
- `title` 和 `body` 为英文。若要以其他语言展示事件，请根据 `service`、`state` 和 `country_name` 自行生成文本。## 响应示例```json theme={null}
{
  "status": "degraded",
  "updated_at": "2026-10-13T09:41:07.512345Z",
  "services": [
    { "key": "service_id_verification", "name": "ID verification", "status": "operational" },
    { "key": "service_liveness_face_match", "name": "Liveness and face match", "status": "operational" },
    { "key": "service_aml_screening", "name": "AML screening", "status": "operational" },
    { "key": "service_kyb_registries", "name": "KYB registries", "status": "operational" },
    { "key": "service_database_validation", "name": "Database validation", "status": "degraded" },
    { "key": "service_phone_delivery", "name": "Phone verification delivery", "status": "operational" },
    { "key": "service_email_delivery", "name": "Email verification delivery", "status": "operational" },
    { "key": "service_transaction_monitoring", "name": "Transaction monitoring", "status": "operational" }
  ],
  "incidents": [
    {
      "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
      "service": "service_database_validation",
      "service_name": "Database validation",
      "state": "degraded",
      "status": "ongoing",
      "title": "Database validation is degraded in Brazil.",
      "body": "Checks against Brazil (CPF) may be slow or fail since 08:55 UTC.",
      "affected": "Brazil (CPF)",
      "country_name": "Brazil",
      "started_at": "2026-10-13T08:55:00Z",
      "resolved_at": null,
      "duration_minutes": null
    },
    {
      "id": "7c9e6679-7425-40de-944b-e07fc1f90ae7",
      "service": "service_aml_screening",
      "service_name": "AML screening",
      "state": "down",
      "status": "resolved",
      "title": "AML screening is back to normal.",
      "body": "Recovered at 14:32 UTC after 17 minutes.",
      "affected": "",
      "country_name": "",
      "started_at": "2026-10-11T14:15:00Z",
      "resolved_at": "2026-10-11T14:32:00Z",
      "duration_minutes": 17
    }
  ]
}
```## 相关内容- [健康检查](https://docs.didit.me/zh/api-reference/healthcheck.md)：公开的存活探测端点，同样无需认证请求头。
- [警报 Webhook](https://docs.didit.me/zh/integration/alert-webhooks.md)：针对您组织使用的服务，将 `alert.service.degraded` 和 `alert.service.recovered` 推送到您的端点。
- [速率限制](https://docs.didit.me/zh/integration/rate-limiting.md)


## OpenAPI

````yaml zh/openapi-25.json GET /v3/status/
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/status/:
    get:
      tags:
        - Status
      summary: 获取服务状态（公开，无需身份验证）
      description: >-
        返回每个 Didit 服务的状态（`operational`、`degraded` 或
        `down`）、整体状态（其中最差的状态），以及正在发生或在过去 7 天内已解决的突发事件。可用于为状态小组件提供数据支持，或在您的集成中检查
        Didit 的健康状态。


        公开：无需发送认证请求头。响应不包含任何组织数据，对所有调用方均相同。响应会缓存 30 秒，因此轮询频率请勿超过每 30 秒一次。
      operationId: get_v3_status
      parameters: []
      responses:
        '200':
          description: 当前服务状态。
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceStatusFeed'
              examples:
                One service degraded:
                  summary: 一起正在发生的突发事件以及一起本周已解决的突发事件
                  value:
                    status: degraded
                    updated_at: '2026-10-13T09:41:07.512345Z'
                    services:
                      - key: service_id_verification
                        name: ID verification
                        status: operational
                      - key: service_liveness_face_match
                        name: Liveness and face match
                        status: operational
                      - key: service_aml_screening
                        name: AML screening
                        status: operational
                      - key: service_kyb_registries
                        name: KYB registries
                        status: operational
                      - key: service_database_validation
                        name: Database validation
                        status: degraded
                      - key: service_phone_delivery
                        name: Phone verification delivery
                        status: operational
                      - key: service_email_delivery
                        name: Email verification delivery
                        status: operational
                      - key: service_transaction_monitoring
                        name: Transaction monitoring
                        status: operational
                    incidents:
                      - id: 3fa85f64-5717-4562-b3fc-2c963f66afa6
                        service: service_database_validation
                        service_name: Database validation
                        state: degraded
                        status: ongoing
                        title: Database validation is degraded in Brazil.
                        body: >-
                          Checks against Brazil (CPF) may be slow or fail since
                          08:55 UTC.
                        affected: Brazil (CPF)
                        country_name: Brazil
                        started_at: '2026-10-13T08:55:00Z'
                        resolved_at: null
                        duration_minutes: null
                      - id: 7c9e6679-7425-40de-944b-e07fc1f90ae7
                        service: service_aml_screening
                        service_name: AML screening
                        state: down
                        status: resolved
                        title: AML screening is back to normal.
                        body: Recovered at 14:32 UTC after 17 minutes.
                        affected: ''
                        country_name: ''
                        started_at: '2026-10-11T14:15:00Z'
                        resolved_at: '2026-10-11T14:32:00Z'
                        duration_minutes: 17
                All operational:
                  summary: 过去 7 天内没有事件
                  value:
                    status: operational
                    updated_at: '2026-10-13T09:41:07.512345Z'
                    services:
                      - key: service_id_verification
                        name: ID verification
                        status: operational
                      - key: service_liveness_face_match
                        name: Liveness and face match
                        status: operational
                      - key: service_aml_screening
                        name: AML screening
                        status: operational
                      - key: service_kyb_registries
                        name: KYB registries
                        status: operational
                      - key: service_database_validation
                        name: Database validation
                        status: operational
                      - key: service_phone_delivery
                        name: Phone verification delivery
                        status: operational
                      - key: service_email_delivery
                        name: Email verification delivery
                        status: operational
                      - key: service_transaction_monitoring
                        name: Transaction monitoring
                        status: operational
                    incidents: []
        '429':
          description: >-
            来自同一 IP 地址（或同一 API 密钥，如果您发送了密钥）的 GET 请求在一分钟内超过 600 次。重试前请遵循
            `Retry-After`。
          content:
            application/json:
              schema:
                type: object
                required:
                  - detail
                properties:
                  detail:
                    type: string
              example:
                detail: >-
                  GET request rate limit exceeded. You can make up to 600
                  requests per minute.
      security:
        - {}
      x-codeSamples:
        - lang: curl
          label: curl
          source: curl -fsS https://verification.didit.me/v3/status/
        - lang: python
          label: Python
          source: >-
            import requests


            resp = requests.get('https://verification.didit.me/v3/status/',
            timeout=5)

            resp.raise_for_status()

            feed = resp.json()

            print(feed['status'])

            for service in feed['services']:
                if service['status'] != 'operational':
                    print(service['key'], service['status'])
        - lang: javascript
          label: JavaScript
          source: >-
            const feed = await
            fetch('https://verification.didit.me/v3/status/').then((r) =>
            r.json());

            console.log(feed.status);

            const affected = feed.services.filter((s) => s.status !==
            'operational');

            console.log(affected.map((s) => `${s.key}: ${s.status}`));
components:
  schemas:
    ServiceStatusFeed:
      type: object
      description: 公开服务状态：各项 Didit 服务的状态、整体状态以及正在发生或在过去 7 天内已解决的事件。
      required:
        - status
        - updated_at
        - services
        - incidents
      properties:
        status:
          type: string
          enum:
            - operational
            - degraded
            - down
          description: 所有服务当前状态中的最差状态，仅由正在发生的事件决定。
          example: degraded
        updated_at:
          type: string
          format: date-time
          description: Didit 生成此响应的时间（ISO 8601，UTC）。响应会缓存 30 秒，因此可能最多有 30 秒的延迟。
          example: '2026-10-13T09:41:07.512345Z'
        services:
          type: array
          description: 每个服务对应一个条目，始终列出所有服务。
          items:
            $ref: '#/components/schemas/ServiceStatusService'
        incidents:
          type: array
          description: >-
            按 `started_at` 最新的优先排序。包括所有进行中的事件，加上过去 7 天内解决的事件（最多 50
            个已解决事件）。若在此期间无事件发生则为空。
          items:
            $ref: '#/components/schemas/ServiceStatusIncident'
    ServiceStatusService:
      type: object
      required:
        - key
        - name
        - status
      properties:
        key:
          type: string
          enum:
            - service_id_verification
            - service_liveness_face_match
            - service_aml_screening
            - service_kyb_registries
            - service_database_validation
            - service_phone_delivery
            - service_email_delivery
            - service_transaction_monitoring
          description: >-
            稳定的服务密钥。请基于此键进行匹配，切勿基于显示名称。`service_id_verification`：身份证件验证，`service_liveness_face_match`：活体检测与人脸比对，`service_aml_screening`：AML
            筛查，`service_kyb_registries`：KYB
            注册机构，`service_database_validation`：数据库核验，`service_phone_delivery`：电话验证投递，`service_email_delivery`：邮箱验证投递，`service_transaction_monitoring`：交易监控。
          example: service_database_validation
        name:
          type: string
          description: 服务的英文显示名称。
          example: Database validation
        status:
          type: string
          enum:
            - operational
            - degraded
            - down
          description: 当该服务没有正在发生的事件时为 `operational`，否则为其正在发生事件中最严重的状态。
          example: degraded
    ServiceStatusIncident:
      type: object
      required:
        - id
        - service
        - service_name
        - state
        - status
        - title
        - body
        - affected
        - country_name
        - started_at
        - resolved_at
        - duration_minutes
      properties:
        id:
          type: string
          format: uuid
          description: 事件 ID。
          example: 3fa85f64-5717-4562-b3fc-2c963f66afa6
        service:
          type: string
          enum:
            - service_id_verification
            - service_liveness_face_match
            - service_aml_screening
            - service_kyb_registries
            - service_database_validation
            - service_phone_delivery
            - service_email_delivery
            - service_transaction_monitoring
          description: 受影响服务的键（参见 `services[].key`）。
          example: service_database_validation
        service_name:
          type: string
          description: 受影响服务的英文显示名称。
          example: Database validation
        state:
          type: string
          enum:
            - degraded
            - down
          description: 服务受影响的方式。已解决的事件会保留其最后所处的状态。
          example: degraded
        status:
          type: string
          enum:
            - ongoing
            - resolved
          description: 在服务恢复前为 `ongoing`，恢复后为 `resolved`。
          example: ongoing
        title:
          type: string
          description: 英文标题。如需翻译，请根据 `service`、`state` 和 `country_name` 构建您自己的文本。
          example: Database validation is degraded in Brazil.
        body:
          type: string
          description: 英文详情说明行：自何时起核验可能会变慢或失败，或者何时已恢复。
          example: Checks against Brazil (CPF) may be slow or fail since 08:55 UTC.
        affected:
          type: string
          description: 受影响的国家/地区或登记机构，例如 `Brazil (CPF)`。当事件未与特定国家/地区或登记机构关联时为空。
          example: Brazil (CPF)
        country_name:
          type: string
          description: 受影响的国家/地区，以英文表示。当事件未与特定国家/地区关联时为空。
          example: Brazil
        started_at:
          type: string
          format: date-time
          description: 事件开始时间（ISO 8601，UTC）。
          example: '2026-10-13T08:55:00Z'
        resolved_at:
          type: string
          format: date-time
          nullable: true
          description: 服务恢复时间（ISO 8601，UTC）。事件持续期间为 `null`。
        duration_minutes:
          type: integer
          nullable: true
          description: 从 `started_at` 到 `resolved_at` 的整分钟数。事件仍在持续时为 `null`。

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.