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

# List Events

> Everything Reclack has emitted for your workspace.

## Overview

List everything Reclack has emitted for your workspace, whether or not an
endpoint existed at the time. This is the easiest way to see payloads while
you are still building a handler.


## OpenAPI

````yaml GET /v1/events
openapi: 3.1.0
info:
  title: Reclack API
  version: 1.0.0
  description: >-
    Recurring and one-time stablecoin payments, taken straight from your
    customers' wallets.


    Reclack is non-custodial. Payments move from a customer's wallet to a
    settlement address you control, and Reclack never holds funds and never asks
    anyone for a seed phrase or a private key.


    ## Authentication


    Send your API key in the `Api-Key` header:


    ```

    Api-Key: rk_live_your_key_here

    ```


    `X-API-Key` is accepted too. The key prefix decides the environment:
    `rk_sandbox_` for test chains, `rk_live_` for production.


    ## Responses


    Objects and lists come back under `data`. Errors come back under `error`
    with a `type`, an optional `code` and a message written for a person.
servers:
  - url: https://api.reclack.com
    description: Sandbox and live, chosen by your key
security:
  - apiKeyAuth: []
tags:
  - name: Products
  - name: Prices
  - name: Customers
  - name: Subscriptions
  - name: Usage
  - name: Invoices
  - name: Checkouts
  - name: Payment links
  - name: Transactions
  - name: Webhooks
  - name: API keys
  - name: Settlement
paths:
  /v1/events:
    get:
      tags:
        - Webhooks
      summary: List events
      description: Everything Reclack has emitted for your workspace.
      operationId: webhooks-list-events
      parameters:
        - name: type
          in: query
          required: false
          schema:
            type: string
          description: Filter by event type.
        - name: limit
          in: query
          required: false
          schema:
            type: integer
          description: How many to return.
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: array
                    items:
                      $ref: '#/components/schemas/Event'
        '400':
          description: The request is missing something or contradicts itself
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '401':
          description: No key, a revoked key, or a key that does not exist
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '403':
          description: The key is valid but is not allowed to do this
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    Event:
      type: object
      properties:
        id:
          type: string
          example: evt_4Kd9ZmPq
        type:
          type: string
          example: subscription.renewed
        object:
          type: string
          enum:
            - payment
            - invoice
            - subscription
            - checkout
            - customer
        data:
          type: object
          additionalProperties: true
          description: The object the event is about.
        created_at:
          type: string
          format: date-time
          example: '2026-10-18T22:07:41Z'
    Error:
      type: object
      properties:
        error:
          type: object
          properties:
            type:
              type: string
              description: >-
                One of invalid_request_error, authentication_error,
                permission_error or api_error.
              example: invalid_request_error
            code:
              type: string
              description: A stable, machine readable reason.
              example: price_not_found
            message:
              type: string
              description: A sentence written for a person.
              example: No price was found for that id
  securitySchemes:
    apiKeyAuth:
      type: apiKey
      in: header
      name: Api-Key
      description: >-
        Your Reclack API key. The prefix decides the environment: rk_sandbox_
        for test chains, rk_live_ for production.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.