Send a Webhook Test Event

Endpoint URL: {identityDomain} /{customerId} /webhooks/subscriptions/{subscriptionId}/test


Sends a test notification for a webhooks subscription. Webhook subscriptions specify the event types that trigger near real-time notifications: when one of these events occurs, a webhooks notification is sent to a listener endpoint created and maintained by the organization associated with the subscription.

Note that the Webhooks v3 APIs all have an API response timeout of 10 seconds.

Respects the API Client Allow List: No

Base URL

The base URL for this endpoint is your Identity Cloud API URL, including the appropriate region. For example, if you are in the US region, then your base URL will look like this:

If you are in the Australian (AU) region your base URL will look like this: 

URL path parameters








Unique identifier of the organization (customer) associated with the webhooks subscription being tested. For example:





Unique identifier of the webhooks subscription being tested. For example:


Request Parameters

No request parameters are needed to call this endpoint.


This endpoint requires token-based authentication. To obtain an access token, you must use a confidential client (using the client ID as the username and the client secret as the password) to access the /{customerId}/login/token endpoint. The access token returned from that endpoint is then used in the Authorization header of your API call. For example, if you get back the access token 03v-eeodppPrrHXXIx56pRLyDBaOldDxqEwI59MFCFGVuSkLRapzgmfwmEHyKWle then your Authorization header will look like this when using Curl:

-H 'Authorization: Bearer 03v-eeodppPrrHXXIx56pRLyDBaOldDxqEwI59MFCFGVuSkLRapzgmfwmEHyKWle'

In Postman, set the Authorization Type to Bearer and use the access token as the value of the Token field.

Sample Request (curl)

The following command sends a test event (entityCreated) to the webhooks subscription with the ID 454fe969-1909-4e93-b552-674d47eafdb0:

curl -X POST \ \
  -H 'Authorization: Bearer Xk7EzdpGq5GPQcsxCWM2SxdlwU_iTsA4i2Px4TEzBrfLIvddjnDVBJxjPDuCARHH' 


202 Accepted

If your call to this endpoint succeeds, you won’t get back a full API response; instead, you'll get back a 202 Accepted status code.

Error Response Codes

The following table includes information about some of the other response codes that you might encounter when calling this endpoint.

Response Code



Forbidden. You do not have permission to access the requested resource.


Not found. The specified customer and/or the specific webhooks subscription could not be found.