Endpoints API
Tous les services sont accessibles via l'orchestrator qui sert de point d'entree unique.
Routage
Client → https://<env>.paywithnex.com/api/* → Orchestrator → Service cibleL'orchestrator route les requetes vers le bon service en fonction du path :
| Path | Service cible |
|---|---|
/api/auth/register | orchestrator (workflow multi-service) |
/api/auth/* | auth |
/api/config/* | configuration |
/api/* (catch-all) | orchestrator |
Health checks
Via orchestrator
| Endpoint | Description |
|---|---|
GET /api/health | Health check de l'orchestrator |
Directs par service (staging/review)
Chaque service expose un health check sur /hz/<service> :
GET https://staging.paywithnex.com/hz/auth
GET https://staging.paywithnex.com/hz/orchestrator
GET https://staging.paywithnex.com/hz/ledger-wallets
...Authentification
Les endpoints proteges necessitent un header Authorization: Bearer <token>.
Le token est un Firebase custom token obtenu via le flow d'authentification :
POST /api/auth/login
Body: { phone, pin }
Response: { token, refreshToken }Devises supportees
- XAF — Franc CFA CEMAC
- XOF — Franc CFA UEMOA