Delete a webhook destination

DELETE 
/partner/webhook/:id

Stops deliveries to a destination. Shared by both integrations — it works the same for BNPL and real-estate destinations.

The destination is deactivated, not erased. It keeps appearing in GET /partner/webhook with isActive: false, and its URL, secret and subscriptions are preserved. What changes is that it stops receiving events and stops counting toward your limit of 10 active destinations. Deleting a destination that is already inactive also answers 200.

Because the URL stays registered, posting it again does not create a new destination or a new secret:

• POST /partner/webhook/subscription reactivates it, with its original token, and answers 200 without the token.
• POST /partner/webhook refuses it with 409.

To get a new secret, register a different URL.

Request

Responses

200

Destination deactivated

400

Bad Request - The bearer token is validly signed but is not your current partner API token.

401

Unauthorized - Invalid, expired or missing bearer token

403

Forbidden - The destination does not belong to you, no destination has this id, or the partner is inactive. All three answer the same way, with only the status in the body, so the endpoint cannot be used to discover which ids exist.

422

Unprocessable Entity (ERR_INVALID_UUID_ID) - The id is not 36 characters long. This is checked before ownership, so a malformed id returns this rather than the 403 above. Only the length is checked here: send the id exactly as GET /partner/webhook returns it.

429

Too Many Requests - Rate limit exceeded. The body is the text You have reached maximum retries in this timespan., not JSON.