> ## 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.

# Get an event

> Returns a single event by its ID. The event's `data` is the same payload Fintoc sends to your webhook endpoints. Events are scoped to the mode of the API key you authenticate with, so an event from the other mode returns a `404 Not Found` error.



## OpenAPI

````yaml reference/main-api.json GET /v2/events/{id}
openapi: 3.1.0
info:
  title: fintoc-api
  version: v2026-02-01
servers:
  - url: https://api.fintoc.com
security: []
paths:
  /v2/events/{id}:
    get:
      tags:
        - Webhooks
      summary: Get an event
      description: >-
        Returns a single event by its ID. The event's `data` is the same payload
        Fintoc sends to your webhook endpoints. Events are scoped to the mode of
        the API key you authenticate with, so an event from the other mode
        returns a `404 Not Found` error.
      operationId: v2.events-get
      parameters:
        - name: id
          in: path
          description: >-
            Unique identifier for the event to get (for example
            `evt_0ujsswThIGTUYm2K8FjOOfXtY1K`).
          required: true
          schema:
            type: string
      responses:
        '200':
          description: The event with the given `id`.
          content:
            application/json:
              examples:
                event:
                  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:
                $ref: '#/components/schemas/event'
        '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 does not exist, or belongs to a different mode than the
            API key.
          content:
            application/json:
              examples:
                event_not_found:
                  value:
                    error:
                      type: invalid_request_error
                      code: missing_resource
                      param: id
                      message: 'No such event: evt_0ujsswThIGTUYm2K8FjOOfXtY1K'
                      doc_url: https://docs.fintoc.com/reference/errors
              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:
      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_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
  securitySchemes:
    api_key:
      type: apiKey
      name: Authorization
      in: header

````