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

# List tickets

> 🚧 **Under development.** Not available today.

Read subscriber-submitted billing tickets. Most customers route tickets via webhook to their CS tool; this endpoint is for cases where Recurr-hosted ticket history is queried directly.




## OpenAPI

````yaml /api-reference/openapi.yaml get /tickets
openapi: 3.1.0
info:
  title: Recurr API
  version: 1.0.0
  description: >
    Recurr's webhook event API. Subscription, payment, motion, and ticket

    events delivered as signed HTTP POSTs to your registered endpoints.


    See the [Overview](/api-reference/overview) for delivery model, HMAC

    authentication, idempotency, retry policy, and schema versioning.


    REST endpoints (Replay, Destination management) are documented as

    `paths` for completeness but are roadmap. See
    [Replay](/api-reference/replay)

    and [Destinations](/api-reference/destinations) for status.
  contact:
    email: hello@recurr.dev
    url: https://recurr.dev
  license:
    name: Proprietary
servers:
  - url: https://api.recurr.dev/v1
    description: Production (roadmap)
security:
  - BearerAuth: []
tags:
  - name: Subscribers
    description: Read subscriber state, history, and tags. Update metadata.
  - name: Subscriptions
    description: Subscription state + admin overrides (pause, resume, cancel, plan change).
  - name: Events
    description: Query historical webhook events for audit + debugging.
  - name: Cohorts
    description: >-
      Manage cohort definitions + view members. Used by Recurr motions for
      targeting.
  - name: Motions
    description: Inspect motion performance + manually trigger for specific subscribers.
  - name: Metrics
    description: Aggregate metrics — MRR, churn, recovery, cohort retention.
  - name: Payments
    description: Charge detail + refund / customer-credit operations.
  - name: Tickets
    description: Read subscriber-submitted billing tickets.
  - name: Replay
    description: Re-send historical webhook events to a destination.
  - name: Destinations
    description: Manage webhook delivery endpoints.
paths:
  /tickets:
    get:
      tags:
        - Tickets
      summary: List tickets
      description: >
        🚧 **Under development.** Not available today.


        Read subscriber-submitted billing tickets. Most customers route tickets
        via webhook to their CS tool; this endpoint is for cases where
        Recurr-hosted ticket history is queried directly.
      operationId: listTickets
      parameters:
        - name: status
          in: query
          schema:
            type: string
            enum:
              - open
              - resolved
              - closed
        - $ref: '#/components/parameters/Limit'
        - $ref: '#/components/parameters/StartingAfter'
        - $ref: '#/components/parameters/EndingBefore'
      responses:
        '200':
          description: Ticket list
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/TicketList'
      security:
        - BearerAuth: []
components:
  parameters:
    Limit:
      name: limit
      in: query
      description: Maximum number of items to return (1-100, default 50).
      schema:
        type: integer
        minimum: 1
        maximum: 100
        default: 50
    StartingAfter:
      name: starting_after
      in: query
      description: >-
        Cursor for pagination. Pass the `next_cursor` from the previous response
        to fetch the next page.
      schema:
        type: string
    EndingBefore:
      name: ending_before
      in: query
      description: Cursor for reverse pagination.
      schema:
        type: string
  schemas:
    TicketList:
      type: object
      required:
        - data
        - has_more
      properties:
        data:
          type: array
          items:
            $ref: '#/components/schemas/Ticket'
        has_more:
          type: boolean
        next_cursor:
          type: string
          nullable: true
    Ticket:
      type: object
      required:
        - id
        - subscriber_id
        - topic
        - status
        - created_at
      properties:
        id:
          type: string
          example: tkt_01HQX...
        subscriber_id:
          type: string
        topic:
          type: string
          enum:
            - billing_question
            - refund_request
            - plan_change
            - cancel
            - payment_issue
            - other
        subject:
          type: string
        body:
          type: string
        source:
          type: string
          enum:
            - help_center
            - billing_portal
            - email_reply
        priority:
          type: string
          enum:
            - normal
            - high
        status:
          type: string
          enum:
            - open
            - resolved
            - closed
        resolution_note:
          type: string
          nullable: true
        resolved_at:
          type: string
          format: date-time
          nullable: true
        created_at:
          type: string
          format: date-time
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: rk_live_… / rk_test_…
      description: |
        Your Recurr **secret API key** as a Bearer token:
        `Authorization: Bearer rk_live_…`.

        Keys are **environment-scoped** — `rk_live_` operates on live data,
        `rk_test_` on isolated test data (see
        [Test mode](/api-reference/test-mode)). Create, scope, and rotate keys
        in your dashboard (**Settings → API keys**, `developer` role). Secret
        keys are server-side only — never ship them in an app binary or client
        JavaScript.

````