Enterprise webhooks
An enterprise workspace can register up to 10 HTTPS endpoints per mode: 10 webhooks per mode, Sandbox and Live. When something happens in the workspace (a deal is created, a milestone is released, a payout settles), RekberPay sends a signed POST with the event as JSON to every endpoint of that mode subscribed to it.
Sandbox and Live endpoints
An endpoint belongs to the mode it was added in, and livemode on every event it receives is the endpoint's mode: a Live endpoint only gets live events (livemode: true), a Sandbox endpoint only test events (livemode: false). Point production at a Live endpoint and staging at a Sandbox one. Every route below acts on the endpoints of the request mode (the key's mode, or X-Enterprise-Mode for a session), and an endpoint of the other mode answers 404 NOT_FOUND, its deliveries included.
Enterprise only
Webhooks belong to an enterprise workspace. Consumer escrows and Jasa Pembayaran orders do not send webhooks; poll GET /v1/escrows/:id/payment-status and GET /v1/jasabayar/:id/payment-status instead.
All routes are under https://api.rekberpay.com/v1/enterprise. Every member can read webhooks and their delivery log, with a workspace API key or from the dashboard. Changing them (add, edit, pause, resume, test, rotate the secret, delete, send again) needs an admin's dashboard session: API keys get 403 KEY_NOT_ALLOWED on every webhook write, so a leaked key cannot point your events at another URL or read a new secret. A webhook ID from another workspace answers 404 NOT_FOUND. For a receiver you can copy, see Receiving webhooks.
Endpoints
| Method | Path | Endpoint | Auth |
|---|---|---|---|
GET | /v1/enterprise/webhooks | List webhooks | viewer |
POST | /v1/enterprise/webhooks | Add a webhook | admin, dashboard only |
PATCH | /v1/enterprise/webhooks/:id | Update, pause or resume a webhook | admin, dashboard only |
DELETE | /v1/enterprise/webhooks/:id | Delete a webhook | admin, dashboard only |
POST | /v1/enterprise/webhooks/:id/rotate-secret | Rotate the signing secret | admin, dashboard only |
POST | /v1/enterprise/webhooks/:id/test | Send a test event | admin, dashboard only |
GET | /v1/enterprise/webhooks/:id/deliveries | List deliveries | viewer |
POST | /v1/enterprise/webhooks/:id/deliveries/:did/redeliver | Send a delivery again | admin, dashboard only |
List webhooks
Every webhook of the request mode, oldest first, each with livemode, the endpoint's mode. The secret is never returned; secret_fingerprint is the first 8 hex characters of sha256(secret) so you can check which secret you hold.
- Auth: A workspace API key (
Authorization: Bearer rpe_...), a personal API key or a dashboard session. - Role: Any workspace member (
viewerand up). - Rate limit: 60 webhook calls a minute per user, plus the shared 300 a minute.
- Idempotency: Not needed. Reading has no side effects.
Example request
curl https://api.rekberpay.com/v1/enterprise/webhooks \
-H "Authorization: Bearer $REKBERPAY_WORKSPACE_KEY"const res = await fetch('https://api.rekberpay.com/v1/enterprise/webhooks', {
headers: {
Authorization: `Bearer ${process.env.REKBERPAY_WORKSPACE_KEY}`,
},
});
const data = await res.json();import os
import requests
resp = requests.get(
"https://api.rekberpay.com/v1/enterprise/webhooks",
headers={
"Authorization": f"Bearer {os.environ['REKBERPAY_WORKSPACE_KEY']}",
},
timeout=30,
)
print(resp.status_code, resp.json())<?php
$ch = curl_init('https://api.rekberpay.com/v1/enterprise/webhooks');
curl_setopt_array($ch, [
CURLOPT_RETURNTRANSFER => true,
CURLOPT_HTTPHEADER => [
'Authorization: Bearer ' . getenv('REKBERPAY_WORKSPACE_KEY'),
],
]);
$response = json_decode(curl_exec($ch), true);
$status = curl_getinfo($ch, CURLINFO_RESPONSE_CODE);
curl_close($ch);Example response
200 OK
{
"success": true,
"data": [
{
"id": "7777777a-7777-4777-8777-777777777777",
"url": "https://example.com/rekberpay/webhooks",
"description": "ERP sync",
"events": [
"deal.created",
"disbursement.settled",
"milestone.released"
],
"status": "active",
"paused_reason": null,
"secret_fingerprint": "3fa1c09b",
"failure_count": 0,
"last_delivery_at": null,
"last_delivery_status": null,
"last_response_code": null,
"created_at": "2026-10-13T14:33:16.731Z",
"updated_at": "2026-10-13T14:33:16.731Z",
"livemode": false
}
]
}Errors
| Status | Code | Cause |
|---|---|---|
401 | UNAUTHORIZED, SESSION_EXPIRED, INVALID_TOKEN | No session or key, the session expired, or the key is wrong or revoked |
400 | INVALID_ACCOUNT | X-Enterprise-Account is not a UUID |
403 | NO_WORKSPACE | You are not an active member of that workspace, or the key belongs to another one |
429 | RATE_LIMITED | Over the rate limit. Wait for Retry-After seconds |
Add a webhook
Registers an endpoint and answers once with its signing secret (whsec_ and 43 characters). Store it now; RekberPay shows only the fingerprint afterwards.
The URL must be https://, without a user name or password, on port 443, 8443 or another port from 1024 up (well known service ports are refused), and its host must resolve only to public addresses. localhost, *.local, *.internal and private, loopback or link-local addresses are refused.
- Auth: Dashboard session only. API keys, workspace or personal, get
403 KEY_NOT_ALLOWED. - Role:
adminorowner. - Rate limit: 60 webhook calls a minute per user, plus the shared 300 a minute.
- Idempotency: Not supported on purpose: a new secret is never replayed. A retry adds a second webhook, so after a timeout list the webhooks before you try again.
Body (JSON)
| Name | Type | Required | Description |
|---|---|---|---|
url | string | Yes | The HTTPS endpoint, at most 500 characters |
events | string[] | Yes | 1 to 64 event names, or ["*"] for every event, including ones added later |
description | string | null | No | At most 200 characters |
Example request
curl -X POST https://api.rekberpay.com/v1/enterprise/webhooks \
-b cookies.txt \
-H "X-CSRF-Token: $CSRF_TOKEN" \
-H "X-Enterprise-Account: $WORKSPACE_ID" \
-H "Content-Type: application/json" \
-d '{
"url": "https://example.com/rekberpay/webhooks",
"events": [
"milestone.released",
"disbursement.settled",
"deal.created"
],
"description": "ERP sync"
}'const res = await fetch('https://api.rekberpay.com/v1/enterprise/webhooks', {
method: 'POST',
headers: {
Cookie: process.env.REKBERPAY_SESSION_COOKIE, // '__Host-rekber_session=...' from POST /v1/auth/login
'X-CSRF-Token': process.env.REKBERPAY_CSRF_TOKEN,
'X-Enterprise-Account': process.env.WORKSPACE_ID,
'Content-Type': 'application/json',
},
body: JSON.stringify({
url: "https://example.com/rekberpay/webhooks",
events: [
"milestone.released",
"disbursement.settled",
"deal.created"
],
description: "ERP sync"
}),
});
const data = await res.json();import os
import requests
session = requests.Session()
# The session cookie from POST /v1/auth/login
session.cookies.set("__Host-rekber_session", os.environ["REKBERPAY_SESSION"], domain="api.rekberpay.com")
resp = session.post(
"https://api.rekberpay.com/v1/enterprise/webhooks",
headers={
"X-CSRF-Token": os.environ["REKBERPAY_CSRF_TOKEN"],
"X-Enterprise-Account": os.environ["WORKSPACE_ID"],
},
json={
"url": "https://example.com/rekberpay/webhooks",
"events": [
"milestone.released",
"disbursement.settled",
"deal.created",
],
"description": "ERP sync",
},
timeout=30,
)
print(resp.status_code, resp.json())<?php
$ch = curl_init('https://api.rekberpay.com/v1/enterprise/webhooks');
curl_setopt_array($ch, [
CURLOPT_CUSTOMREQUEST => 'POST',
CURLOPT_RETURNTRANSFER => true,
CURLOPT_COOKIEJAR => 'cookies.txt',
CURLOPT_COOKIEFILE => 'cookies.txt',
CURLOPT_HTTPHEADER => [
'X-CSRF-Token: ' . getenv('REKBERPAY_CSRF_TOKEN'),
'X-Enterprise-Account: ' . getenv('WORKSPACE_ID'),
'Content-Type: application/json',
],
CURLOPT_POSTFIELDS => json_encode([
'url' => 'https://example.com/rekberpay/webhooks',
'events' => [
'milestone.released',
'disbursement.settled',
'deal.created',
],
'description' => 'ERP sync',
]),
]);
$response = json_decode(curl_exec($ch), true);
$status = curl_getinfo($ch, CURLINFO_RESPONSE_CODE);
curl_close($ch);Example response
201 Created
{
"success": true,
"data": {
"id": "7777777a-7777-4777-8777-777777777777",
"url": "https://example.com/rekberpay/webhooks",
"description": "ERP sync",
"events": [
"deal.created",
"disbursement.settled",
"milestone.released"
],
"status": "active",
"paused_reason": null,
"secret_fingerprint": "3fa1c09b",
"failure_count": 0,
"last_delivery_at": null,
"last_delivery_status": null,
"last_response_code": null,
"created_at": "2026-10-13T14:33:16.731Z",
"updated_at": "2026-10-13T14:33:16.731Z",
"livemode": false,
"secret": "whsec_Xb4nR7tK2mQ9vL1sP6wZ3yH8cJ0dF5gA2eU7iO4kN1t"
}
}Errors
| Status | Code | Cause |
|---|---|---|
400 | INVALID_BODY | An unknown event, an unknown field or a missing URL |
400 | WEBHOOK_URL_INVALID_URL, WEBHOOK_URL_HTTPS_REQUIRED, WEBHOOK_URL_URL_CREDENTIALS, WEBHOOK_URL_PORT_NOT_ALLOWED, WEBHOOK_URL_HOST_DENIED, WEBHOOK_URL_PRIVATE_ADDRESS, WEBHOOK_URL_DNS_FAILED | The URL is not allowed. The message says why |
409 | WEBHOOK_LIMIT | The workspace already has 10 webhooks in this mode |
503 | SIGNING_NOT_CONFIGURED | Webhook signing is not available right now |
401 | UNAUTHORIZED, SESSION_EXPIRED, INVALID_TOKEN | No session or key, the session expired, or the key is wrong or revoked |
400 | INVALID_ACCOUNT | X-Enterprise-Account is not a UUID |
403 | NO_WORKSPACE | You are not an active member of that workspace, or the key belongs to another one |
403 | FORBIDDEN | Your role is below admin |
403 | KEY_NOT_ALLOWED | Called with an API key instead of a dashboard session |
403 | CSRF_FAILED | Session call without the matching X-CSRF-Token header |
429 | RATE_LIMITED | Over the rate limit. Wait for Retry-After seconds |
A real WEBHOOK_URL_HTTPS_REQUIRED answer:
400 Bad Request
{
"success": false,
"error": {
"code": "WEBHOOK_URL_HTTPS_REQUIRED",
"message": "The URL must start with https://."
}
}Update, pause or resume a webhook
Send any of the fields; an empty body answers 400 INVALID_BODY. status: "paused" stops deliveries: the ones already queued stay pending and wait, and events that happen while it is paused are not queued for it. status: "active" resumes it, resets the failure count and sends the queued deliveries shortly after. A new events list replaces the old one.
- Auth: Dashboard session only. API keys, workspace or personal, get
403 KEY_NOT_ALLOWED. - Role:
adminorowner. - Rate limit: 60 webhook calls a minute per user, plus the shared 300 a minute.
- Idempotency: Send an
Idempotency-Keyheader (UUID v4). A retry with the same key and body returns the first answer withIdempotent-Replay: true.
Path parameters
| Name | Type | Description |
|---|---|---|
id | UUID | The webhook ID |
Body (JSON)
| Name | Type | Required | Description |
|---|---|---|---|
url | string | No | A new HTTPS endpoint |
events | string[] | No | A new event list: 1 to 64 event names, or ["*"] |
description | string | null | No | null or an empty string clears it |
status | string | No | active or paused |
Example request
curl -X PATCH https://api.rekberpay.com/v1/enterprise/webhooks/7777777a-7777-4777-8777-777777777777 \
-b cookies.txt \
-H "X-CSRF-Token: $CSRF_TOKEN" \
-H "X-Enterprise-Account: $WORKSPACE_ID" \
-H "Idempotency-Key: ccccccca-cccc-4ccc-8ccc-cccccccccccc" \
-H "Content-Type: application/json" \
-d '{
"status": "paused"
}'const res = await fetch('https://api.rekberpay.com/v1/enterprise/webhooks/7777777a-7777-4777-8777-777777777777', {
method: 'PATCH',
headers: {
Cookie: process.env.REKBERPAY_SESSION_COOKIE, // '__Host-rekber_session=...' from POST /v1/auth/login
'X-CSRF-Token': process.env.REKBERPAY_CSRF_TOKEN,
'X-Enterprise-Account': process.env.WORKSPACE_ID,
'Content-Type': 'application/json',
'Idempotency-Key': 'ccccccca-cccc-4ccc-8ccc-cccccccccccc',
},
body: JSON.stringify({
status: "paused"
}),
});
const data = await res.json();import os
import requests
session = requests.Session()
# The session cookie from POST /v1/auth/login
session.cookies.set("__Host-rekber_session", os.environ["REKBERPAY_SESSION"], domain="api.rekberpay.com")
resp = session.patch(
"https://api.rekberpay.com/v1/enterprise/webhooks/7777777a-7777-4777-8777-777777777777",
headers={
"X-CSRF-Token": os.environ["REKBERPAY_CSRF_TOKEN"],
"X-Enterprise-Account": os.environ["WORKSPACE_ID"],
"Idempotency-Key": "ccccccca-cccc-4ccc-8ccc-cccccccccccc",
},
json={
"status": "paused",
},
timeout=30,
)
print(resp.status_code, resp.json())<?php
$ch = curl_init('https://api.rekberpay.com/v1/enterprise/webhooks/7777777a-7777-4777-8777-777777777777');
curl_setopt_array($ch, [
CURLOPT_CUSTOMREQUEST => 'PATCH',
CURLOPT_RETURNTRANSFER => true,
CURLOPT_COOKIEJAR => 'cookies.txt',
CURLOPT_COOKIEFILE => 'cookies.txt',
CURLOPT_HTTPHEADER => [
'X-CSRF-Token: ' . getenv('REKBERPAY_CSRF_TOKEN'),
'X-Enterprise-Account: ' . getenv('WORKSPACE_ID'),
'Content-Type: application/json',
'Idempotency-Key: ccccccca-cccc-4ccc-8ccc-cccccccccccc',
],
CURLOPT_POSTFIELDS => json_encode([
'status' => 'paused',
]),
]);
$response = json_decode(curl_exec($ch), true);
$status = curl_getinfo($ch, CURLINFO_RESPONSE_CODE);
curl_close($ch);Example response
200 OK
{
"success": true,
"data": {
"id": "7777777a-7777-4777-8777-777777777777",
"url": "https://example.com/rekberpay/webhooks",
"description": "ERP sync",
"events": [
"deal.created",
"disbursement.settled",
"milestone.released"
],
"status": "paused",
"paused_reason": "manual",
"secret_fingerprint": "3fa1c09b",
"failure_count": 0,
"last_delivery_at": null,
"last_delivery_status": null,
"last_response_code": null,
"created_at": "2026-10-13T14:33:16.731Z",
"updated_at": "2026-10-13T14:33:17.270Z",
"livemode": false
}
}Errors
| Status | Code | Cause |
|---|---|---|
400 | INVALID_BODY | An unknown field, or nothing to update |
400 | WEBHOOK_URL_* | The new URL is not allowed |
404 | NOT_FOUND | No such webhook in the request mode |
409 | CONCURRENT_MODIFICATION | The webhook changed while the call ran |
401 | UNAUTHORIZED, SESSION_EXPIRED, INVALID_TOKEN | No session or key, the session expired, or the key is wrong or revoked |
400 | INVALID_ACCOUNT | X-Enterprise-Account is not a UUID |
403 | NO_WORKSPACE | You are not an active member of that workspace, or the key belongs to another one |
403 | FORBIDDEN | Your role is below admin |
403 | KEY_NOT_ALLOWED | Called with an API key instead of a dashboard session |
403 | CSRF_FAILED | Session call without the matching X-CSRF-Token header |
429 | RATE_LIMITED | Over the rate limit. Wait for Retry-After seconds |
Delete a webhook
Deletes the webhook and its delivery log.
- Auth: Dashboard session only. API keys, workspace or personal, get
403 KEY_NOT_ALLOWED. - Role:
adminorowner. - Rate limit: 60 webhook calls a minute per user, plus the shared 300 a minute.
- Idempotency: Send an
Idempotency-Keyheader (UUID v4). A retry with the same key and body returns the first answer withIdempotent-Replay: true.
Path parameters
| Name | Type | Description |
|---|---|---|
id | UUID | The webhook ID |
Example request
curl -X DELETE https://api.rekberpay.com/v1/enterprise/webhooks/ddddddda-dddd-4ddd-8ddd-dddddddddddd \
-b cookies.txt \
-H "X-CSRF-Token: $CSRF_TOKEN" \
-H "X-Enterprise-Account: $WORKSPACE_ID" \
-H "Idempotency-Key: eeeeeeea-eeee-4eee-8eee-eeeeeeeeeeee"const res = await fetch('https://api.rekberpay.com/v1/enterprise/webhooks/ddddddda-dddd-4ddd-8ddd-dddddddddddd', {
method: 'DELETE',
headers: {
Cookie: process.env.REKBERPAY_SESSION_COOKIE, // '__Host-rekber_session=...' from POST /v1/auth/login
'X-CSRF-Token': process.env.REKBERPAY_CSRF_TOKEN,
'X-Enterprise-Account': process.env.WORKSPACE_ID,
'Idempotency-Key': 'eeeeeeea-eeee-4eee-8eee-eeeeeeeeeeee',
},
});
const data = await res.json();import os
import requests
session = requests.Session()
# The session cookie from POST /v1/auth/login
session.cookies.set("__Host-rekber_session", os.environ["REKBERPAY_SESSION"], domain="api.rekberpay.com")
resp = session.delete(
"https://api.rekberpay.com/v1/enterprise/webhooks/ddddddda-dddd-4ddd-8ddd-dddddddddddd",
headers={
"X-CSRF-Token": os.environ["REKBERPAY_CSRF_TOKEN"],
"X-Enterprise-Account": os.environ["WORKSPACE_ID"],
"Idempotency-Key": "eeeeeeea-eeee-4eee-8eee-eeeeeeeeeeee",
},
timeout=30,
)
print(resp.status_code, resp.json())<?php
$ch = curl_init('https://api.rekberpay.com/v1/enterprise/webhooks/ddddddda-dddd-4ddd-8ddd-dddddddddddd');
curl_setopt_array($ch, [
CURLOPT_CUSTOMREQUEST => 'DELETE',
CURLOPT_RETURNTRANSFER => true,
CURLOPT_COOKIEJAR => 'cookies.txt',
CURLOPT_COOKIEFILE => 'cookies.txt',
CURLOPT_HTTPHEADER => [
'X-CSRF-Token: ' . getenv('REKBERPAY_CSRF_TOKEN'),
'X-Enterprise-Account: ' . getenv('WORKSPACE_ID'),
'Idempotency-Key: eeeeeeea-eeee-4eee-8eee-eeeeeeeeeeee',
],
]);
$response = json_decode(curl_exec($ch), true);
$status = curl_getinfo($ch, CURLINFO_RESPONSE_CODE);
curl_close($ch);Example response
200 OK
{
"success": true,
"data": {
"id": "ddddddda-dddd-4ddd-8ddd-dddddddddddd",
"deleted": true
}
}Errors
| Status | Code | Cause |
|---|---|---|
404 | NOT_FOUND | No such webhook in the request mode |
401 | UNAUTHORIZED, SESSION_EXPIRED, INVALID_TOKEN | No session or key, the session expired, or the key is wrong or revoked |
400 | INVALID_ACCOUNT | X-Enterprise-Account is not a UUID |
403 | NO_WORKSPACE | You are not an active member of that workspace, or the key belongs to another one |
403 | FORBIDDEN | Your role is below admin |
403 | KEY_NOT_ALLOWED | Called with an API key instead of a dashboard session |
403 | CSRF_FAILED | Session call without the matching X-CSRF-Token header |
429 | RATE_LIMITED | Over the rate limit. Wait for Retry-After seconds |
Rotate the signing secret
Replaces the secret and answers once with the new one. It takes effect at once: every attempt after the rotation, including retries of older deliveries, is signed with the new secret.
- Auth: Dashboard session only. API keys, workspace or personal, get
403 KEY_NOT_ALLOWED. - Role:
adminorowner. - Rate limit: 60 webhook calls a minute per user, plus the shared 300 a minute.
- Idempotency: Not supported on purpose: a new secret is never replayed.
Path parameters
| Name | Type | Description |
|---|---|---|
id | UUID | The webhook ID |
Example request
curl -X POST https://api.rekberpay.com/v1/enterprise/webhooks/7777777a-7777-4777-8777-777777777777/rotate-secret \
-b cookies.txt \
-H "X-CSRF-Token: $CSRF_TOKEN" \
-H "X-Enterprise-Account: $WORKSPACE_ID" \
-H "Content-Type: application/json" \
-d '{}'const res = await fetch('https://api.rekberpay.com/v1/enterprise/webhooks/7777777a-7777-4777-8777-777777777777/rotate-secret', {
method: 'POST',
headers: {
Cookie: process.env.REKBERPAY_SESSION_COOKIE, // '__Host-rekber_session=...' from POST /v1/auth/login
'X-CSRF-Token': process.env.REKBERPAY_CSRF_TOKEN,
'X-Enterprise-Account': process.env.WORKSPACE_ID,
'Content-Type': 'application/json',
},
body: JSON.stringify({}),
});
const data = await res.json();import os
import requests
session = requests.Session()
# The session cookie from POST /v1/auth/login
session.cookies.set("__Host-rekber_session", os.environ["REKBERPAY_SESSION"], domain="api.rekberpay.com")
resp = session.post(
"https://api.rekberpay.com/v1/enterprise/webhooks/7777777a-7777-4777-8777-777777777777/rotate-secret",
headers={
"X-CSRF-Token": os.environ["REKBERPAY_CSRF_TOKEN"],
"X-Enterprise-Account": os.environ["WORKSPACE_ID"],
},
json={},
timeout=30,
)
print(resp.status_code, resp.json())<?php
$ch = curl_init('https://api.rekberpay.com/v1/enterprise/webhooks/7777777a-7777-4777-8777-777777777777/rotate-secret');
curl_setopt_array($ch, [
CURLOPT_CUSTOMREQUEST => 'POST',
CURLOPT_RETURNTRANSFER => true,
CURLOPT_COOKIEJAR => 'cookies.txt',
CURLOPT_COOKIEFILE => 'cookies.txt',
CURLOPT_HTTPHEADER => [
'X-CSRF-Token: ' . getenv('REKBERPAY_CSRF_TOKEN'),
'X-Enterprise-Account: ' . getenv('WORKSPACE_ID'),
'Content-Type: application/json',
],
CURLOPT_POSTFIELDS => json_encode(new stdClass()),
]);
$response = json_decode(curl_exec($ch), true);
$status = curl_getinfo($ch, CURLINFO_RESPONSE_CODE);
curl_close($ch);Example response
200 OK
{
"success": true,
"data": {
"id": "7777777a-7777-4777-8777-777777777777",
"url": "https://example.com/rekberpay/webhooks",
"description": "ERP sync",
"events": [
"deal.created",
"disbursement.settled",
"milestone.released"
],
"status": "active",
"paused_reason": null,
"secret_fingerprint": "3fa1c09b",
"failure_count": 0,
"last_delivery_at": null,
"last_delivery_status": null,
"last_response_code": null,
"created_at": "2026-10-13T14:33:16.731Z",
"updated_at": "2026-10-13T14:33:17.292Z",
"livemode": false,
"secret": "whsec_Xb4nR7tK2mQ9vL1sP6wZ3yH8cJ0dF5gA2eU7iO4kN1t"
}
}Errors
| Status | Code | Cause |
|---|---|---|
404 | NOT_FOUND | No such webhook in the request mode |
503 | SIGNING_NOT_CONFIGURED | Webhook signing is not available right now |
401 | UNAUTHORIZED, SESSION_EXPIRED, INVALID_TOKEN | No session or key, the session expired, or the key is wrong or revoked |
400 | INVALID_ACCOUNT | X-Enterprise-Account is not a UUID |
403 | NO_WORKSPACE | You are not an active member of that workspace, or the key belongs to another one |
403 | FORBIDDEN | Your role is below admin |
403 | KEY_NOT_ALLOWED | Called with an API key instead of a dashboard session |
403 | CSRF_FAILED | Session call without the matching X-CSRF-Token header |
429 | RATE_LIMITED | Over the rate limit. Wait for Retry-After seconds |
Send a test event
Queues a webhook.test delivery. It goes out within about 30 seconds; watch it in the delivery log.
- Auth: Dashboard session only. API keys, workspace or personal, get
403 KEY_NOT_ALLOWED. - Role:
adminorowner. - Rate limit: 60 webhook calls a minute per user, plus the shared 300 a minute.
- Idempotency: Send an
Idempotency-Keyheader (UUID v4). A retry with the same key and body returns the first answer withIdempotent-Replay: true.
Path parameters
| Name | Type | Description |
|---|---|---|
id | UUID | The webhook ID |
Example request
curl -X POST https://api.rekberpay.com/v1/enterprise/webhooks/7777777a-7777-4777-8777-777777777777/test \
-b cookies.txt \
-H "X-CSRF-Token: $CSRF_TOKEN" \
-H "X-Enterprise-Account: $WORKSPACE_ID" \
-H "Idempotency-Key: 8888888a-8888-4888-8888-888888888888" \
-H "Content-Type: application/json" \
-d '{}'const res = await fetch('https://api.rekberpay.com/v1/enterprise/webhooks/7777777a-7777-4777-8777-777777777777/test', {
method: 'POST',
headers: {
Cookie: process.env.REKBERPAY_SESSION_COOKIE, // '__Host-rekber_session=...' from POST /v1/auth/login
'X-CSRF-Token': process.env.REKBERPAY_CSRF_TOKEN,
'X-Enterprise-Account': process.env.WORKSPACE_ID,
'Content-Type': 'application/json',
'Idempotency-Key': '8888888a-8888-4888-8888-888888888888',
},
body: JSON.stringify({}),
});
const data = await res.json();import os
import requests
session = requests.Session()
# The session cookie from POST /v1/auth/login
session.cookies.set("__Host-rekber_session", os.environ["REKBERPAY_SESSION"], domain="api.rekberpay.com")
resp = session.post(
"https://api.rekberpay.com/v1/enterprise/webhooks/7777777a-7777-4777-8777-777777777777/test",
headers={
"X-CSRF-Token": os.environ["REKBERPAY_CSRF_TOKEN"],
"X-Enterprise-Account": os.environ["WORKSPACE_ID"],
"Idempotency-Key": "8888888a-8888-4888-8888-888888888888",
},
json={},
timeout=30,
)
print(resp.status_code, resp.json())<?php
$ch = curl_init('https://api.rekberpay.com/v1/enterprise/webhooks/7777777a-7777-4777-8777-777777777777/test');
curl_setopt_array($ch, [
CURLOPT_CUSTOMREQUEST => 'POST',
CURLOPT_RETURNTRANSFER => true,
CURLOPT_COOKIEJAR => 'cookies.txt',
CURLOPT_COOKIEFILE => 'cookies.txt',
CURLOPT_HTTPHEADER => [
'X-CSRF-Token: ' . getenv('REKBERPAY_CSRF_TOKEN'),
'X-Enterprise-Account: ' . getenv('WORKSPACE_ID'),
'Content-Type: application/json',
'Idempotency-Key: 8888888a-8888-4888-8888-888888888888',
],
CURLOPT_POSTFIELDS => json_encode(new stdClass()),
]);
$response = json_decode(curl_exec($ch), true);
$status = curl_getinfo($ch, CURLINFO_RESPONSE_CODE);
curl_close($ch);Example response
202 Accepted
{
"success": true,
"data": {
"delivery_id": "9999999a-9999-4999-8999-999999999999",
"status": "pending"
}
}Errors
| Status | Code | Cause |
|---|---|---|
404 | NOT_FOUND | No such webhook in the request mode |
409 | WEBHOOK_PAUSED | Resume the webhook first |
401 | UNAUTHORIZED, SESSION_EXPIRED, INVALID_TOKEN | No session or key, the session expired, or the key is wrong or revoked |
400 | INVALID_ACCOUNT | X-Enterprise-Account is not a UUID |
403 | NO_WORKSPACE | You are not an active member of that workspace, or the key belongs to another one |
403 | FORBIDDEN | Your role is below admin |
403 | KEY_NOT_ALLOWED | Called with an API key instead of a dashboard session |
403 | CSRF_FAILED | Session call without the matching X-CSRF-Token header |
429 | RATE_LIMITED | Over the rate limit. Wait for Retry-After seconds |
A real WEBHOOK_PAUSED answer:
409 Conflict
{
"success": false,
"error": {
"code": "WEBHOOK_PAUSED",
"message": "Resume this webhook before sending a test."
}
}List deliveries
The delivery log, newest first. response_body is the first 500 characters of your answer. Delivered rows are kept for 30 days and failed rows for 90 days. pagination.total counts at most 10,000 rows.
- Auth: A workspace API key (
Authorization: Bearer rpe_...), a personal API key or a dashboard session. - Role: Any workspace member (
viewerand up). - Rate limit: 60 webhook calls a minute per user, plus the shared 300 a minute.
- Idempotency: Not needed. Reading has no side effects.
Path parameters
| Name | Type | Description |
|---|---|---|
id | UUID | The webhook ID |
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
page | integer | No | Default 1 |
limit | integer | No | 1 to 50. Default 20 |
Example request
curl "https://api.rekberpay.com/v1/enterprise/webhooks/7777777a-7777-4777-8777-777777777777/deliveries?limit=5" \
-H "Authorization: Bearer $REKBERPAY_WORKSPACE_KEY"const res = await fetch('https://api.rekberpay.com/v1/enterprise/webhooks/7777777a-7777-4777-8777-777777777777/deliveries?limit=5', {
headers: {
Authorization: `Bearer ${process.env.REKBERPAY_WORKSPACE_KEY}`,
},
});
const data = await res.json();import os
import requests
resp = requests.get(
"https://api.rekberpay.com/v1/enterprise/webhooks/7777777a-7777-4777-8777-777777777777/deliveries?limit=5",
headers={
"Authorization": f"Bearer {os.environ['REKBERPAY_WORKSPACE_KEY']}",
},
timeout=30,
)
print(resp.status_code, resp.json())<?php
$ch = curl_init('https://api.rekberpay.com/v1/enterprise/webhooks/7777777a-7777-4777-8777-777777777777/deliveries?limit=5');
curl_setopt_array($ch, [
CURLOPT_RETURNTRANSFER => true,
CURLOPT_HTTPHEADER => [
'Authorization: Bearer ' . getenv('REKBERPAY_WORKSPACE_KEY'),
],
]);
$response = json_decode(curl_exec($ch), true);
$status = curl_getinfo($ch, CURLINFO_RESPONSE_CODE);
curl_close($ch);Example response
200 OK
{
"success": true,
"data": [
{
"id": "9999999a-9999-4999-8999-999999999999",
"event": "webhook.test",
"event_seq": null,
"status": "pending",
"attempts": 0,
"next_attempt_at": "2026-10-13T14:33:16.747Z",
"response_code": null,
"response_body": null,
"last_error": null,
"duration_ms": null,
"delivered_at": null,
"created_at": "2026-10-13T14:33:16.747Z"
}
],
"pagination": {
"page": 1,
"limit": 5,
"total": 1,
"total_pages": 1
}
}| Field | Type | Description |
|---|---|---|
event, event_seq | string, integer | null | The event and its seq in the event feed. null for webhook.test |
status | string | pending (waiting for its next attempt, or queued on a paused webhook), delivered or failed (out of retries, or the event can no longer be sent) |
attempts | integer | Attempts so far |
next_attempt_at | string | null | When the next attempt runs. Only for pending |
response_code | integer | null | Your HTTP status on the last attempt |
response_body | string | null | The first 500 characters of your answer |
last_error | string | null | Why the last attempt failed, for example a timeout or a URL that is no longer allowed |
duration_ms | integer | null | How long your server took to answer |
delivered_at | string | null | When your server accepted it |
Errors
| Status | Code | Cause |
|---|---|---|
404 | NOT_FOUND | No such webhook in the request mode |
401 | UNAUTHORIZED, SESSION_EXPIRED, INVALID_TOKEN | No session or key, the session expired, or the key is wrong or revoked |
400 | INVALID_ACCOUNT | X-Enterprise-Account is not a UUID |
403 | NO_WORKSPACE | You are not an active member of that workspace, or the key belongs to another one |
429 | RATE_LIMITED | Over the rate limit. Wait for Retry-After seconds |
Send a delivery again
Queues the same event again as a new delivery with a new delivery ID and a fresh signature. It works on a delivery that is delivered or failed. While any delivery of the same event to this webhook is still pending (the original or an earlier copy), it is still on its retry schedule, so this answers 409 DELIVERY_PENDING until that delivery finishes. The payload id stays the same, so your deduplication still works; a webhook.test sent again gets the new delivery ID as its id.
- Auth: Dashboard session only. API keys, workspace or personal, get
403 KEY_NOT_ALLOWED. - Role:
adminorowner. - Rate limit: 60 webhook calls a minute per user, plus the shared 300 a minute.
- Idempotency: Send an
Idempotency-Keyheader (UUID v4). A retry with the same key and body returns the first answer withIdempotent-Replay: true.
Path parameters
| Name | Type | Description |
|---|---|---|
id | UUID | The webhook ID |
did | UUID | The delivery ID |
Example request
curl -X POST https://api.rekberpay.com/v1/enterprise/webhooks/7777777a-7777-4777-8777-777777777777/deliveries/9999999a-9999-4999-8999-999999999999/redeliver \
-b cookies.txt \
-H "X-CSRF-Token: $CSRF_TOKEN" \
-H "X-Enterprise-Account: $WORKSPACE_ID" \
-H "Idempotency-Key: aaaaaaaa-aaaa-4aaa-8aaa-aaaaaaaaaaaa" \
-H "Content-Type: application/json" \
-d '{}'const res = await fetch('https://api.rekberpay.com/v1/enterprise/webhooks/7777777a-7777-4777-8777-777777777777/deliveries/9999999a-9999-4999-8999-999999999999/redeliver', {
method: 'POST',
headers: {
Cookie: process.env.REKBERPAY_SESSION_COOKIE, // '__Host-rekber_session=...' from POST /v1/auth/login
'X-CSRF-Token': process.env.REKBERPAY_CSRF_TOKEN,
'X-Enterprise-Account': process.env.WORKSPACE_ID,
'Content-Type': 'application/json',
'Idempotency-Key': 'aaaaaaaa-aaaa-4aaa-8aaa-aaaaaaaaaaaa',
},
body: JSON.stringify({}),
});
const data = await res.json();import os
import requests
session = requests.Session()
# The session cookie from POST /v1/auth/login
session.cookies.set("__Host-rekber_session", os.environ["REKBERPAY_SESSION"], domain="api.rekberpay.com")
resp = session.post(
"https://api.rekberpay.com/v1/enterprise/webhooks/7777777a-7777-4777-8777-777777777777/deliveries/9999999a-9999-4999-8999-999999999999/redeliver",
headers={
"X-CSRF-Token": os.environ["REKBERPAY_CSRF_TOKEN"],
"X-Enterprise-Account": os.environ["WORKSPACE_ID"],
"Idempotency-Key": "aaaaaaaa-aaaa-4aaa-8aaa-aaaaaaaaaaaa",
},
json={},
timeout=30,
)
print(resp.status_code, resp.json())<?php
$ch = curl_init('https://api.rekberpay.com/v1/enterprise/webhooks/7777777a-7777-4777-8777-777777777777/deliveries/9999999a-9999-4999-8999-999999999999/redeliver');
curl_setopt_array($ch, [
CURLOPT_CUSTOMREQUEST => 'POST',
CURLOPT_RETURNTRANSFER => true,
CURLOPT_COOKIEJAR => 'cookies.txt',
CURLOPT_COOKIEFILE => 'cookies.txt',
CURLOPT_HTTPHEADER => [
'X-CSRF-Token: ' . getenv('REKBERPAY_CSRF_TOKEN'),
'X-Enterprise-Account: ' . getenv('WORKSPACE_ID'),
'Content-Type: application/json',
'Idempotency-Key: aaaaaaaa-aaaa-4aaa-8aaa-aaaaaaaaaaaa',
],
CURLOPT_POSTFIELDS => json_encode(new stdClass()),
]);
$response = json_decode(curl_exec($ch), true);
$status = curl_getinfo($ch, CURLINFO_RESPONSE_CODE);
curl_close($ch);Example response
202 Accepted
{
"success": true,
"data": {
"delivery_id": "bbbbbbba-bbbb-4bbb-8bbb-bbbbbbbbbbbb",
"status": "pending"
}
}Errors
| Status | Code | Cause |
|---|---|---|
404 | NOT_FOUND | No such webhook or delivery in the request mode |
409 | WEBHOOK_PAUSED | Resume the webhook first |
409 | DELIVERY_PENDING | A delivery of this event is still being retried. Wait until it is delivered or failed, then send it again |
401 | UNAUTHORIZED, SESSION_EXPIRED, INVALID_TOKEN | No session or key, the session expired, or the key is wrong or revoked |
400 | INVALID_ACCOUNT | X-Enterprise-Account is not a UUID |
403 | NO_WORKSPACE | You are not an active member of that workspace, or the key belongs to another one |
403 | FORBIDDEN | Your role is below admin |
403 | KEY_NOT_ALLOWED | Called with an API key instead of a dashboard session |
403 | CSRF_FAILED | Session call without the matching X-CSRF-Token header |
429 | RATE_LIMITED | Over the rate limit. Wait for Retry-After seconds |
Delivery
Each delivery is one POST of the JSON payload:
| Header | Value |
|---|---|
Content-Type | application/json |
User-Agent | RekberPay-Webhooks/1.0 |
X-RekberPay-Event | The event name, for example milestone.released |
X-RekberPay-Delivery | Delivery ID. A redelivery has a new one |
X-RekberPay-Signature | t=<unix seconds>,v1=<hex HMAC-SHA256> |
- Any
2xxanswer within 10 seconds counts as delivered. Anything else (other status codes, redirects, timeouts, connection errors) is a failed attempt. Redirects are never followed. - Deliveries go out within about 30 seconds of the event. Order is not guaranteed; use
seqto order events. - Answer
2xxto events you do not know. A webhook subscribed to*also gets events added later, for exampledispute.evidence_addedand the Platform events, and a4xxor5xxfor one you do not handle counts as a failed attempt. Ignore keys you do not know in a payload too. - Delivery is at least once. The same event can arrive twice (a retry after your
2xxwas lost, or a manual send again). Deduplicate on the payloadid.
Retries
A failed attempt is retried after 10s, 20s, 30s, 45s and 60s, then 2m, 2m, 2.5m, 3m and 3m (about 15 minutes in all), then every hour until 24 hours after the first attempt: 34 attempts at most. Each delay has about 10% random jitter. After that the delivery is failed. A failed delivery stays in the event feed, and you can send any delivery again with Send a delivery again.
RekberPay pauses the webhook (status: "paused", paused_reason: "failures") only after 20 failed attempts in a row across all its deliveries whose failing streak began at least 1 hour earlier, and records a webhook.paused event. While the webhook is paused (by RekberPay or by hand), deliveries that were already queued stay pending; nothing is cancelled. Events that happen while it is paused are not queued for it, so read them from GET /v1/enterprise/events. Fix the endpoint, then resume it: that resets the failure count, and every queued delivery goes out shortly after.
Signature
v1 is HMAC-SHA256(secret, "<t>.<raw body>") in lowercase hex, computed over the exact bytes of the body. To verify:
- Split the header on
,and readtand everyv1. - Reject the request if
tis more than 5 minutes from your clock. - Compute the HMAC over
t, a., and the raw body as received (before any JSON parsing), with your webhook's secret. - Compare it with each
v1in constant time. Accept on a match.
This header was made by RekberPay's signer for the payload below (sent as one line of compact JSON, shown here formatted), with the sample secret whsec_Xb4nR7tK2mQ9vL1sP6wZ3yH8cJ0dF5gA2eU7iO4kN1t and t=1792128796:
X-RekberPay-Signature: t=1792128796,v1=b32f73e84e4ef9f166187ed3a39e736228484698d96ef402cba064a188772a28The Node.js verifier in Receiving webhooks verifies this header.
Payload
An example milestone.released event, as it is sent:
{
"id": "11111118-1111-4111-8111-111111111111",
"seq": 140544,
"event": "milestone.released",
"account_id": "fffffff2-ffff-4fff-8fff-ffffffffffff",
"entity_type": "milestone",
"entity_id": "fffffff4-ffff-4fff-8fff-ffffffffffff",
"deal_id": "eeeeeee4-eeee-4eee-8eee-eeeeeeeeeeee",
"amount": 30000000,
"summary": "Released DEAL-2026-0009 / Tooling and proof approval in 2 payouts",
"occurred_at": "2026-10-13T14:33:16.481Z",
"livemode": false,
"data": {
"previous": null,
"next": {
"status": "released"
}
}
}| Field | Type | Notes |
|---|---|---|
id | string | Event ID, the same on every retry and redelivery. Deduplicate on it. For webhook.test it is the delivery ID |
seq | integer | The same seq as GET /v1/enterprise/events. null for webhook.test |
event | string | Event name |
account_id | string | Workspace ID |
entity_type | string | deal, milestone, approval, disbursement, refund, payout_instruction, counterparty, counterparty_link, document, member, account, webhook, and in Platform mode platform_user, withdrawal, rating, message |
entity_id | string or null | ID of that entity |
deal_id | string or null | The deal the event belongs to, when there is one |
amount | number or null | Rupiah the event moved, when there is one |
summary | string | The same one-line text as the activity feed |
occurred_at | string | ISO 8601 time of the event |
livemode | boolean | The mode of the event, which is the mode of the endpoint that receives it: true for Live, false for Sandbox. Fixed when the event happens, the same on every retry. false also for webhook.test, and for events from before the mode switch about test data. In production, ignore events with livemode: false |
data.previous, data.next | object or null | State before and after. Bank account numbers appear only masked; hashes and secrets are never sent |
A production receiver should still drop any event with livemode: false before it changes anything: sandbox deals and payouts move test money only. Point a staging receiver at a Sandbox endpoint to see those events.
Treat the payload as a notification. When you need the full current state, read it from the API, for example GET /v1/enterprise/deals/:id.
Events
deal.created, deal.updated, deal.activated, deal.cancelled, deal.funded, deal.fee_proposed, deal.fee_agreed, milestone.added, milestone.updated, milestone.funded, milestone.evidence_submitted, milestone.revision_requested, milestone.approved, milestone.released, milestone.paid, milestone.shipped, milestone.received, milestone.release_pending, milestone.auto_released, milestone.auto_refunded, milestone.release_reversed, milestone.extended, approval.requested, approval.decided, dispute.opened, dispute.evidence_added, dispute.resolved, disbursement.queued, disbursement.requeued, disbursement.processing, disbursement.settled, disbursement.failed, payout_instruction.created, payout_instruction.updated, payout_instruction.deleted, payout_instruction.verified, payout_instruction.suspended, refund.queued, refund.requeued, refund.processing, refund.settled, refund.failed, counterparty.created, counterparty.updated, counterparty.kyb_updated, counterparty.link_requested, counterparty.linked, counterparty.link_declined, counterparty.unlinked, document.added, document.deleted, platform.user.linked, platform.user.consent_declined, platform.user.claimed, platform.user.unlinked, platform.user.kyc_updated, platform.user.balance_scope_changed, platform.user.deletion_requested, platform.user.deletion_cancelled, platform.user.deleted, bank_account.added, withdrawal.requested, withdrawal.settled, withdrawal.failed, withdrawal.returned, deposit.required, deposit.paid, deposit.applied, deposit.returned, rating.created, rating.published, rating.hidden, message.created, account.created, account.updated, settings.updated, member.added, member.invited, member.joined, member.removed, member.role_changed, webhook.paused.
The refund.* events track the money RekberPay sends back when a dispute cancels a funded milestone or a funded deal is cancelled; see Refund events.
The platform.user.*, withdrawal.*, deposit.* and rating.* events, message.created, bank_account.added, and milestone.paid, milestone.shipped, milestone.received, milestone.release_pending, milestone.auto_released, milestone.auto_refunded, milestone.release_reversed and milestone.extended are the 30 new events of Platform mode (PaaS). They come only from Platform activity, so a workspace that does not use Platform never receives them. Their payloads name users by partner_user_ref, never by a RekberPay user ID. When each one fires, and the fields of each payload: Platform webhook events.
deal.funded is sent once when a whole upfront deal is funded, whether by a payment RekberPay confirmed or with test money in Sandbox. amount is the funded total and data.next holds milestone_ids, funded_amount, funding_method and funding_reference. Each milestone it funded also gets its own milestone.funded event. A deal that is paid per milestone only sends milestone.funded. See Funding a deal upfront.
The deal room records more events in the activity feed of the paying workspace (preview.link_sent, preview.first_viewed, preview.reset, preview.revoked, requirement.added, requirement.met, requirement.removed, deal.cancel_requested, deal.cancel_declined, deal.cancel_withdrawn, deal.payee_payout_set, deal.lead_changed, counterparty.claimed, counterparty.claim_confirmed, counterparty.link_superseded, counterparty.link_invited and counterparty.link_invite_refused). They are not sent to webhooks. Poll List events to read them. Every feed-only event (notes, templates, API keys, business verification and more) is listed in Event names.
deal.fee_proposed and deal.fee_agreed belong to deals with a counterparty that has its own RekberPay workspace: one side proposes the fee split, the other accepts it, and the deal cannot be activated or funded in between. The counterparty.link_* events record linking a counterparty to that workspace, and counterparty.unlinked (sent to both workspaces) records ending the link. Active deals stay shared until they close; see Unlinking.
Refund events
A refund is the money RekberPay sends back to the paying workspace when it resolves a dispute by cancelling a milestone that was funded, or when a funded deal is cancelled (Refunds). The events use the same envelope, signature and delivery and retry rules as every other event, and go to the paying workspace only. The linked counterparty's workspace gets none.
entity_type is refund and entity_id is the refund ID, the same id as milestones[].refund.id in Get a deal. deal_id is the deal and amount is the whole refund: the milestone amount plus the buyer fee share. A dispute decision arrives first as dispute.resolved, with data.next of { status: "cancelled", outcome: "cancelled", note }; a deal cancel writes deal.cancelled right after its refund events, with data.next.refunds listing each refund.
| Event | Sent when | data.previous | data.next |
|---|---|---|---|
refund.queued | A live refund was created by a dispute decision or a deal cancel | null | status: "queued", milestone_id, principal_amount, fee_amount, is_test: false |
refund.processing | RekberPay started sending it | { status } | status: "processing", milestone_id |
refund.settled | It was sent | { status } | status: "settled", milestone_id, settlement_reference (the bank reference, or null) and destination |
refund.failed | The transfer failed | { status } | status: "failed", milestone_id, failure_reason |
refund.requeued | A failed refund was put back to be sent again | { status: "failed" } | status: "queued", milestone_id |
destination is where a settled refund went: { bank_name, account_last4 }, the workspace's verified bank account at that moment, with the last 4 digits only, or null when none could be read. It stays on the event even if the workspace changes its bank account later.
A refund of a sandbox deal, or of a live milestone that was funded with sandbox test money, moves no real money. It is created already settled and sends one event, refund.settled, with livemode: false, data.previous: null and data.next of { status: "settled", milestone_id, principal_amount, fee_amount, is_test: true }. Ignore it in production like every event with livemode: false.
A live refund is queued first:
{
"id": "7c1d4e92-3b58-4f06-a9d1-5e2b8a60f347",
"seq": 140701,
"event": "refund.queued",
"account_id": "44444444-4444-4444-8444-444444444444",
"entity_type": "refund",
"entity_id": "99999997-9999-4999-8999-999999999997",
"deal_id": "eeeeeee4-eeee-4eee-8eee-eeeeeeeeeeee",
"amount": 20400000,
"summary": "Refund to the payer queued for DEAL-2026-0009 / First 20,000 cartons",
"occurred_at": "2026-10-14T09:12:40.000Z",
"livemode": true,
"data": {
"previous": null,
"next": {
"status": "queued",
"milestone_id": "11111115-1111-4111-8111-111111111111",
"principal_amount": 20000000,
"fee_amount": 400000,
"is_test": false
}
}
}and later sent:
{
"id": "d03a76b1-52c8-4e19-8f40-a7b3c91e2d65",
"seq": 140755,
"event": "refund.settled",
"account_id": "44444444-4444-4444-8444-444444444444",
"entity_type": "refund",
"entity_id": "99999997-9999-4999-8999-999999999997",
"deal_id": "eeeeeee4-eeee-4eee-8eee-eeeeeeeeeeee",
"amount": 20400000,
"summary": "Refund to the payer settled (ref TRF-20261015-0042)",
"occurred_at": "2026-10-15T03:41:08.000Z",
"livemode": true,
"data": {
"previous": {
"status": "processing"
},
"next": {
"status": "settled",
"milestone_id": "11111115-1111-4111-8111-111111111111",
"settlement_reference": "TRF-20261015-0042",
"destination": {
"bank_name": "DBS Bank Indonesia",
"account_last4": "4321"
}
}
}
}Counterparty and fee events
These events belong to linked workspaces and the fee agreement. They use the same envelope, signature (X-RekberPay-Signature) and delivery and retry rules as every other event.
Link events. counterparty.link_requested, counterparty.linked, counterparty.link_declined and counterparty.unlinked are written to the log of both workspaces, so each workspace's own webhooks receive their own copy. The copy for the workspace that owns the counterparty row has entity_type: "counterparty" and the counterparty ID. The copy for the other workspace has entity_type: "counterparty_link" and the link ID. In data.next, workspace_id is always the other workspace, and link_id is the link.
| Event | Sent when | data.next (besides link_id and workspace_id) |
|---|---|---|
counterparty.link_requested | The paying workspace asks to link | None |
counterparty.linked | The asked workspace accepts | status: "accepted" on the asking workspace's copy |
counterparty.link_declined | The asked workspace declines | status: "declined" on the asking workspace's copy |
counterparty.unlinked | Either side ends an accepted link | See below |
counterparty.unlinked carries ended_by (owner when the paying workspace ended it, counterparty when the linked workspace did) and kept_shared, the number of deals that stay shared (active until they close, archived as a read-only record). The paying workspace's copy also has detached_drafts (how many draft deals were detached), detached_references (up to 20 deal references) and owner_buyer_percent (the default split those drafts went back to); its data.previous holds the old linked_account_id and link_id. The other workspace's copy has status: "unlinked" and a data.previous of { link_id, workspace_id, status: "accepted" }. Withdrawing a pending request records no event.
The paying workspace's copy:
{
"id": "2f6c1a52-7c9e-4d0f-8b38-5a1d9e0c7b41",
"seq": 140612,
"event": "counterparty.unlinked",
"account_id": "44444444-4444-4444-8444-444444444444",
"entity_type": "counterparty",
"entity_id": "eeeeeee3-eeee-4eee-8eee-eeeeeeeeeeee",
"deal_id": null,
"amount": null,
"summary": "Counterparty PT Pemasok Baja unlinked from its RekberPay workspace PT Pemasok Baja",
"occurred_at": "2026-10-19T08:21:40.000Z",
"livemode": true,
"data": {
"previous": {
"linked_account_id": "bbbbbbbb-bbbb-4bbb-8bbb-bbbbbbbbbbbb",
"link_id": "cccccccc-cccc-4ccc-8ccc-cccccccccccc"
},
"next": {
"linked_account_id": null,
"workspace_id": "bbbbbbbb-bbbb-4bbb-8bbb-bbbbbbbbbbbb",
"ended_by": "owner",
"kept_shared": {
"active": 2,
"archived": 5
},
"detached_drafts": 1,
"detached_references": [
"DEAL-2026-0051"
],
"owner_buyer_percent": 100
}
}
}The linked workspace's copy of the same event:
{
"id": "9a3e7b60-1d52-4f8c-a4e9-3c7d01b6f852",
"seq": 98211,
"event": "counterparty.unlinked",
"account_id": "bbbbbbbb-bbbb-4bbb-8bbb-bbbbbbbbbbbb",
"entity_type": "counterparty_link",
"entity_id": "cccccccc-cccc-4ccc-8ccc-cccccccccccc",
"deal_id": null,
"amount": null,
"summary": "PT Pembeli Jaya unlinked this workspace as its counterparty PT Pemasok Baja",
"occurred_at": "2026-10-19T08:21:40.000Z",
"livemode": true,
"data": {
"previous": {
"link_id": "cccccccc-cccc-4ccc-8ccc-cccccccccccc",
"workspace_id": "44444444-4444-4444-8444-444444444444",
"status": "accepted"
},
"next": {
"link_id": "cccccccc-cccc-4ccc-8ccc-cccccccccccc",
"workspace_id": "44444444-4444-4444-8444-444444444444",
"status": "unlinked",
"ended_by": "owner",
"kept_shared": {
"active": 2,
"archived": 5
}
}
}
}Fee events. deal.fee_proposed and deal.fee_agreed are written to the log, and so the webhooks, of the paying workspace only; the linked workspace reads them in the events of the shared deal. amount on deal.fee_proposed is the platform fee. data.next holds proposed_by (workspace or counterparty), buyer_percent (the paying workspace's share) and counterparty_workspace_id. When the linked workspace counters or accepts, the event also has data.previous (status, proposed_by and buyer_percent before) and data.next.status (proposed or agreed). deal.fee_agreed means both sides agreed; the deal can then be activated.
{
"id": "5b8d2c14-6e07-4a39-9d1f-0e4a7c3b2d68",
"seq": 140603,
"event": "deal.fee_proposed",
"account_id": "44444444-4444-4444-8444-444444444444",
"entity_type": "deal",
"entity_id": "eeeeeee4-eeee-4eee-8eee-eeeeeeeeeeee",
"deal_id": "eeeeeee4-eeee-4eee-8eee-eeeeeeeeeeee",
"amount": 1200000,
"summary": "Fee split proposed to the counterparty workspace: the workspace pays the whole fee",
"occurred_at": "2026-10-19T03:02:11.000Z",
"livemode": true,
"data": {
"previous": null,
"next": {
"proposed_by": "workspace",
"buyer_percent": 100,
"counterparty_workspace_id": "bbbbbbbb-bbbb-4bbb-8bbb-bbbbbbbbbbbb"
}
}
}webhook.test is only sent by Send a test event. Changes to the webhooks themselves (webhook.created, webhook.updated, webhook.deleted, webhook.secret_rotated) stay in the activity feed and are never sent to a webhook, even with ["*"].