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

# Send a test event

> Send a signed synthetic test event to the registered endpoint. One
attempt, no retries. The attempt is recorded in
`GET /api/v1.1/webhook-deliveries` but deliberately does **not** count
toward the 10-consecutive-failure auto-suspend threshold. Target URL
priority (fixed, not event-derived): `messageUrl` → `callbackMessageUrl`
→ `voiceUrl` → `callbackVoiceUrl` (`voiceStreamUrl` is never a test target).

This route has its own stricter rate limit — **10 requests / 60s**,
on top of (not instead of) the account-wide default — since it POSTs
to an arbitrary partner-supplied URL.




## OpenAPI

````yaml /openapi.yaml post /api/v1.1/webhooks/{id}/test
openapi: 3.1.0
info:
  title: Spenza Partner API
  version: 3.0.0
  summary: >-
    Partner API for SIMs, eSIMs, plans, billing, users, groups and numbers —
    v1.1 surface.
  description: >
    The **Spenza Partner API** lets you manage SIMs, eSIMs, plans,
    subscriptions,

    billing, users, phone numbers, teams and device/SIM/user groups
    programmatically.


    All endpoints follow one consistent standard:


    - **Auth** — exchange your API `key` + `secret` for a bearer token, then
    send
      `Authorization: Bearer <token>` on every request.
    - **Envelopes** — success responses are `{ success, data, meta? }`; errors
    are
      `{ success: false, error: { code, message, details? } }`.
    - **Pagination** — list endpoints accept `page` (1-indexed) and `pageSize`
      (max 100); totals are returned in `meta`.
    - **Idempotency** — many write endpoints honor an optional `Idempotency-Key`
      request header so a retried call replays the original result instead of
      repeating the side effect.
    - **Async operations** — a handful of endpoints (eSIM provisioning, port-in,
      the `/api/v3/...` purchase variants, top-up) return `202` (`201` for
      top-up) with a `transactionId` + `statusEndpoint` instead of the finished
      resource. Poll
      `GET /api/v3/transactions/{transactionId}` (no auth required) until the
      transaction reaches a terminal status.

    One resource — **port-in submission** — is a documented exception: it lives
    at

    `POST /api/v3/port-in`, requires an Admin-tier account role rather than just
    a

    valid bearer token, and is **not** on the standard envelope (see that
    operation's

    description for its exact response shape).
  contact:
    name: Spenza API Support
    email: support@spenza.com
    url: https://spenza.com
  license:
    name: Proprietary
    url: https://spenza.com/terms
  x-logo:
    url: https://spenza.com/logo.png
    altText: Spenza
servers:
  - url: https://api.spenza.com
    description: Production
security:
  - bearerAuth: []
tags:
  - name: Authentication
    description: Exchange API credentials for a bearer token.
  - name: SIMs
    description: List, inspect, assign and manage SIMs.
  - name: Subscriptions
    description: Plan subscriptions attached to SIMs.
  - name: Plans & Catalog
    description: Purchasable plans and SIM products.
  - name: eSIM
    description: Provision eSIMs and fetch activation QR / install status.
  - name: Billing
    description: Invoices, credit balance and top-ups.
  - name: Users
    description: End users (employees) on your account that SIMs/devices are assigned to.
  - name: Orders & Transactions
    description: Order history and financial transactions.
  - name: Numbers & Port-in
    description: Check port-in eligibility and port existing numbers into Spenza.
  - name: Messaging
    description: Send outbound SMS from a provisioned number.
  - name: Webhooks
    description: Register endpoints for operator SMS/voice events and inspect deliveries.
  - name: Notifications
    description: In-account notifications and delivery preferences.
  - name: Device Groups
    description: Organize devices into named groups with spend/data limits.
  - name: SIM Groups
    description: Organize SIMs into named groups with spend/data limits.
  - name: User Groups
    description: Organize users (departments) into named groups with spend/data limits.
  - name: Devices
    description: The device catalog (phones/tablets) and their assignment to users.
  - name: Team Members
    description: Admins who manage your Spenza account (distinct from Users/end-users).
  - name: Async Status
    description: Universal status poll for any asynchronous (v3) operation.
paths:
  /api/v1.1/webhooks/{id}/test:
    post:
      tags:
        - Webhooks
      summary: Send a test event
      description: >
        Send a signed synthetic test event to the registered endpoint. One

        attempt, no retries. The attempt is recorded in

        `GET /api/v1.1/webhook-deliveries` but deliberately does **not** count

        toward the 10-consecutive-failure auto-suspend threshold. Target URL

        priority (fixed, not event-derived): `messageUrl` → `callbackMessageUrl`

        → `voiceUrl` → `callbackVoiceUrl` (`voiceStreamUrl` is never a test
        target).


        This route has its own stricter rate limit — **10 requests / 60s**,

        on top of (not instead of) the account-wide default — since it POSTs

        to an arbitrary partner-supplied URL.
      operationId: testWebhook
      parameters:
        - name: id
          in: path
          required: true
          schema:
            type: string
            example: wh_69146d70ed68
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                eventType:
                  type: string
                  default: webhook.test
                  description: No enum — send whatever event name you want to rehearse.
      responses:
        '200':
          description: >-
            Test attempted (regardless of whether it succeeded — see
            `delivered`).
          content:
            application/json:
              example:
                success: true
                data:
                  delivered: true
                  responseCode: 200
                  attemptedAt: '2026-07-31T09:00:00.000Z'
        '400':
          description: No target URL configured on this registration.
          content:
            application/json:
              example:
                success: false
                error:
                  code: VALIDATION_ERROR
                  message: >-
                    This webhook has no endpoint URL configured to send a test
                    event to.
        '404':
          description: No webhook with that id.
          content:
            application/json:
              example:
                success: false
                error:
                  code: WEBHOOK_NOT_FOUND
                  message: We couldn't find that webhook.
        '429':
          $ref: '#/components/responses/RateLimited'
        '502':
          description: Your endpoint didn't respond successfully.
          content:
            application/json:
              example:
                success: false
                error:
                  code: DELIVERY_FAILED
                  message: >-
                    We sent the test event but your endpoint didn't respond
                    successfully — check your handler and try again.
components:
  responses:
    RateLimited:
      description: >
        Rate limit exceeded for this endpoint (or the account-wide default of
        120 req/min).

        Only `Retry-After` is present on this response — the `X-RateLimit-*`

        headers below are sent on successful (non-429) requests, not on the

        429 itself.
      headers:
        Retry-After:
          description: Seconds until you can retry.
          schema:
            type: integer
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorEnvelope'
          example:
            success: false
            error:
              code: RATE_LIMITED
              message: 'ThrottlerException: Too Many Requests'
  schemas:
    ErrorEnvelope:
      type: object
      required:
        - success
        - error
      properties:
        success:
          type: boolean
          example: false
        error:
          type: object
          required:
            - code
            - message
          properties:
            code:
              type: string
              example: SIM_NOT_FOUND
            message:
              type: string
              example: We couldn't find a SIM with that ICCID on your account.
            details:
              description: >-
                Present on some 4xx errors (for example a list of missing
                fields). Always absent on 5xx.
              type: object
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: Bearer token obtained from `POST /api/v1.1/auth/token`.

````