Alerts Schema

Alerts Schema

We strictly maintain a structural blueprint for all incoming alert types to ensure downstream interfaces operate flawlessly.

Base Definition

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "title": "AlaskaIntel Alert Feed",
  "type": "object",
  "properties": {
    "updated_at": {
      "type": "string",
      "format": "date-time"
    },
    "alerts_count": {
      "type": "integer",
      "minimum": 0
    },
    "data": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "id": { "type": "string" },
          "category": { "type": "string", "enum": ["WEATHER", "EMERGENCY", "LAW_ENFORCEMENT"] },
          "severity": { "type": "string", "enum": ["INFO", "WATCH", "WARNING", "CRITICAL", "SEVERE"] },
          "title": { "type": "string" },
          "description": { "type": "string" },
          "timestamp": { "type": "string", "format": "date-time" }
        },
        "required": ["id", "category", "severity", "title", "timestamp"]
      }
    }
  },
  "required": ["updated_at", "alerts_count", "data"]
}

By conforming to this model, independent systems natively integrating AlaskaIntel pipelines do not require constant edge-case parsing mechanics.