About webhooks
Integrations
Webhooks are outbound calls that are sent from Kinde when a specified events occurs. Calls are sent using HTTPS REST calls to a verified external URL you specify.
Use Kinde’s webhooks to create triggers and push event data to your other systems and applications.
Webhook request payloads are signed and sent as a JSON Web Token (JWT) from Kinde.
You’re probably using a library to validate your JWTs and they will require the url for your public JSON Web Key (also known as a jwks
file).
The jwks file can be found at https://<your_subdomain>.kinde.com/.well-known/jwks
Everything you can do in Kinde’s UI with webhooks, you can also do through the Kinde API using these endpoints.
POST api/v1/webhooks
- create a webhookPATCH api/v1/webhook/{webhook_id}
- update a webhookDELETE api/v1/webhook/{webhook_id}
- delete a webhookGET api/v1/webhooks
- list of available webhooksEvents can also be retrieved using:
GET /api/v1/events/{event_id}
- get an event by the event_id provided in a webhookGET /api/v1/event_types
- list the available event typesAvailable triggers include:
organization.created;organization.updated;user.created;user.updated;user.deleted;user.authentication_failed;user.authenticated;organization.deleted;role.created;role.updated;role.deleted;permission.created;permission.updated;permission.deleted;subscriber.created;access_request.created;
In order to use webhooks, you need a publicly available URL. To test locally you need to use a proxy to expose your local instance on the internet.
Here are a couple of free tools to help you to do this.
—subdomain
attribute to fix the issued subdomain.Each of these services expose a local port though a public URL that can be set as your web socket.