Endpoints
Payment endpoints require authentication with your X-Public-Key and X-Secret-Key headers. Health endpoints are public and need no API keys.
Payments
| Method | Endpoint | Description | GET | /api/v1/auth/test | Test API keys | POST | /api/v1/payments/create | Create payment | GET | /api/v1/payments/:id | Get status | DELETE | /api/v1/payments/:id | Cancel payment |
|---|
Health
No authentication required.
| Method | Endpoint | Description |
|---|---|---|
| GET | /health | Full health check, including the database. Returns 200, or 503 when the database check fails. |
| GET | /health/live | Liveness check. Returns 200 with {"status": "ok"}. |
| GET | /health/ready | Readiness check. Returns 200 with {"status": "ready"}, or 503 with {"status": "not_ready"} when the database is unreachable. |
GET /health response
json
{"status": "ok","timestamp": "2026-09-16T14:32:07.512Z","version": "1.0.0","checks": {"database": {"status": "ok","latencyMs": 3}}}
When the database check fails, /health returns HTTP 503 with status set to unhealthy:
json
{"status": "unhealthy","timestamp": "2026-09-16T14:32:07.512Z","version": "1.0.0","checks": {"database": {"status": "unhealthy","error": "Database connection failed"}}}