Skip to main content
Use these routes to check whether a Lumeus API is up and its data is current, for example in a status page or before a batch job. All four API hosts (Activity, Assets, Webhooks and RPC) serve them on both networks, without authentication and without charge.
Output
Readiness is cached for five seconds. Liveness can stay healthy while readiness fails.

What “current” means

Every host requires a healthy Stellar RPC node whose latest ledger closed within the last 90 seconds. Each API then adds its own check: Webhooks readiness does not check your receiver. If callbacks stop arriving, inspect the subscription’s deliveries and coverage.

When readiness fails

Back off for Retry-After and keep your saved pagination state. Do not replace missing data with an empty successful result. After an outage, ingestion resumes from where it stopped and publishes ledgers in order, so catch-up can take a while. Keep your saved generation and cursor unless the API reports a generation change (409 generation_changed).