Skip to content

API Reference Overview

The Wajub REST API — base URL, authentication, conventions and resource list.

The Wajub API is organized around REST: predictable URLs, JSON bodies, standard HTTP codes and key-based authentication. A single base URL serves both environments.

Built-in Playground

Configure your API keys in the top bar, then use the Test this endpoint button on each resource page to send real requests from the documentation.

Base URL

https://api.wajub.com

All requests must use HTTPS. HTTP requests are redirected.

Quick authentication

Authorization: sk_test.2a7c5e91b0d34f68
  • Authorization — your API key. Use a private key (sk.… / sk_test.…) for server-side operations (transfers, refunds, balance reads), a public key (pk.… / pk_test.…) for client-side operations, or a restricted key (rk.… / rk_test.…) scoped to specific resources.

See Authentication for full details.

Response structure

All API responses share a consistent JSON envelope:

Success (200)
{
"status": "OK",
"message": "The transaction has been fetched",
"code": 200,
"transaction": { /* resource data */ }
}
Error (422)
{
"status": "Unprocessable Content",
"message": "Some fields are invalid",
"code": 422,
"errors": {
  "amount": ["The amount must be at least 100."]
}
}

See Response structure for the full format.

Conventions

TopicDescription
AuthenticationPublic, private, and restricted keys
ErrorsHTTP codes and errors field structure
Failure ReasonsComplete catalog of reason codes
Paginationper_page / page / cursor parameters
Rate limitsQuotas and X-RateLimit-* headers
IdempotencyReplay requests without double-charging
VersioningDate-based API versions

Resources

ResourceKey endpoints
PaymentsPOST /payments, GET /payments/{id}
RefundsPOST /refunds
TransfersPOST /transfers, GET /transfers/{id}
CustomersPOST /customers, GET /customers/{id}
SubaccountsPOST /accounts
BalanceGET /balance
EventsGET /events
BeneficiariesPOST /beneficiaries
Webhook EndpointsPOST /webhook-endpoints
Payment LinksPOST /links
InvoicesPOST /invoices
DisputesGET /disputes

Testing the API

Was this page helpful?