Developer/API Documentation

API Documentation

Complete reference for integrating Argus AI real-time traffic intelligence into your applications. RESTful endpoints, WebSocket streams, and comprehensive code examples.

Quick Start Guide View Endpoints

<10s

Detection Latency

<100ms

API Response Time

99.9%

Uptime SLA

Detection Types

What We Detect

Others detect the symptoms (jams, congestion). We detect the incident that causes them—and forecast the impact before it happens.

Incidents & Crashes

Congestion

Traffic Jams

Emergency Vehicles

Disabled Vehicles

First Responders

Traffic Stops

Construction

Pedestrians

Current Data Available

Real-time incident alerts (all 9 types)
Traffic flow data
Traffic volume counts
Aggregated multi-source intelligence

Predictive Flow

COMING SOON

Vision-based predictive traffic flow—anticipating conditions in 10-minute intervals, up to 90 minutes ahead.

No one else predicts because they don't see what's happening. We do.

Quick Start Guide

Get Your API Key

Contact our team to receive your API credentials. Keys are issued per organization with custom rate limits.

Request Access →

Subscribe to Events

See Webhook API →

Make Requests

Query incidents, traffic flow, or subscribe to real-time WebSocket alerts for your coverage area.

View Endpoints →

Your First API RequestcURL

curl -X GET "https://api.getargus.ai/v1/incidents" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "lat": 40.7128,
    "lng": -74.0060,
    "radius_km": 10,
    "types": ["accident", "congestion", "road_closure"]
  }'

Base URL

PRODUCTIONhttps://api.getargus.ai/v1

All API endpoints are relative to this base URL. The API uses HTTPS exclusively for all communications. HTTP requests will be redirected to HTTPS.

API Endpoints

POST/webhooks/subscribe

GET/webhooks/{id}

PATCH/webhooks/{id}

DELETE/webhooks/{id}

GET/webhooks

POST/webhooks/subscribe

Register a new webhook endpoint with preferences. Receive real-time traffic incident alerts pushed directly to your server with sub-10-second latency from detection.

Request Body

{
  "url": "https://customer.com/webhook/123",
  "events": [
    "event.crash",
    "event.disabled_vehicle",
    "event.first_responder",
    "event.construction"
  ],
  "preferences": {
    "geographic_location": {
      "country": "US",
      "region": "CA"
    }
  }
}

Parameters

Parameter	Type	Required	Description
`url`	string	Yes	HTTPS endpoint URL to receive webhooks
`events`	array	Yes	Array of event types to subscribe to
`preferences`	object	No	Geographic and other filtering preferences

Available Event Types

event.crash

Traffic accidents and crashes

event.construction

Construction and roadwork events

event.disabled_vehicle

Disabled or broken down vehicles

event.first_responder

Emergency responder activity

Response Example

201 Created

{
  "id": "wh_abc123",
  "url": "https://customer.com/webhook/123",
  "events": ["event.crash", "event.disabled_vehicle"],
  "preferences": {
    "geographic_location": {
      "country": "US",
      "region": "CA"
    }
  },
  "created_at": "2025-09-24T10:00:00Z",
  "status": "active"
}

Webhook Payload Schema

When an event occurs, Argus will send a POST request to your registered webhook URL with the following payload structure:

Webhook POST Payload

{
  "id": "del_abc123xyz",
  "event": "event.crash",
  "timestamp": "2025-11-07T14:32:15.234Z",
  "data": {
    "severity": "critical",
    "location": {
      "latitude": 47.6062,
      "longitude": -122.3321,
      "address": "I-405 Northbound, Mile 23.4",
      "city": "Seattle",
      "state": "WA",
      "country": "US",
      "road": "I-405",
      "direction": "Northbound"
    },
    "description": "Multi-vehicle collision blocking two lanes",
    "lanes_affected": 2,
    "estimated_duration_minutes": 45
  },
  "metadata": {
    "source": "traffic_camera_ai",
    "confidence_score": 0.94
  }
}

Payload Fields

Field	Type	Description
`id`	string	Unique delivery ID for this webhook notification
`event`	string	Event type (event.crash, event.construction, event.disabled_vehicle, event.first_responder)
`timestamp`	string	ISO 8601 timestamp when the event was detected
`data`	object	Event-specific data including location, severity, and details (structure varies by event type)
`metadata`	object	Optional metadata including AI confidence scores and data sources

HTTP Headers

Each webhook request includes these custom headers:

Content-Type: application/json
User-Agent: WebhookDelivery/1.0
X-Webhook-Event: event.crash
X-Webhook-ID: del_abc123xyz
X-Webhook-Timestamp: 2025-11-07T14:32:15.234Z

Response Requirements

Respond with HTTP 200-299 status code to acknowledge successful receipt
Response must be returned within 30 seconds
Failed deliveries are automatically retried up to 3 times with exponential backoff
Your webhook endpoint must use HTTPS

GET/webhooks/{id}

Retrieve details about a specific webhook subscription by ID.

PATCH/webhooks/{id}

Update an existing webhook subscription. Modify the URL, events, or preferences.

DELETE/webhooks/{id}

Delete a webhook subscription. You will no longer receive events at the registered URL.

GET/webhooks

List all webhook subscriptions for your account.

Error Handling

The API uses conventional HTTP status codes and returns detailed error messages in JSON format. All errors include a unique error code for debugging.

Status Code	Error Code	Description
400	`invalid_request`	Missing or invalid parameters
401	`unauthorized`	Invalid or missing API key
403	`forbidden`	API key lacks required permissions
404	`not_found`	Resource not found
429	`rate_limited`	Rate limit exceeded
500	`server_error`	Internal server error

Error Response Format

{
  "success": false,
  "error": {
    "code": "invalid_request",
    "message": "Parameter 'lat' must be between -90 and 90",
    "details": {
      "field": "lat",
      "value": 95.5,
      "constraint": "range(-90, 90)"
    },
    "request_id": "req_xyz123abc"
  }
}

API FAQ

What is the API response time?

The Argus AI API typically responds in under 100ms for most queries. Incident data is available within 10 seconds of detection, making it the fastest traffic intelligence API available for navigation and routing applications.

What geographic coverage does the API provide?

Argus AI currently covers major metropolitan areas and interstate highways across the United States. Coverage includes real-time data from traffic cameras, telematics partners, 911/PSAP systems, and roadway sensors. Contact us for specific regional availability.

How does Argus AI achieve sub-10-second latency?

Our AI video inference processes traffic camera and dashcam feeds in real-time, detecting incidents within seconds of occurrence. Combined with direct 911/PSAP integrations and telematics partnerships, we eliminate the delays inherent in crowdsourced or GPS-only solutions.

Can I access historical incident data?

Yes. The /v1/incidents/history endpoint provides access to historical incident data for analytics, forensics, route planning optimization, and insurance use cases. Historical data includes all incident metadata, timestamps, duration, and source attribution.

What data sources feed the API?

Argus AI aggregates five distinct data sources: 911/PSAP dispatch systems, commercial telematics networks, public roadway sensors, AI-powered traffic camera analysis, and dashcam video inference. Each incident includes source attribution so you know the data origin and confidence level.

Do you offer enterprise SLAs?

Enterprise plans include 99.9% uptime SLA, dedicated support, custom rate limits, priority WebSocket connections, and optional dedicated infrastructure. Contact our team to discuss enterprise requirements and custom integrations.

Ready to Integrate?

Get API access and start building with real-time traffic intelligence. Our team is ready to help you integrate comprehensive traffic data into your navigation application.

Request API Access Explore Data Sources