Production availability, latency distribution and source-data freshness are measured separately so developers can understand both API responsiveness and auction-data recency.
Source-data freshness, not HTTP latency.
Approximate for supported live auction workflows.
A fast API response does not guarantee fresh source data, and an invalid API key does not mean the service is down. Apibara reports these dimensions separately so integrations can interpret them correctly.
Search workloads vary. A direct VIN lookup is not the same workload as a broad inventory query with filters, location constraints and pagination. Percentiles expose this distribution better than one average response time.
Server-side failure and relevant to production availability.
Authentication, validation, subscription or quota responses. The API is still responding correctly.
{
"server_failure": "5xx",
"client_4xx_is_downtime": false,
"freshness_is_latency": false
}Source freshness describes how recently supported Copart or IAAI records were collected or changed. HTTP latency measures how quickly the API serves a request. These answer different questions.
Continue from API cursors instead of rebuilding the full catalog.
Process changed or recently updated inventory rather than everything.
Use platform, VIN, lot, make, model, dates and locations intentionally.
Avoid repeatedly requesting metadata that rarely changes.
Performance is aggregated from production /api/v1/vehicle-auction/*
request logs. Server-side 5xx responses are treated as service failures; client 4xx responses are not counted as server downtime.
Freshness remains a separate measurement from request latency.
No. They are client, authorization, validation or quota responses. Server-side 5xx responses are the primary failure class for production availability.
They describe response-time distribution. p50 is around the median, while p95 and p99 expose slower tail requests.
No. Latency measures how long a request takes. Freshness measures how recently auction data changed in the dataset.
Yes. Use /status.json and /performance.json.