Skip to main content
GET
Get incident
API key required. Send X-API-Key with this request. See REST authentication.
Operation schema
Open the generated operation schema for machine-readable request and response details.

Authorizations

X-API-Key
string
header
required

API key for authentication. Get yours at https://0xarchive.io/dashboard

Headers

0xArchive-Version
enum<string>

Selects the 2026-10 response contract. Send 2026-10-01; any dated version on or after it selects the same shapes. Without the header every response keeps its existing shape. With it:

  • The data quality routes, /v1/status/coverage and /v1/symbols answer the standard {success, data, meta} envelope.
  • Record times that are integer milliseconds by default become RFC 3339 UTC strings with millisecond precision, and the integer moves to a *_ms field: L4 resting-order timestamp (timestamp_ms), CVD buckets, HIP-3 oracle reads, Lighter and Lighter on Robinhood Chain liquidations and liquidation volume. Levels and trigger-levels snapshot_ts become RFC 3339 with snapshot_ts_ms.
  • Error bodies carry the contract error_code names: invalid_parameter instead of invalid_query_params and invalid_path_params, historical_depth_exceeded instead of history_window_exceeded, and historical_range_exceeded instead of request_range_exceeded; a malformed cursor that fails to parse answers 400 invalid_cursor instead of invalid_query_params. With 0xArchive-Version: 2026-10-01, malformed cursors on trades, liquidations, L2 and L4 diffs, order history, TP/SL and order-flow routes answer 400 invalid_cursor. Without the header, the first six route families treat a malformed cursor as no cursor and return the first page; order flow answers 400 invalid_query_params. Malformed trade time inputs answer 400 invalid_time_range with the header and 400 invalid_query_params without it.

The response echoes the selected version in its own 0xArchive-Version header.

Available options:
2026-10-01
Example:

"2026-10-01"

Path Parameters

id
string
required

Incident ID

Response

Incident details

Without 0xArchive-Version: the route's own object plus success and meta.request_id.

success
enum<boolean>
required
Available options:
true
meta
object
required
id
string

Unique incident ID

status
enum<string>
Available options:
open,
investigating,
identified,
monitoring,
resolved
severity
enum<string>
Available options:
minor,
major,
critical
exchange
string | null

Affected exchange

data_types
string[]

Affected data types

symbols_affected
string[]

Affected symbols

started_at
string<date-time>
resolved_at
string<date-time> | null
duration_minutes
integer | null
title
string
description
string | null
root_cause
string | null
resolution
string | null
records_affected
integer<int64> | null
records_recovered
integer<int64> | null
Last modified on October 7, 2026