Environments
| Environment | Use | Base URL |
|---|---|---|
| Test | Default, to develop and test your integration | https://api-v2.test.eldowallet.fr |
| Production | Going live, real customers | https://api-v2.eldowallet.fr |
Both environments expose the same API. Every example in this documentation, the "Try it" button of the API reference and the SDK target the test environment.
The API has no prefix and no version segment: https://api-v2.test.eldowallet.fr/clients, not /api/v2/clients.
Tokens are specific to each environment: a test token is rejected in production, and vice versa.
Ready for production?
Is your integration working in test? The next step happens with our team: they open your production wallet, walk you through the plan that fits your volumes and use cases, and support you until launch.
Before going live
Your launch checklist, to review with our team when your access is opened:
- Use dummy data in test (
@example.com, fake phone numbers). Passes sent by email or SMS are actually delivered. - Respect the rate limit: 1,000 requests per minute. Beyond a few hundred sends, use bulk operations.
- Monitor the API's availability from your own monitoring.
- Set up webhooks to track installations.
Switching to production
Once your production access is open:
- Switch the base URL to
https://api-v2.eldowallet.fr. - Use a token from your production wallet, created with POST
/wallets/tokensand stored outside your code.
Keep the base URL and the token in configuration (environment variables), never hard-coded.