Conventions
How every KreedX API behaves — learn it once, and the second integration feels familiar.
KreedX APIs are RESTful, and every response — errors included — is JSON. The rules below hold across the whole catalogue.
| Topic | How it works |
|---|---|
| Style | REST over HTTPS, with predictable JSON responses |
| Environments | Sandbox and production, with separate credentials for each |
| Asynchronous events | Webhooks to an HTTPS endpoint you provide |
| Every transaction | Carries a unique reference ID, through to settlement |
| Failures | Retried where the network allows, then returned as a clear status rather than left pending |
| Tooling | SDK samples and code examples, shared during integration |
| Availability | Enterprise-grade uptime SLA |
Where to go from here
- Status & Error Codes — what a failure looks like, and what to retry.
- Webhooks & Transaction Status — how to learn a transaction's final result.

Translate