Skip to main content
POST
/
rum
/
application
/
webhook
/
test
Test application webhook
curl --request POST \
  --url 'https://api.flashcat.cloud/rum/application/webhook/test?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "application_id": "rum-app-prod",
  "webhook_url": "https://hooks.example.com/rum-alerts"
}
'
{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {
    "ok": true,
    "status_code": 200,
    "message": "ok"
  }
}

​
Restrictions

AspectValue
Rate limits1,000 requests/minute; 50 requests/second per account
PermissionsApplications Manage (rum)

​
Usage

  • The endpoint validates the URL before sending the sample event.
  • A failed delivery still returns HTTP 200 with ok=false and the delivery error in message.

Authorizations

​
app_key
string
query
required

App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.

Body

application/json

Parameters for sending a sample RUM alert webhook.

​
application_id
string
required

RUM application ID.

​
webhook_url
string<uri>
required

Webhook URL to receive the sample alert event.

Response

Success

Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.

​
request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

​
data
object
required

Result of the webhook test delivery.