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

# Get webhook items

> Lists webhook items for the creditor the API key is issued for. Use state=PENDING to fetch unprocessed items, optionally limited to one webhook with webhookId. For polling, create the webhook with pull=true and mark each item SUCCESS after processing it. Fetch page 0 again after acknowledging a batch: acknowledged items leave the PENDING results, so increasing the page would skip items.

**Required scope:** `read:webhooks`



## OpenAPI

````yaml GET /v1/{tenantId}/webhooks/items
openapi: 3.1.0
info:
  title: Debbie Creditor API Docs
  description: >-
    The Debbie Creditor API is a RESTful interface allowing you, as a creditor,
    to programmatically send data to your debt collection partner and access
    your data in the platform. It provides predictable URLs for accessing
    resources, and uses built-in HTTP features to receive commands and return
    responses. This makes it easy to integrate with your own systems, for
    example your ERP or invoicing system.
  version: v1.0.0
  x-logo:
    url: https://debbie-platform.github.io/creditor-api-docs/deb-logo.svg
servers:
  - url: https://api.debbiecollect.com
security:
  - bearerAuth: []
tags:
  - name: Customers
    description: Endpoints for interacting with customers
  - name: Files
    description: Endpoints for interacting with files
  - name: Documents
    description: Endpoints for attaching documentation to a case or to your creditor
  - name: Voucher types
    description: >-
      Endpoints for reading the voucher types available on your debt collection
      partner
  - name: Billings
    description: Endpoints for reading how a settlement is made up
  - name: Case voucher allocations
    description: Apply creditor payments and credit notes to specific case vouchers.
externalDocs:
  description: Find out more about Debbie here
  url: https://debbiecollect.com
paths:
  /v1/{tenantId}/webhooks/items:
    get:
      tags:
        - Webhooks
      summary: Get webhook items
      description: >-
        Lists webhook items for the creditor the API key is issued for. Use
        state=PENDING to fetch unprocessed items, optionally limited to one
        webhook with webhookId. For polling, create the webhook with pull=true
        and mark each item SUCCESS after processing it. Fetch page 0 again after
        acknowledging a batch: acknowledged items leave the PENDING results, so
        increasing the page would skip items.


        **Required scope:** `read:webhooks`
      operationId: get-webhook-items
      parameters:
        - in: path
          name: tenantId
          schema:
            type: string
            format: uuid
          required: true
          description: Id of the tenant
        - in: query
          name: page
          schema:
            type: integer
            minimum: 0
            default: 0
          example: 0
          description: Page to get. Starting from 0.
        - in: query
          name: pageSize
          schema:
            type: integer
            maximum: 1000
            minimum: 1
            default: 25
          example: 25
          description: Number of items per page.
        - in: query
          name: webhookId
          schema:
            type: string
            format: uuid
          example: b963f219-255e-47b7-a3f2-0fe6180514a1
          description: Id of the webhook.
        - in: query
          name: state
          schema:
            type: string
          example: PENDING
          description: >-
            Filter by delivery state. Accepts a single state, such as PENDING,
            or a JSON array encoded as a query string, such as
            ["PENDING","SUCCESS"]. Valid states: PENDING, SUCCESS,
            FAILED_AND_NOTIFIED, FAILED_AWATING_NOTIFICATION,
            FAILED_NO_NOTIFICATION.
        - in: query
          name: creditorId
          schema:
            type: string
            format: uuid
          description: >-
            Only return items for webhooks scoped to this creditor. Must be a
            creditor the API key can access; omitting this filter still
            restricts results to the key's creditor.
      responses:
        '200':
          description: Successful operation
          content:
            application/json:
              example:
                items:
                  - createdAt: '2026-09-22T09:00:00.000Z'
                    data:
                      caseId: 3f1c2d4e-5a6b-4c8d-9e0f-1a2b3c4d5e6f
                      referenceId: INV-2026-0042
                      customerId: 9b8a7c6d-5e4f-4a2b-9c0d-9e8f7a6b5c4d
                      creditorId: 0f6c7a3e-6e4e-4f0c-9a2a-2f6cba3f9a11
                    event: cases.delete
                    id: 867ddc9d-ee15-4493-b7fe-f6fbd6bbe71b
                    internal: false
                    name: ERP sync
                    hookId: b963f219-255e-47b7-a3f2-0fe6180514a1
                    url: https://example.com/debbie/webhooks
                    state: PENDING
                    creditorId: 0f6c7a3e-6e4e-4f0c-9a2a-2f6cba3f9a11
                meta:
                  currentPage: 0
                  pageSize: 25
        '401':
          $ref: '#/components/responses/UnauthorizedError'
        '422':
          $ref: '#/components/responses/UnprocessableContent'
components:
  responses:
    UnauthorizedError:
      description: Access token missing or invalid
    UnprocessableContent:
      description: Unable to process the contained instructions.
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        Authentication with an API key can be done by using a bearer token in
        the Authorization header. This is done using the following format
        `Authorization: Bearer {token}`. API keys are issued and revoked
        directly from the creditor portal under Developers > API.

````