This section helps you understand different behaviors of Fasten Connect webhook delivery & provides some best practices.
Webhook-Signature
header. This allows you to verify that the events
were sent by Fasten Connect, not by a third party. You can verify signatures either using our official libraries, or verify manually using your own solution.
See Webhook Verification for more information.
200
) prior to any complex logic that could cause a timeout.
For example, you must return a 200
response before processing the JSONL payload and storing the data in your database.
Webhooks
section in your dashboard.
Need help? You can email us at: support@fastenhealth.com