Manage webhooks

Create a webhook

🚧

Only owners and administrators can configure webhooks.

1. Develop a HTTPS endpoint on your server to receive webhook events
2. Navigate to the ‘Settings’ page in the Palisade console and click ‘Webhooks’
3. Click ‘Create webhook’
4. Enter a webhook name
   This should be an identifiable name that describes the purpose of the webhook.
5. Optional: enter a description for the webhook
6. Copy and paste the HTTPS endpoint address into the ‘URL’ section
7. Select whether you want the endpoint to receive transaction events, wallet events or both
8. Click ‘Save’

Verify webhook deliveries

1. After you create a webhook, Palisade will generate and return a P-256 ECDSA public key in ASN.1 DER format.
   For example:

{
  "id": "a6a1e8bd-30eb-419f-b6ba-e7ac11e86f84",
  "name": "wefewfwe",
  "publicKey": "MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEpHiEkdd/ba5dU4sNCgsWrMOE6fLakHywl0OgF5aVfxkiqNh22oybRAREev7jvnwH4jqitHx79KGi6CMwiJjmaw==",
  // other fields omitted
}

This public key can be viewed by clicking on the webhook in the Palisade console.

2. Extract the signature from the webhook event headers in the URL (it will be in ASN.1 DER format, base64-encoded)
3. Create a SHA-256 hash of the base64-encoded payload
4. Use the public key to verify that the signature matches the payload hash

Most programming languages have cryptography libraries that support ECDSA verification.

Security Requirements & Best Practices

• HTTPS Only: All webhook endpoints must use HTTPS for secure communication
• Signature Verification: Always verify the webhook signature to ensure authenticity
• Response Codes: Return a 200 OK response code to acknowledge receipt of the webhook

Webhook settings

Once webhooks have been created, they will be listed in a table.

Users can view or delete webhooks by clicking the three dots in the ‘actions’ column of the table.

When viewing a webhook, the following information will be available:

• Name
• Description
• URL
• Public key
• Subscriptions: whether the webhook is designed to send wallet events or transaction events (or both)
• Who created the webhook and when

📘

API docs

See our Webhooks API docs for information on how to configure webhooks via the API.