> ## Documentation Index
> Fetch the complete documentation index at: https://docs.secapi.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# POST /v1/webhook_endpoints/{webhook_id}/test

> Send a signed webhook.test event to a webhook endpoint

Send a signed webhook.test event to a webhook endpoint

<Info>
  Audience: application and admin.
</Info>

## Canonical metadata

* `requestId`
* `traceparent`

## Example request

<RequestExample>
  ```bash theme={null}
  curl -X POST \
    -H "Authorization: Bearer $SECAPI_BEARER_TOKEN" \
    -H "secapi-version: 2026-03-19" \
    -H "content-type: application/json" \
    -d '{"eventType":"webhook.test","data":{"source":"dashboard"}}' \
    "https://api.secapi.ai/v1/webhook_endpoints/wh_example_123/test"
  ```
</RequestExample>

## Example response

<ResponseExample>
  ```json theme={null}
  {
    "object": "webhook_test",
    "event": {
      "object": "event",
      "id": "evt_webhook_test_123",
      "type": "webhook.test",
      "createdAt": "2026-06-25T15:01:00.000Z",
      "livemode": false,
      "orgId": "org_example_123",
      "requestId": "req_2ZK8Q1W9F4M6P7R3",
      "data": {
        "message": "SEC API webhook test",
        "webhookId": "wh_2ZK8Q1W9F4M6P7R3",
        "requestedBy": "delivery_api"
      }
    },
    "delivery": {
      "kind": "webhook_delivery",
      "recordedAt": "2026-06-25T15:01:00.250Z",
      "orgId": "org_example_123",
      "eventId": "evt_webhook_test_123",
      "eventType": "webhook.test",
      "webhookId": "wh_2ZK8Q1W9F4M6P7R3",
      "destinationUrl": "https://example.com/hooks/secapi",
      "status": 200,
      "ok": true,
      "requestId": "req_2ZK8Q1W9F4M6P7R3",
      "error": null,
      "latencyMs": 250,
      "replayedFromDeliveryId": null
    },
    "requestId": "req_2ZK8Q1W9F4M6P7R3"
  }
  ```
</ResponseExample>

## Give this prompt to your agent

<Prompt>
  Use SEC API POST /v1/webhook\_endpoints/{webhook_id}/test to send a signed webhook.test event to a webhook endpoint. Preserve `requestId`, `traceparent` in the output. Return a concise markdown summary plus the exact structured payload fields that a downstream engineer or agent should keep using this result.
</Prompt>

## Failure posture

* treat non-2xx responses as contract-aware failures, not free-form errors
* preserve `requestId` and `traceparent` in logs and downstream reports
* if provenance or freshness metadata is present, return it unchanged so trust is not lost in the handoff