APEXReference

Reference

The APEX API reference — base URL, authentication, price estimation and batch, corridors, the 18 analytics endpoints, errors, configuration, and known limitations.

The Reference lane is the APEX API specification. Shared conventions — the header format, the error envelope, rate-limit headers, and versioning — live once in API conventions; the pages here document APEX's specifics. For what the numbers mean, see APEX › Concepts.

Base URL

EnvironmentBase URL
Productionhttps://apex.tovr.eu/api/v1
Staginghttps://apex-staging.tovr.eu/api/v1

Every endpoint except GET /health and GET /openapi.yaml requires an X-API-Key header.

Endpoints at a glance

MethodPathPurpose
POST/estimateSingle lane price estimate
POST/estimate/batchUp to 500 lanes per call
GET/corridorsFull directed-corridor inventory
GET/analytics/*18 market-analytics endpoints
GET/healthLiveness check (no auth)
GET/openapi.yamlThe OpenAPI spec (no auth)

A small admin API (/admin/*, gated by a separate operator key) exists for issuing keys and triggering syncs; it is internal-only and not documented as a public interface.

The two confidence scores

APEX computes two different quality numbers that must not be conflated:

  • Estimate confidence — returned on every /estimate, from data volume + freshness scaled by the cascade level.
  • Corridor aggregate quality — a separate score (sample size, source diversity, price variance) computed during corridor aggregation and surfaced in analytics.

Both are explained side by side in Confidence & quality.

On this page