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

# List pending events for a CLI webhook endpoint

> Events recorded for a `cli` delivery-mode endpoint that have not been acknowledged yet, oldest first. Each item carries the exact request body and headers an HTTP delivery would send. Forward them to your local server, then acknowledge each event with the status it returned. Only valid for endpoints created with `delivery_mode: cli`.



## OpenAPI

````yaml get /v1/webhooks/{id}/events/pending
openapi: 3.0.0
info:
  title: Creem API
  description: >-
    Creem is an all-in-one platform for managing subscriptions and recurring
    revenue, tailored specifically for today's SaaS companies. It enables you to
    boost revenue, enhance customer retention, and scale your operations
    seamlessly.
  version: v1
  contact:
    name: Creem Support
    url: https://creem.io
    email: support@creem.io
  license:
    name: Commercial
    url: https://creem.io/terms
  termsOfService: https://creem.io/terms
servers:
  - url: https://api.creem.io
    description: Production — live API for processing real transactions and data.
    x-speakeasy-server-id: prod
  - url: https://test-api.creem.io
    description: Test — sandbox API for development and testing with no real charges.
    x-speakeasy-server-id: test
security: []
tags: []
externalDocs:
  description: Creem Documentation
  url: https://docs.creem.io
paths:
  /v1/webhooks/{id}/events/pending:
    get:
      tags:
        - Webhooks
      summary: List pending events for a CLI webhook endpoint
      description: >-
        Events recorded for a `cli` delivery-mode endpoint that have not been
        acknowledged yet, oldest first. Each item carries the exact request body
        and headers an HTTP delivery would send. Forward them to your local
        server, then acknowledge each event with the status it returned. Only
        valid for endpoints created with `delivery_mode: cli`.
      operationId: listPendingWebhookEvents
      parameters:
        - name: id
          required: true
          in: path
          description: The webhook ID
          schema:
            type: string
        - name: limit
          required: false
          in: query
          description: Maximum number of pending events to return.
          schema:
            minimum: 1
            maximum: 100
            default: 50
            type: integer
      responses:
        '200':
          description: Successfully retrieved the pending events
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/WebhookPendingEventListEntity'
        '400':
          description: Bad Request - Invalid input parameters
        '401':
          description: Unauthorized - Invalid or missing API key
        '404':
          description: Not Found - Resource does not exist
      security:
        - ApiKey: []
components:
  schemas:
    WebhookPendingEventListEntity:
      type: object
      properties:
        items:
          description: Pending events, oldest first.
          type: array
          items:
            $ref: '#/components/schemas/WebhookPendingEventEntity'
      required:
        - items
    WebhookPendingEventEntity:
      type: object
      properties:
        id:
          type: string
          description: The event ID. Acknowledge the delivery with this ID.
          example: evt_5Xb2mQ7vN1pLk9RtYw3zA
        object:
          type: string
          description: >-
            A string representing the object’s type. Objects of the same type
            share the same value.
          example: webhook_event
        event_type:
          $ref: '#/components/schemas/WebhookEventType'
          example: checkout.completed
        created_at:
          format: date-time
          type: string
          description: When the event was recorded for this endpoint.
          example: '2026-09-17T08:00:00.000Z'
        body:
          type: string
          description: >-
            The exact JSON request body of the delivery. Forward it
            byte-for-byte; the signature header is computed over this string.
          example: >-
            {"id":"evt_5Xb2mQ7vN1pLk9RtYw3zA","eventType":"checkout.completed","created_at":1758096000000,"object":{"id":"ch_..."}}
        headers:
          type: object
          description: >-
            The HTTP headers a real delivery would carry, including
            `creem-signature`. Send them unchanged with `body`.
          additionalProperties:
            type: string
          example:
            creem-signature: a1b2c3…
            Content-Type: application/json
      required:
        - id
        - object
        - event_type
        - created_at
        - body
        - headers
    WebhookEventType:
      type: string
      description: The event type carried in the delivery.
      enum:
        - checkout.completed
        - refund.created
        - dispute.created
        - subscription.active
        - subscription.trialing
        - subscription.canceled
        - subscription.scheduled_cancel
        - subscription.paid
        - subscription.expired
        - subscription.unpaid
        - subscription.update
        - subscription.past_due
        - subscription.paused
        - customer_credits.exhausted
        - credits.granted
        - credits.consumed
        - credits.auto_recharged
  securitySchemes:
    ApiKey:
      type: apiKey
      in: header
      name: x-api-key
      description: >-
        API key for authentication. You can find your API key in the Creem
        dashboard under Settings > API Keys.

````