Skip to main content
Status

API status

Check live whether the eldo wallet API responds, and how fast, in the test environment and in production.

Test environment

https://api-v2.test.eldowallet.fr
Checking…
Availability over 30 days—
  • 24 h —
  • 7 d —
  • 90 d —
Response time
—
24 h average
—
Last check
—
HTTP code
—

Production

https://api-v2.eldowallet.fr
Checking…
Availability over 30 days—
  • 24 h —
  • 7 d —
  • 90 d —
Response time
—
24 h average
—
Last check
—
HTTP code
—
Other serversDevelopment Checking…Staging Checking…

Development

https://api-v2.dev.eldowallet.fr
Checking…
Availability over 30 days—
  • 24 h —
  • 7 d —
  • 90 d —
Response time
—
24 h average
—
Last check
—
HTTP code
—

Staging

https://api-v2.beta.eldowallet.fr
Checking…
Availability over 30 days—
  • 24 h —
  • 7 d —
  • 90 d —
Response time
—
24 h average
—
Last check
—
HTTP code
—

Status and response time measured from your browser every minute, with GET /public/health (your own connection is included; above 1.5 s, the API is shown as slow). Availability is computed from one check per minute from our servers in France.

About these measurements​

  • The values shown are indicative and may not exactly reflect the actual availability of the API. They are not a service level agreement (SLA): only the commitments in your contract apply.
  • Planned maintenance is not distinguished from incidents: it counts like any other unavailability.
  • Availability is based on one check per minute from a single location in France: a shorter interruption may go undetected, and a network issue on our side may show up as unavailability.
  • The live response time is measured from your browser: it also depends on your connection and location.

Having trouble with your calls while the API is operational? See the error codes, or contact support.

API news, once a month

New endpoints, upcoming changes, guides and use cases. No spam, one-click unsubscribe.

Report a technical problem

An API error, a pass that does not update, an email that does not arrive? Describe the problem: our technical team will answer.

For a fast answer, include:

  • The method and endpoint (e.g. POST /clients)
  • The error code returned (errorCode) and the body sent
  • The date and time of the call
  • The identifiers involved (customer, template, pass)

Never include an API token or a password.

AI assistant

Beta

Loading…

AI-generated answers (Claude): double-check important details.

Sign in to use the assistant