API Reference

Receive Forwarded CDR

wbhk
CDR Forwarding

Plugsurfing sends Charging Detail Records (CDRs) when you are set to clear the sessions. If a request does not receive a 200 response (or times out), Plugsurfing retries nightly for up to 7 days using the same requestId for idempotency.

Payload
string
required

Unique identifier for the webhook delivery. The same requestId is reused on retries.

date-time
required

Webhook creation timestamp in UTC.

payer
required
string
enum
required
Allowed:
item
object
required
Headers
string

Base64 encoded HMAC SHA-512 signature of the raw request body. Present when HMAC signing is configured.

date-time

RFC 3339 timestamp for when the payload was signed. Present when HMAC signing is configured.

Responses
200

CDR accepted.

400

Invalid CDR payload.

403

Authorization failed.

500

Receiver failed to process the CDR.

Updated about 1 month ago

Payload
Choose an example

Updated about 1 month ago