Skip to content
Loading keys…
Authorization<token>

A public key (pk./pk_test.) is accepted on /payments, /customers, /links, /invoices and the catalogue reads (/channels, /providers, /countries, /currencies); anything that moves money out, reads the balance or manages the account answers 406 to it. It is an identifier, never an authorization. Use a secret key (sk./sk_test.) for sensitive operations (transfers, refunds, balance), or a restricted key (rk./rk_test.) scoped to specific permissions. The _test. variant of any key selects the sandbox environment, there is no separate sandbox URL. Never expose your secret key in client-side code.

In: header

Query Parameters

per_pageinteger | null

Max results per page.

pageinteger

The page to read, from 1, for offset pagination. Ignored with `cursor`.

cursorstring | null

The `next_cursor` of a previous response, a numbered page included: switches the list to cursor pagination.

searchstring | null

Search over the URL and description.

Response Body

application/json

application/json

curl -X GET "https://api.wajub.com/webhooks?per_page=10&page=2"
GET
/webhooks
{  "code": 200,  "status": "OK",  "message": "Webhook endpoints retrieved",  "items": [    {      "id": "9d4e7a2c-3b1f-4c8e-a6d5-2f8b7c1e0a94",      "url": "https://example.com/webhooks/wajub",      "description": "Order updates",      "events": [        "payment.succeeded",        "payment.failed",        "refund.succeeded"      ],      "status": "enabled",      "active": true,      "sandbox": false,      "created_at": "2026-08-01T12:00:00+00:00",      "updated_at": "2026-08-01T12:00:00+00:00"    }  ],  "meta": {    "current_page": 1,    "last_page": 1,    "per_page": 25,    "total": 1,    "next_cursor": null,    "has_more": false  }}

OK

What did you think of this content?