Skip to main content
PUT
Replace webhook subscription
Use this endpoint to point an existing subscription at a different destination_url – for example, when you migrate to a new server or change your webhook handler path. The event type itself is identified by the path and cannot be changed; unsubscribe and create a new subscription if you need a different event type.
Replacing a subscription does not rotate the signature_key. Your existing key remains valid and continues to sign every delivery for this event type. To issue a new signing key, use Rotate Signature Key.

Authorizations

Authorization
string
header
required

Your Tilta API key, sent as Bearer <key>.

Path Parameters

type
enum<string>
required

The webhook's type. Supports the hierarchical dot-notation taxonomy; subscribing to a parent (e.g. FACILITY) implicitly subscribes to every descendant event (e.g. FACILITY.CREATION.ACCEPTED). Other valid values include ORDER.CONFIRMED and INVOICE.DUE.

Available options:
BUYER,
BUYER.CREATED,
BUYER.UPDATED,
FACILITY,
FACILITY.CREATION,
FACILITY.CREATION.ACCEPTED,
FACILITY.CREATION.IN_REVIEW,
FACILITY.CREATION.REJECTED,
FACILITY.EXPIRED,
FACILITY.FROZEN,
FACILITY.INCREASE,
FACILITY.INCREASE.ACCEPTED,
FACILITY.INCREASE.IN_REVIEW,
FACILITY.INCREASE.REJECTED,
FACILITY.RENEWAL,
FACILITY.RENEWAL.ACCEPTED,
FACILITY.RENEWAL.IN_REVIEW,
FACILITY.RENEWAL.REJECTED,
FACILITY.UNFROZEN,
INVOICE,
INVOICE.CLOSED,
INVOICE.CREATED,
INVOICE.DUE,
INVOICE.FILE,
INVOICE.FILE.CREATED,
INVOICE.FILE.DELETED,
INVOICE.FILE.REPLACED,
INVOICE.FINANCING,
INVOICE.FINANCING.PAID_OUT,
ORDER,
ORDER.CANCELLED,
ORDER.CLOSED,
ORDER.CONFIRMED,
ORDER.DISBURSED,
ORDER.EXPIRED
Example:

"FACILITY.CREATION.ACCEPTED"

Body

application/json
destination_url
string<uri>
required

Where the webhook should be sent to. This must be an endpoint that handles POST requests.

Response

destination_url
string<uri>
required

Where the webhook should be sent to. This must be an endpoint that handles POST requests.

type
enum<string>
required

The webhook's type. Supports the hierarchical dot-notation taxonomy; subscribing to a parent (e.g. FACILITY) implicitly subscribes to every descendant event (e.g. FACILITY.CREATION.ACCEPTED). Other valid values include ORDER.CONFIRMED and INVOICE.DUE.

Available options:
BUYER,
BUYER.CREATED,
BUYER.UPDATED,
FACILITY,
FACILITY.CREATION,
FACILITY.CREATION.ACCEPTED,
FACILITY.CREATION.IN_REVIEW,
FACILITY.CREATION.REJECTED,
FACILITY.EXPIRED,
FACILITY.FROZEN,
FACILITY.INCREASE,
FACILITY.INCREASE.ACCEPTED,
FACILITY.INCREASE.IN_REVIEW,
FACILITY.INCREASE.REJECTED,
FACILITY.RENEWAL,
FACILITY.RENEWAL.ACCEPTED,
FACILITY.RENEWAL.IN_REVIEW,
FACILITY.RENEWAL.REJECTED,
FACILITY.UNFROZEN,
INVOICE,
INVOICE.CLOSED,
INVOICE.CREATED,
INVOICE.DUE,
INVOICE.FILE,
INVOICE.FILE.CREATED,
INVOICE.FILE.DELETED,
INVOICE.FILE.REPLACED,
INVOICE.FINANCING,
INVOICE.FINANCING.PAID_OUT,
ORDER,
ORDER.CANCELLED,
ORDER.CLOSED,
ORDER.CONFIRMED,
ORDER.DISBURSED,
ORDER.EXPIRED
Example:

"FACILITY.CREATION.ACCEPTED"