API key authentication
Send your key in the x-api-key header on every request. JWT browser sessions still work in parallel for web clients.
The same backend used by the web application is available over HTTP. Create an API key from your profile and authenticate server-to-server requests with the x-api-key header.
https://www.cargacell.com/api/v1Send your key in the x-api-key header on every request. JWT browser sessions still work in parallel for web clients.
All paths are relative to the base URL above.
x-api-key authentication.Validate the key and read or update the current account profile.
| Method | Path | Description | Tags |
|---|---|---|---|
| POST | /auth/login | Email and password login | |
| GET | /auth/me | Get current authenticated user | |
| PATCH | /auth/me | Update profile and billing data |
Browse operators and products, then build orders before checkout.
| Method | Path | Description | Tags |
|---|---|---|---|
| GET | /catalog/countries | List available countries | |
| GET | /catalog/operators | List available operators | |
| GET | /catalog/recharge-products | Recharge catalog with filters | |
| GET | /cart | Get current cart | |
| POST | /cart/items | Add a cart item | |
| DELETE | /cart/items/:itemId | Remove a cart item |
Price and dispatch recharges using wallet balance. External checkout is web-session-only.
| Method | Path | Description | Tags |
|---|---|---|---|
| POST | /payments/quote | Get a price quote | |
| POST | /payments/prepare | Validate web checkout inputs | Web only |
| POST | /payments/checkout | Complete external web checkout | Web only |
| GET | /payments/history | Payment history | |
| GET | /wallet/balance | Current wallet balance | |
| POST | /wallet/checkout | Dispatch recharges funded by wallet | |
| POST | /api-access/b2b/recharges | B2B dedicated wallet-funded recharge | B2B |
Admin accounts can use the same API-key mechanism for all back-office endpoints.
| Method | Path | Description | Tags |
|---|---|---|---|
| GET | /admin/summary | Dashboard summary | Admin |
| GET | /admin/users | User management | Admin |
| GET | /admin/recharges | Recharge operations | Admin |
| GET | /admin/payments | Payment operations | Admin |
| GET | /admin/products | Catalog operations | Admin |
Live examples mirroring the current backend behavior. Toggle between Request and Response in each card.
Send a GET request to confirm authentication is working and inspect the account the key belongs to.
Fetch the recharge catalog. Products with active or scheduled promotions include full promo details (name, description, optional terms).
Push a recipient line into the cart. Fetch the product catalog first to resolve a valid productId.
Dedicated B2B endpoint — skips MONEI entirely and dispatches immediately from approved wallet balance.
Standard wallet-funded checkout — works with both API keys and web sessions.
Admin API keys can call back-office endpoints using the same x-api-key header.
Three dispatch paths exist. Choose the one that fits your integration.
External payment checkout
Web onlyThe browser initiates a MONEI payment via POST /payments/prepare, then confirms after authorization via POST /payments/checkout. Requires a JWT web session. API keys are rejected.
Wallet checkout
Call POST /wallet/checkout with your items. The backend computes available balance from approved top-ups minus captured wallet payments and rejects if insufficient. Works with both API keys and web sessions.
B2B wallet recharge
B2BCall POST /api-access/b2b/recharges. Uses the same wallet engine as path 2, but is purpose-built for API-key clients that must never interact with the MONEI flow. Dispatches immediately when balance is sufficient.
In all wallet-funded paths, successful payment creates queued recharge rows. Those are dispatched by the recharge processor, or marked as waitlisted when a DT One promo window applies.
All key operations are available in Dashboard → Profile.
Create
Create a named key for each integration or environment. The plaintext value is shown only once at creation time — copy it immediately.
Restrict
Add IP whitelist entries to lock a key to fixed infrastructure — office gateways, worker servers, or cloud function egress IPs.
Revoke
Revoke compromised or unused keys immediately. Revocation takes effect instantly. Never reuse old keys — generate a fresh one instead.