-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New webhooks documentation #1024
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Overall readability score: 63.23 (🟢 +0.3) View detailed metrics🟢 - Shows an increase in readability
Averages:
View metric targets
|
|
||
A webhook signature is your way to verify that the messages are sent by Codat and helps you avoid impersonation or replay attacks. We sign every webhook and its metadata with a unique key for each endpoint and include timestamps for when the message attempt occurred. | ||
|
||
You can use this signature to verify that the message truly came from Codat and process it. Our webhook service partner provides instructions, examples, and libraries in their [webhook verification documentation](https://docs.svix.com/receiving/verifying-payloads/how). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should bring Svix's docs into ours and use these as the webhook builder section of the docs. That way we can use Codat specific event types in the example and outline best practices when consuming events.
Some minor changes needed. |
Description
Type of change
Please delete options that are not relevant.
Reviews and merging
You are responsible for getting your PR merged. Address review comments promptly and make sure to merge the PR when ready.
Feel free to 'Enable automerge' - your PR will automatically merge when accepted and passing the build.