Search for Webhooks API
On this page
1.45.0
This API is used to search for Webhooks and may be called using the GET or POST HTTP methods. Examples of each are provided below. The POST method is provided to allow for a richer request object without worrying about exceeding the maximum length of a URL. Calling this API with either the GET or POST HTTP method will provide the same search results given the same query parameters.
Request#
OpenAPI Spec
Use a POST request instead to send your search criteria in a JSON request body:
OpenAPI Spec
Query Parameters#
descriptionThe case-insensitive string to search for in the Webhook description. This can contain wildcards using the asterisk character (*). If no wildcards are present, this parameter value will be interpreted as *value*.
numberOfResultsThe number of results to return from the search.
orderByThe field to order the search results as well as an order direction.
The possible values are:
description- the description of the Webhookid- the unique Id of the WebhookinsertInstant- the instant when the Webhook was createdurl- the Webhook URL
The order direction is optional. Possible values of the order direction are ASC or DESC. If omitted, the default sort order is ASC.
For example, to order the results by the insert instant in a descending order, use insertInstant DESC.
startRowThe offset into the total results. In order to paginate the results, increment this value by the numberOfResults for subsequent requests.
For example, if the total search results are greater than the page size designated by numberOfResults, set this value to 25 to retrieve results 26-50, assuming the default page size.
tenantIdRestricts the results to Webhooks associated with the given Tenant and all global Webhooks.
urlThe case-insensitive string to search for in the Webhook URL. This can contain wildcards using the asterisk character (*). If no wildcards are present, this parameter value will be interpreted as *value*.
Request Body#
search.description The case-insensitive string to search for in the Webhook description. This can contain wildcards using the asterisk character (*). If no wildcards are present, this parameter value will be interpreted as *value*.
search.numberOfResults The number of results to return from the search.
search.orderBy The field to order the search results as well as an order direction.
The possible values are:
description- the description of the Webhookid- the unique Id of the WebhookinsertInstant- the instant when the Webhook was createdurl- the Webhook URL
The order direction is optional. Possible values of the order direction are ASC or DESC. If omitted, the default sort order is ASC.
For example, to order the results by the insert instant in a descending order, use insertInstant DESC.
search.startRow The offset into the total results. In order to paginate the results, increment this value by the numberOfResults for subsequent requests.
For example, if the total search results are greater than the page size designated by numberOfResults, set this value to 25 to retrieve results 26-50, assuming the default page size.
search.tenantId Restricts the results to Webhooks associated with the given Tenant and all global Webhooks.
search.url The case-insensitive string to search for in the Webhook URL. This can contain wildcards using the asterisk character (*). If no wildcards are present, this parameter value will be interpreted as *value*.
{
"search": {
"description": "game",
"numberOfResults": 25,
"orderBy": "insertInstant",
"startRow": 0,
"tenantId": "30663132-6464-6665-3032-326466613934"
}
}Response#
The response for this API contains the Webhooks matching the search criteria in paginated format and the total number of results matching the search criteria.
Response Codes| Code | Description |
|---|---|
| 200 | The request was successful. The response will contain a JSON body. |
| 400 | The request was invalid and/or malformed. The response will contain an Errors JSON Object with the specific errors. This status will also be returned if a paid FusionAuth license is required and is not present. |
| 401 | You did not supply a valid Authorization header. The header was omitted or your API key was not valid. The response will be empty. See Authentication. |
| 500 | There was an internal error. A stack trace is provided and logged in the FusionAuth log files. The response will be empty. |
Response Body#
webhooks[x].applicationIds The Ids of the Applications that this Webhook is associated with. If no Ids are returned and the global field is false, this Webhook is not used. Typically global should be set to true.
1.37.0In version 1.37.0 and beyond, Webhooks are optionally associated with Tenants instead of Applications. See new field tenantIds.
webhooks[x].connectTimeout The connection timeout in milliseconds used when FusionAuth sends events to the Webhook.
webhooks[x].data An object that can hold any information about the Webhook that should be persisted.
webhooks[x].description A description of the Webhook. This is used for display purposes only.
webhooks[x].eventsEnabled A mapping for the events that are enabled for this Webhook. The key of the Object property is the name of the event and the value is a boolean. It should look like this:
{
"user.create": true,
"user.delete": false
}
The possible event types are:
audit-log.create- When an audit log is created Available since1.30.0entity.create- When an entity is created Available since1.69.0entity.create.complete- When an entity create transaction has completed Available since1.69.0entity.delete- When an entity is deleted Available since1.69.0entity.delete.complete- When an entity delete transaction has completed Available since1.69.0entity.update- When an entity is updated Available since1.69.0entity.update.complete- When an entity update transaction has completed Available since1.69.0event-log.create- When an event log is created Available since1.30.0jwt.public-key.update- When a JWT signing Public / Private keypair may have been changedjwt.refresh- When an access token is refreshed using a refresh token Available since1.16.0jwt.refresh-token.revoke- When a JWT Refresh Token is revokedkickstart.success- When kickstart has successfully completed Available since1.30.0user.action- When a user action is triggereduser.bulk.create- When multiple users are created in bulk (i.e. during an import)user.create- When a user is createduser.create.complete- When a user create transaction has completed Available since1.30.0user.deactivate- When a user is deactivateduser.delete- When a user is deleteduser.delete.complete- When a user delete transaction has completed Available since1.30.0user.email.update- When a user updates their email address Available since1.30.0user.email.verified- When a user verifies their email address Available since1.8.0user.identity-provider.link- When a link is created from a user to an Identity Provider Available since1.36.0user.identity-provider.unlink- When an existing Identity Provider link is removed from a User Available since1.36.0user.identity.verified- When a user's identity is verified Available since1.59.0user.loginId.duplicate.create- When a request to create a user with a login Id (email or username) which is already in use has been received Available since1.30.0Enterprise plan To use the
user.loginId.duplicate.createevent , you'll need an Enterprise plan.user.loginId.duplicate.update- When a request to update a user and change their login Id (email or username) to one that is already in use has been received Available since1.30.0Enterprise plan To use the
user.loginId.duplicate.updateevent , you'll need an Enterprise plan.user.login.failed- When a user fails a login request Available since1.6.0user.login.new-device- When a user begins a login request with a new device Available since1.30.0Enterprise plan To use the
user.login.new-deviceevent , you'll need an Enterprise plan.user.login.success- When a user completes a login request Available since1.6.0user.login.suspicious- When a user logs in and is considered to be a potential threat (requires an activated Enterprise license) Available since1.30.0Enterprise plan To use the
user.login.suspiciousevent , you'll need an Enterprise plan.user.password.breach- When Reactor detects a user is using a potentially breached password (requires an activated license) Available since1.15.0user.password.reset.send- When a forgot password email has been sent to a user Available since1.30.0Enterprise plan To use the
user.password.reset.sendevent, you'll need an Enterprise plan.user.password.reset.start- When the process to reset a user password has started Available since1.30.0Enterprise plan To use the
user.password.reset.startevent, you'll need an Enterprise plan.user.password.reset.success- When a user has successfully reset their password Available since1.30.0Enterprise plan To use the
user.password.reset.successevent, you'll need an Enterprise plan.user.password.update- When a user has updated their password Available since1.30.0Enterprise plan To use the
user.password.updateevent, you'll need an Enterprise plan.user.reactivate- When a user is reactivateduser.registration.create- When a user registration is created Available since1.6.0user.registration.create.complete- When a user registration create transaction has completed Available since1.30.0user.registration.delete- When a user registration is deleted Available since1.6.0user.registration.delete.complete- When a user registration delete transaction has completed Available since1.30.0user.registration.update- When a user registration is updated Available since1.6.0user.registration.update.complete- When a user registration update transaction has completed Available since1.30.0user.registration.verified- When a user completes registration verification Available since1.8.0user.two-factor.challenge- When a user is presented a two-factor challenge Available since1.68.0Enterprise plan To use the
user.two-factor.challengeevent, you'll need an Enterprise plan.user.two-factor.failed-attempt- When a user submits an incorrect answer to a two-factor challenge Available since1.68.0Enterprise plan To use the
user.two-factor.failed.attemptevent, you'll need an Enterprise plan.user.two-factor.method.add- When a user has added a two-factor method Available since1.30.0Enterprise plan To use the
user.two-factor.method.addevent, you'll need an Enterprise plan.user.two-factor.method.remove- When a user has removed a two-factor method Available since1.30.0Enterprise plan To use the
user.two-factor.method.removeevent, you'll need an Enterprise plan.user.two-factor.success- When a user submits a correct answer to a two-factor challenge Available since1.68.0Enterprise plan To use the
user.two-factor.successevent, you'll need an Enterprise plan.user.update- When a user is updateduser.update.complete- When a user update transaction has completed Available since1.30.0
webhooks[x].global Whether or not this Webhook is used for all Tenants or just for specific Tenants.
Whether or not this Webhook is used for all events or just for specific Applications.
webhooks[x].headers An object that contains headers that are sent as part of the HTTP request for the events.
webhooks[x].httpAuthenticationPassword The HTTP basic authentication password that is sent as part of the HTTP request for the events.
webhooks[x].httpAuthenticationUsername The HTTP basic authentication username that is sent as part of the HTTP request for the events.
webhooks[x].id The Id of the Webhook.
webhooks[x].insertInstant The instant that the Webhook was added to the FusionAuth database.
webhooks[x].lastUpdateInstant The instant that the Webhook was last updated in the FusionAuth database.
webhooks[x].readTimeout The read timeout in milliseconds used when FusionAuth sends events to the Webhook.
webhooks[x].signatureConfiguration.enabled Whether or not webhook events are signed.
webhooks[x].signatureConfiguration.signingKeyId The Id of the key used to sign webhook events.
webhooks[x].sslCertificate An SSL certificate in PEM format that is used to establish the SSL (TLS specifically) connection to the Webhook.
1.48.0In version 1.48.0 and beyond, the webhook SSL certificate can be managed via webhook.sslCertificateKeyId.
webhooks[x].sslCertificateKeyId The Id of an existing Key. The X.509 certificate is used for client certificate authentication in requests to the Webhook.
webhooks[x].tenantIds The Ids of the Tenants that this Webhook is associated with. If no Ids are returned and the global field is false, this Webhook is not used.
webhooks[x].url The fully qualified URL of the Webhook's endpoint that will accept the event requests from FusionAuth.
{
"webhooks": [
{
"connectTimeout": 1000,
"data": {
"updatedBy": "richard"
},
"description": "The standard game Webhook",
"eventsEnabled": {
"user.create": true,
"user.delete": false
},
"global": false,
"headers": {
"Header 1": "value 1",
"Header 2": "value 2"
},
"httpAuthenticationPassword": "password",
"httpAuthenticationUsername": "username",
"id": "00000000-0000-0000-0000-000000000042",
"insertInstant": 1471786482322,
"lastUpdateInstant": 1595361143101,
"readTimeout": 2000,
"signatureConfiguration": {
"enabled": true,
"signingKeyId": "401c9046-b274-403f-963d-adc5024c6ef0"
},
"sslCertificateKeyId": "e31e242b-4eca-4309-921f-48cb72ec9bfb",
"tenantIds": [
"32306536-3036-6431-3865-646430303332",
"30663132-6464-6665-3032-326466613934"
],
"url": "http://mygameserver.local:7001/fusionauth-webhook"
}
]
}Related
Learn about the APIs for creating, retrieving, updating and deleting Webhooks.
An overview of the FusionAuth Event and Webhook system.
Learn about FusionAuth events.
API documentation for the FusionAuth Create a Webhook API.