Build with Project Aziz APIs

Create applications, integrations, and tools that help find missing persons faster. Access our suite of open APIs to build solutions that save lives.

Request Write Access View Documentation

Available APIs

All APIs are currently READ ONLY by default. Request write access below to create and modify data.

REST API

Standard HTTP-based API with JSON responses. Perfect for traditional web and mobile applications.

GET endpoints for cases, tips, and search parties
Pagination and filtering support
Rate limiting: 1000 requests/hour
API versioning (v1, v2)

WebSocket API

Real-time bidirectional communication. Get instant updates when cases are created or tips are submitted.

Live case updates and notifications
Subscribe to specific cases or geographic areas
Persistent connections for dashboards
Automatic reconnection handling

WebTransport & Field Units

Next-generation protocol built on HTTP/3 with real-time field technology notifications. Ultra-low latency for time-critical search operations.

Field Unit Notifications

Deploy mesh-networked field technology that receives live updates on new tips, case status changes, and search coordination events through WebTransport streams.

Millisecond-level latency for field device alerts
Strict JSON schema for embedded system parsing
Private case channels for authorized field units
Public alert channels for system-wide broadcasts
Multiplexed streams without head-of-line blocking
Battery and signal strength monitoring for edge devices
Perfect for IoT, mesh networks, and edge computing

MCP (Model Context Protocol)

AI-native protocol for large language models and AI agents to access Project Aziz data and capabilities.

AI-powered case analysis and insights
Natural language queries for complex searches
Integrate with Claude, ChatGPT, and custom AI agents
Semantic search across all case data

What You Can Build

Mobile Applications

Build iOS and Android apps that allow users to browse cases, receive alerts, and submit tips on the go.

Dashboards & Analytics

Create real-time dashboards for law enforcement or media to monitor active cases and tip trends.

AI Assistants

Develop AI-powered bots that help families manage cases, answer questions, and coordinate searches.

Integrations

Connect Project Aziz with social media platforms, news outlets, or existing law enforcement systems.

Field Unit Technology

Deploy custom field hardware that listens to WebSocket/WebTransport channels for real-time tip notifications, case status updates, and search coordination.

Visualization Tools

Create maps, timelines, and visual tools to help investigators and families track search efforts.

Field Unit Integration Guide

Notification Schema

All field unit notifications follow a strict, machine-readable JSON schema for reliable parsing on embedded systems:

{
  "event": "tip.received",
  "version": "1.0",
  "timestamp": "2026-05-20T14:30:00Z",
  "case_id": 42,
  "priority": "critical",
  "payload": { /* event-specific */ },
  "metadata": { /* context */ }
}

Event Types

tip.received— New tip submitted (critical if location included)
case.status_changed— Case status update (always critical)
search_party.updated— Search zone or participant change
system.field_alert— System-wide alert (weather, safety)
device.registered— Device enrollment confirmation

Channel Subscriptions

Field units subscribe to private or public channels based on authorization:

field-units.{caseId} — Case-specific updates
field-alerts — System-wide broadcasts
command-center.{caseId} — Command coordination
device-registry — Device pairing & config

Priority Handling

Embedded systems should process notifications by priority:

critical — Display immediately, bypass queue
high — Process within 2 updates
normal — Standard queue (~10s)
low — Background queue (~60s)

Device Registration Flow

1. Device calls POST /api/field-devices/register
2. Receives config with sync intervals & endpoints
3. Subscribes to assigned channels via WebSocket
4. Sends status updates via POST /api/field-devices/{id}/status

Offline Resilience

Field devices have tools to handle connectivity loss:

• Automatic reconnection with exponential backoff
• Local notification queue for offline periods
• History sync via /api/field-devices/{caseId}/notifications
• Battery level monitoring & alerts
• Signal strength tracking for mesh optimization

📖 Full Documentation

See docs/field-unit-notifications.md for complete schemas, examples, and best practices.

Request Write Access

All APIs are read-only by default. If you need to create or modify data (write access), fill out this form and we'll review your request.