Wallet free signup retired
0xArchive API reference for Wallet free signup retired. Includes authentication, parameters, response shape, examples, and route-safe implementation notes.
Headers
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/coverageand/v1/symbolsanswer 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
*_msfield: L4 resting-ordertimestamp(timestamp_ms), CVD buckets, HIP-3 oracle reads, Lighter and Lighter on Robinhood Chain liquidations and liquidation volume. Levels and trigger-levelssnapshot_tsbecome RFC 3339 withsnapshot_ts_ms. - Error bodies carry the contract
error_codenames:invalid_parameterinstead ofinvalid_query_paramsandinvalid_path_params,historical_depth_exceededinstead ofhistory_window_exceeded, andhistorical_range_exceededinstead ofrequest_range_exceeded; a malformed cursor that fails to parse answers 400invalid_cursorinstead ofinvalid_query_params. With0xArchive-Version: 2026-10-01, malformed cursors on trades, liquidations, L2 and L4 diffs, order history, TP/SL and order-flow routes answer 400invalid_cursor. Without the header, the first six route families treat a malformed cursor as no cursor and return the first page; order flow answers 400invalid_query_params. Malformed trade time inputs answer 400invalid_time_rangewith the header and 400invalid_query_paramswithout it.
The response echoes the selected version in its own 0xArchive-Version header.
2026-10-01 "2026-10-01"
Response
Wallet-only Free signup is retired.
Body of every non-2xx JSON response. code repeats the HTTP status, error_code is the stable machine-readable code (see ErrorCode), error is a human-readable message, and request_id identifies the request for support. Validation failures add param and, where the accepted set is fixed, valid_values. A 404 for a datatype the venue does not offer (unsupported_for_venue) adds venue, datatype and available_on; any other unknown path answers 404 route_not_found.
Stable, machine-readable error code. Branch on this value, not on the error text.
Contract codes
WebSocket only (sent in {"type":"error"} messages, never by REST)
Route-specific codes
Legacy names. Requests without 0xArchive-Version: 2026-10-01 keep the four names that predate the contract; with the header they receive the contract names instead.
Treat any value not listed here as a generic error of the HTTP status.
invalid_parameter, invalid_symbol, invalid_interval, invalid_cursor, invalid_time_range, range_before_coverage, historical_range_exceeded, historical_depth_exceeded, unsupported_for_venue, route_not_found, not_found, unauthorized, forbidden, insufficient_credits, rate_limited, conflict, upstream_unavailable, internal_error, endpoint_unsupported, slow_consumer, positions_unavailable, reconstruction_unavailable, snapshot_advanced, pagination_unavailable, api_key_limit_reached, wallet_requires_plan, wallet_account_required, wallet_free_signup_retired, account_disabled, oauth_not_permitted, insufficient_scope, invalid_query_params, invalid_path_params, history_window_exceeded, request_range_exceeded "invalid_parameter"