Setup your webhook
Written and published on 2025-08-03
Webhooks allow you to propagate event data to your servers.
You can use webhooks to listen for events on your Sphere account and get automatically notified when key events, such as a successful purchase, successful transfer, charge dispute, or subscription payment collection happen, and take appropriate actions like updating your database or sending out an e-mail.
Note
The average response time of Sphere webhook requests is under 5000ms.
Note
We don't recommend restricting traffic to a set number of individual IP addresses as our webhook system is designed to have dynamic IP addresses.
Webhook Signatures
A webhook signature is a security measure which allows you to verify the integrity and authenticity of the data you're receiving, using hash-based message authentication code (HMAC).
To verify that a webhook request is coming from Sphere, you can use the signature header. The value of the header is a HMAC-SHA256 signature of the request body, using the webhook secret
as the key.
Webhook Event Sequencing
Webhook events are guaranteed to be sent at least once. However, due to the nature of the webhook system, events may be sent out of order.
This means that you may receive notifications in an unexpected order.
For this reason, we recommend that you design your implementation in a way that does not rely on the order that events are received.
Create a Webhook
To start receiving webhook notifications, you can use our Webhook API to create a webhook by specifying the URL and the events you want to receive.
https://api.spherepay.co/v1/webhook
For the full API specification, see the Sphere API Reference.
Request Example
Response Example
Last updated on