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

# POST /v1/webhooks/{id}/test — Send a Test Event

> Deliver a test event synchronously and see the exact HTTP status and error your server returned.

Sends a `webhook.test` event inline and hands back what actually happened — the real response status and error text. Use it to confirm your signature check passes before you depend on push in production.

A failed test still returns HTTP 200 here; read the `delivered` field, not the status code.

**Authentication required.** Send your key as `Authorization: Bearer csb_pub_...`. A read key is enough — managing webhooks moves no money.


## OpenAPI

````yaml POST /webhooks/{id}/test
openapi: 3.1.0
info:
  title: CSBoard API
  version: 1.0.0
  description: >-
    Market data over the CSBoard marketplace — live listings, floats, stickers,
    minAsk prices, FX rates — plus opt-in buying straight from your balance.
    Free to read, key-gated, built for automation.
  contact:
    name: CSBoard
    url: https://csboard.com/docs
servers:
  - url: https://csboard.com/v1
    description: Production
security:
  - bearerAuth: []
tags:
  - name: Status
    description: Liveness and freshness probes.
  - name: Market data
    description: Read the live catalog, prices, and FX rates.
  - name: Trading
    description: Buy listings from your CSBoard balance. Opt-in, key-gated.
  - name: Account
    description: Your balance, settled funds, and trading status.
  - name: Webhooks
    description: Register an endpoint and receive signed order updates instead of polling.
paths:
  /webhooks/{id}/test:
    post:
      tags:
        - Webhooks
      summary: Send a test event
      description: >-
        Delivers a `webhook.test` event synchronously and returns the real HTTP
        status and error text your server produced. The point is to find out NOW
        whether your signature check passes and your endpoint answers, instead
        of inferring it from your own logs.
      operationId: testWebhook
      parameters:
        - name: id
          in: path
          required: true
          schema:
            type: string
      responses:
        '200':
          description: >-
            Attempt result (a failed test is still a 200 here — read
            `delivered`).
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: object
                    properties:
                      delivered:
                        type: boolean
                      response_status:
                        type: integer
                        nullable: true
                      error:
                        type: string
                        nullable: true
                      sent:
                        type: object
                        description: The exact envelope we POSTed.
        '404':
          description: '`not_found`.'
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        Send your key as a Bearer token on every request: `Authorization: Bearer
        csb_pub_...`. Generate keys in your CSBoard profile.

````