Status

GET /v1/health tells you whether every service is up right now, how many of its sources answered and the uptime we measured. No API key needed and it doesn't count toward your quota.

Every 10 minutes we run one cheap request against each real source behind each endpoint (the forwarder panels and carriers for tracking, both QC warehouses, the marketplace and warehouse feeds for lookup, the shipping calculator) and store the result for 90 days. The status page shows the same data.

Request

request
curl "https://repsapi.pl/v1/health?days=7"

Response

200 · response
{
  "status": "operational",
  "checked_at": "2026-10-13T13:28:35.610Z",
  "services": {
    "api":      { "status": "operational", "latency_ms": 12,   "sources": { "up": 1, "total": 1 } },
    "tracking": { "status": "operational", "latency_ms": 1820, "sources": { "up": 7, "total": 7 } },
    "qc":       { "status": "operational", "latency_ms": 2017, "sources": { "up": 2, "total": 2 } },
    "lookup":   { "status": "operational", "latency_ms": 905,  "sources": { "up": 3, "total": 3 } },
    "convert":  { "status": "operational", "latency_ms": 0,    "sources": { "up": 1, "total": 1 } },
    "shipping": { "status": "operational", "latency_ms": 508,  "sources": { "up": 1, "total": 1 } }
  },
  "uptime_30d": { "api": 100, "tracking": 99.31, "qc": 100, "lookup": 99.86, "convert": 100 },
  "history": [
    { "date": "2026-10-13", "services": { "tracking": { "status": "operational", "uptime": 100 }, "…": "…" } },
    "…"
  ],
  "source": "repsapi.pl",
  "docs": "https://repsapi.pl/docs/status"
}

Fields

  • status - overall: operational, degraded (something is partly down) or down.
  • services.*.status - operational when every source answered, degraded when some did, down when none did.
  • services.*.sources - how many of the service's sources answered in the last check.
  • services.*.latency_ms - the slowest source in the last check.
  • uptime_30d - share of checks in the last 30 days where the service wasn't down, in %; null before the first check.
  • history - only with ?days=1…90: per-day status and uptime for each service.
  • services.shipping - the shipping calculator behind /v1/shipping/estimate and /v1/haul. It has been checked since 14 October 2026, so its uptime only covers checks from that day on.

Notes

  • The response is cached for 30 seconds; checking more often won't return anything newer.
  • When the API itself is down the endpoint answers 503, so plain HTTP uptime monitors notice.