> ## Documentation Index
> Fetch the complete documentation index at: https://docs.0xarchive.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Get system status JSON Schema

> Get system status JSON Schema contract. Includes route metadata, request parameters, response statuses, examples, and JSON fields for implementation.

Source OpenAPI: 0xArchive API 1.5.0; 140 paths; 119 component schemas.

Get overall system health status including per venue-family and per-data-type status.

## Route Metadata

| Field                | Value                     |
| -------------------- | ------------------------- |
| Method               | `GET`                     |
| Path                 | `/v1/data-quality/status` |
| operationId          | `getDataQualityStatus`    |
| Tag                  | Data Quality              |
| Family               | Data Quality              |
| Deprecated or legacy | no                        |

## Response Contracts

### Status 200

System status

#### application/json

```json theme={"theme":"github-dark"}
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "getDataQualityStatus response 200",
  "description": "Overall system status",
  "type": "object",
  "properties": {
    "active_incidents": {
      "description": "Number of active incidents",
      "type": "integer"
    },
    "data_types": {
      "description": "Per-data-type status",
      "type": "object",
      "additionalProperties": {
        "description": "Status of a data type",
        "type": "object",
        "properties": {
          "completeness_24h": {
            "description": "Data completeness over last 24 hours (0-100)",
            "type": "number"
          },
          "status": {
            "type": "string",
            "enum": [
              "operational",
              "degraded",
              "outage",
              "maintenance"
            ]
          }
        }
      }
    },
    "exchanges": {
      "description": "Per venue-family status entries. The response field remains named `exchanges` in the API contract.",
      "type": "object",
      "additionalProperties": {
        "description": "Status for one supported venue-family key.",
        "type": "object",
        "properties": {
          "last_data_at": {
            "description": "Timestamp of last received data",
            "type": "string",
            "format": "date-time",
            "nullable": true
          },
          "latency_ms": {
            "description": "Current latency in milliseconds",
            "type": "integer",
            "nullable": true
          },
          "status": {
            "type": "string",
            "enum": [
              "operational",
              "degraded",
              "outage",
              "maintenance"
            ]
          }
        }
      }
    },
    "status": {
      "description": "Overall system status",
      "type": "string",
      "enum": [
        "operational",
        "degraded",
        "outage",
        "maintenance"
      ]
    },
    "updated_at": {
      "description": "When this status was computed",
      "type": "string",
      "format": "date-time"
    }
  }
}
```

### Status 401

Authentication required

#### application/json

```json theme={"theme":"github-dark"}
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "getDataQualityStatus response 401",
  "description": "Error response",
  "type": "object",
  "properties": {
    "code": {
      "description": "HTTP status code",
      "type": "integer"
    },
    "error": {
      "description": "Error message",
      "type": "string"
    }
  }
}
```

##### OpenAPI example

```json theme={"theme":"github-dark"}
{
  "code": 401,
  "error": "Missing or invalid API key. Provide X-API-Key header."
}
```