> ## Documentation Index
> Fetch the complete documentation index at: https://rain-sandbox-trial.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Get webhook configuration

> Retrieves the current webhook configuration for the tenant. The configuration controls webhook behavior using pattern-based rules that match webhook event types (e.g., 'card.*', 'transaction.created.*'). Each pattern can specify a version.



## OpenAPI

````yaml /openapi.json get /issuing/webhooks/configuration
openapi: 3.0.3
info:
  title: Issuing API
  description: This is the specification for Rain's Issuing API.
  termsOfService: https://www.rain.xyz/legal/authorized-user-terms
  contact:
    email: support@rain.xyz
  version: 1.3.0
servers:
  - url: https://api-dev.rain.xyz/v1
    description: Sandbox server
  - url: https://api.rain.xyz/v1
    description: Production server
security: []
tags:
  - name: paymentRoutes
    description: >-
      **Endpoint Migration:** The `/v1/automations` endpoints have been renamed
      to `/v1/payment-routes`. The old `/v1/automations` paths remain available
      as deprecated aliases during migration. Update your integrations to use
      `/v1/payment-routes` as the deprecated endpoints will be removed in a
      future release.
  - name: simulate
    description: >-
      Transaction simulation endpoints for testing integration flows in
      non-production environments. These endpoints let you trigger transaction
      events programmatically to automate integration tests and verify webhook
      handling without depending on external systems or staging real deposits.
      **Sandbox only** — all simulation endpoints return `404 Not Found` in
      production.
  - name: raindrops
    description: >-
      Rewards and points management endpoints. Custom API keys need
      `raindrops:read`/`raindrops:write` for general rewards endpoints and
      `raindrops-travel:read`/`raindrops-travel:write` for travel redemption
      endpoints.
    x-group: rewards
paths:
  /issuing/webhooks/configuration:
    get:
      tags:
        - webhooks
      summary: Get webhook configuration
      description: >-
        Retrieves the current webhook configuration for the tenant. The
        configuration controls webhook behavior using pattern-based rules that
        match webhook event types (e.g., 'card.*', 'transaction.created.*').
        Each pattern can specify a version.
      operationId: getWebhookConfiguration
      responses:
        '200':
          description: Successful operation
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/WebhookConfigurationMap'
        '401':
          description: Invalid authorization
        '403':
          description: Forbidden
        '404':
          description: Tenant not found
        '500':
          description: Internal server error
      security:
        - ApiKeyAuth: []
components:
  schemas:
    WebhookConfigurationMap:
      type: object
      description: >-
        A map of webhook event patterns to their configuration settings.
        Patterns can use wildcards to match multiple event types (e.g., 'card.*'
        matches all card events, 'transaction.created.*' matches all transaction
        created events). Pattern format: resource.action.version or resource.*
        for wildcards.
      additionalProperties:
        $ref: '#/components/schemas/WebhookConfiguration'
      example:
        card.*:
          version: 1.0.0
        transaction.created.*:
          version: 2.0.0
    WebhookConfiguration:
      type: object
      description: Configuration settings for a webhook pattern
      properties:
        version:
          type: string
          pattern: ^[0-9]+\.[0-9]+\.[0-9]+$
          description: >-
            The webhook payload version to use (e.g., '1.0.0', '1.1.0', '1.1.1',
            '2.0.0')
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      name: Api-Key
      in: header

````