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

# List events

> Lists events for your organization in the mode of the API key you use, most recent first. Each event's `data` contains the same payload Fintoc sends to your webhook endpoints. Use this endpoint to reprocess events your integration missed without waiting for a redelivery.



## OpenAPI

````yaml reference/main-api.json GET /v2/events
openapi: 3.1.0
info:
  title: fintoc-api
  version: v2026-02-01
servers:
  - url: https://api.fintoc.com
security: []
paths:
  /v2/events:
    get:
      tags:
        - Webhooks
      summary: List events
      description: >-
        Lists events for your organization in the mode of the API key you use,
        most recent first. Each event's `data` contains the same payload Fintoc
        sends to your webhook endpoints. Use this endpoint to reprocess events
        your integration missed without waiting for a redelivery.
      operationId: v2.events-list
      parameters:
        - name: ending_before
          in: query
          required: false
          schema:
            type: string
          description: >-
            Cursor for pagination. Use an event ID to define your place in the
            list. For example, if a list request returns 300 events starting
            with `evt_bar`, send `ending_before=evt_bar` in the next call to
            fetch the previous page.
        - name: limit
          in: query
          required: false
          schema:
            type: integer
            default: 30
          description: >-
            Maximum number of events to return per page. Defaults to 30, with a
            maximum of 300.
        - name: resource_id
          in: query
          required: false
          schema:
            type: string
          description: >-
            Returns only the events about this resource, such as a transfer or a
            payment intent ID.
        - name: since
          in: query
          required: false
          schema:
            oneOf:
              - type: string
                format: date
              - type: string
                format: date-time
          description: >-
            Returns only the events created at or after this point in time.
            Accepts a calendar date, such as `2026-01-15`, or an ISO 8601
            datetime, such as `2026-01-15T14:30:00Z`. Fintoc converts a datetime
            with a timezone offset to UTC. When you pass a date, the day starts
            at 00:00:00 UTC.
        - name: starting_after
          in: query
          required: false
          schema:
            type: string
          description: >-
            Cursor for pagination. Use an event ID to define your place in the
            list. For example, if a list request returns 300 events ending with
            `evt_foo`, send `starting_after=evt_foo` in the next call to fetch
            the next page.
        - name: type
          in: query
          required: false
          schema:
            type: string
            enum:
              - link.credentials_changed
              - link.refresh_intent.succeeded
              - link.refresh_intent.failed
              - account.refresh_intent.succeeded
              - account.refresh_intent.failed
              - account.refresh_intent.rejected
              - payment_intent.succeeded
              - payment_intent.rejected
              - payment_intent.failed
              - payment_intent.pending
              - payment_intent.expired
              - subscription.activated
              - subscription.canceled
              - subscription.payment_method_updated
              - subscription.payment_method_update_failed
              - subscription_intent.succeeded
              - subscription_intent.rejected
              - subscription_intent.failed
              - charge.succeeded
              - charge.failed
              - account.refresh_intent.movements_removed
              - account.refresh_intent.movements_modified
              - refund.succeeded
              - refund.failed
              - refund.in_progress
              - payout.created
              - payout.canceled
              - payout.succeeded
              - payout.returned
              - checkout_session.finished
              - checkout_session.expired
              - transfer.inbound.succeeded
              - transfer.outbound.succeeded
              - transfer.outbound.failed
              - transfer.outbound.returned
              - transfer.inbound.returned
              - transfer.inbound.return_failed
              - account_number.deleted
              - account_verification.succeeded
              - account_verification.failed
              - transfer.inbound.rejected
              - payment_method.activated
              - payment_method.canceled
              - invoice.created
              - invoice.finalized
              - invoice.paid
              - invoice.payment_created
              - invoice.payment_failed
              - invoice.payment_succeeded
              - invoice.voided
              - dispute.waiting_documentation
              - dispute.in_review
              - dispute.won
              - dispute.lost
              - dispute.expired
              - entity.onboarding.approved
              - entity.onboarding.rejected
          description: Returns only the events of this type.
        - name: until
          in: query
          required: false
          schema:
            oneOf:
              - type: string
                format: date
              - type: string
                format: date-time
          description: >-
            Returns only the events created at or before this point in time.
            Accepts a calendar date, such as `2026-01-15`, or an ISO 8601
            datetime, such as `2026-01-15T14:30:00Z`. Fintoc converts a datetime
            with a timezone offset to UTC. When you pass a date, the day ends at
            23:59:59.999999 UTC, so the whole day is included.
      responses:
        '200':
          description: >-
            List of events for the current mode, sorted by creation date (most
            recent first).
          headers:
            Link:
              schema:
                type: string
              required: false
              description: >-
                URL of the next page, with `rel="next"`, when more results are
                available.
          content:
            application/json:
              examples:
                events_list:
                  value:
                    - id: evt_0ujsswThIGTUYm2K8FjOOfXtY1K
                      object: event
                      created_at: '2026-01-15T14:30:00.000Z'
                      data:
                        id: tr_0ujsswThIGTUYm2K8FjOOfXtY1K
                        object: transfer
                        amount: 5000
                        currency: clp
                        status: succeeded
                      mode: live
                      type: transfer.outbound.succeeded
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/event'
        '400':
          description: >-
            Invalid request. `starting_after` and `ending_before` cannot be used
            together. A filter must be a single value, not a list of key-value
            pairs. `type` must be a supported event type.
          content:
            application/json:
              examples:
                unsupported_type:
                  value:
                    error:
                      type: invalid_request_error
                      code: invalid_enum
                      param: type
                      message: 'Invalid type: transfer.outbound.exploded.'
                      doc_url: https://docs.fintoc.com/reference/errors
              schema:
                $ref: '#/components/schemas/error_object_v2'
        '401':
          description: Invalid or missing API key.
          content:
            application/json:
              examples:
                invalid_api_key:
                  value:
                    error:
                      type: authentication_error
                      code: invalid_api_key
                      message: 'Invalid API Key: invalid-*oken'
              schema:
                $ref: '#/components/schemas/error_object'
        '404':
          description: The event used as a pagination cursor does not exist.
          content:
            application/json:
              examples:
                cursor_not_found:
                  value:
                    error:
                      type: missing_cursor
                      code: missing_cursor
                      message: Cursor evt_0ujsswThIGTUYm2K8FjOOfXtY1K not found
              schema:
                $ref: '#/components/schemas/error_object_v2'
      security:
        - api_key: []
components:
  schemas:
    event:
      type: object
      properties:
        id:
          type: string
          description: Unique identifier of the event.
          example: evt_0ujsswThIGTUYm2K8FjOOfXtY1K
        object:
          const: event
          description: Type of the object. Always `event`.
        created_at:
          type: string
          format: date-time
          description: >-
            Time when the event was created, as an ISO 8601 datetime in UTC with
            millisecond precision.
          example: '2026-01-15T14:30:00.000Z'
        data:
          type: object
          additionalProperties: true
          description: >-
            Resource the event is about, in the same shape the API returns the
            resource. The resource depends on `type`: a
            `transfer.outbound.succeeded` event carries a transfer, and a
            `payment_intent.succeeded` event carries a payment intent.
          example:
            id: tr_0ujsswThIGTUYm2K8FjOOfXtY1K
            object: transfer
            amount: 5000
            currency: clp
            status: succeeded
        mode:
          type: string
          enum:
            - live
            - test
          description: Whether the event happened in `live` or in `test` mode.
          example: live
        type:
          type: string
          enum:
            - link.credentials_changed
            - link.refresh_intent.succeeded
            - link.refresh_intent.failed
            - account.refresh_intent.succeeded
            - account.refresh_intent.failed
            - account.refresh_intent.rejected
            - payment_intent.succeeded
            - payment_intent.rejected
            - payment_intent.failed
            - payment_intent.pending
            - payment_intent.expired
            - subscription.activated
            - subscription.canceled
            - subscription.payment_method_updated
            - subscription.payment_method_update_failed
            - subscription_intent.succeeded
            - subscription_intent.rejected
            - subscription_intent.failed
            - charge.succeeded
            - charge.failed
            - account.refresh_intent.movements_removed
            - account.refresh_intent.movements_modified
            - refund.succeeded
            - refund.failed
            - refund.in_progress
            - payout.created
            - payout.canceled
            - payout.succeeded
            - payout.returned
            - checkout_session.finished
            - checkout_session.expired
            - transfer.inbound.succeeded
            - transfer.outbound.succeeded
            - transfer.outbound.failed
            - transfer.outbound.returned
            - transfer.inbound.returned
            - transfer.inbound.return_failed
            - account_number.deleted
            - account_verification.succeeded
            - account_verification.failed
            - transfer.inbound.rejected
            - payment_method.activated
            - payment_method.canceled
            - invoice.created
            - invoice.finalized
            - invoice.paid
            - invoice.payment_created
            - invoice.payment_failed
            - invoice.payment_succeeded
            - invoice.voided
            - dispute.waiting_documentation
            - dispute.in_review
            - dispute.won
            - dispute.lost
            - dispute.expired
            - entity.onboarding.approved
            - entity.onboarding.rejected
          description: The kind of event that happened.
          example: transfer.outbound.succeeded
      required:
        - id
        - object
        - created_at
        - data
        - mode
        - type
    error_object_v2:
      type: object
      properties:
        error:
          type: object
          description: Details of the error that caused the request to fail.
          properties:
            code:
              type: string
              description: >-
                Machine-readable code identifying the specific error, for
                example `invalid_api_key`. Not returned by every error.
              example: invalid_api_key
            doc_url:
              type: string
              description: >-
                URL of a documentation page with more details about the error.
                Not returned by every error.
              example: https://docs.fintoc.com/reference/errors
            message:
              type: string
              description: Human-readable message describing the error.
              example: 'Invalid API Key: invalid-*oken'
            param:
              type:
                - string
                - 'null'
              description: >-
                Name of the request parameter that caused the error. `null` when
                the error cannot be tied to a single parameter, and not returned
                by every error.
              example: amount
            type:
              type: string
              description: >-
                Category of the error, for example `invalid_request_error`,
                `authentication_error`, or `api_error`.
              example: invalid_request_error
          required:
            - type
            - message
    error_object:
      type: object
      properties:
        error:
          type: object
          description: Details of the error that caused the request to fail.
          properties:
            code:
              type: string
              description: >-
                Machine-readable code identifying the specific error, for
                example `invalid_api_key`. Not returned by every error.
              example: invalid_api_key
            doc_url:
              type: string
              description: >-
                URL of a documentation page with more details about the error.
                Not returned by every error.
              example: https://docs.fintoc.com/reference/errors
            message:
              type: string
              description: Human-readable message describing the error.
              example: 'Invalid API Key: invalid-*oken'
            param:
              type:
                - string
                - 'null'
              description: >-
                Name of the request parameter that caused the error. `null` when
                the error cannot be tied to a single parameter, and not returned
                by every error.
              example: amount
            type:
              type: string
              description: >-
                Category of the error, for example `invalid_request_error`,
                `authentication_error`, or `api_error`.
              example: invalid_request_error
          required:
            - type
            - message
  securitySchemes:
    api_key:
      type: apiKey
      name: Authorization
      in: header

````