Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/api/endpoints/v0/users.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ hide_table_of_contents: true
The email address of the user.
</attribute>
<attribute id="su-resp-preferredName" name="preferredName" type="string" response optional>
The preferred name of the user. If provided, this should be used instead of the first and ast name, except where legally required.
The preferred name of the user. If provided, this should be used instead of the first and last name, except where legally required.
</attribute>
<attribute id="su-resp-firstName" name="firstName" type="string" response>
The first name of the user.
Expand Down
4 changes: 4 additions & 0 deletions docs/api/webhooks/_category_.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
{
"label": "Webhooks",
"position": 3
}
9 changes: 9 additions & 0 deletions docs/api/webhooks/about.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
# About Webhooks

Webhooks allow you to set up external applications to receive notifications when certain events happen. When a webhook event is triggered, we'll send a HTTP POST payload to the provided URL for the application.

These webhook events can be used to trigger automated actions in third-party applications, such as updating access control, mailing lists, and more.

## Test event

When you setup a webhook, you can send a test event to verify that the webhook is working correctly by using the **Test** button in Housekeeping.
Loading