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

# Get the event log

> What happened to this verification, in order.



## OpenAPI

````yaml /api-reference/openapi.json get /v1/verifications/{id}/events
openapi: 3.1.0
info:
  title: rial API
  version: 0.1.0
  description: 'Prove a photo is real. Base URL: https://api.rial.io'
  contact:
    name: rial-platform team
    url: https://github.com/Rial-ventures-Inc/rial-platform
  license:
    name: UNLICENSED — proprietary, internal use only
servers:
  - url: https://api.rial.io
    description: Production
security: []
tags:
  - name: Verifications
    description: >-
      Create, fetch, list, and finalize verifications. The core of the API —
      every tenant integration starts here.
  - name: Templates
    description: >-
      Publish, update, revoke and inspect link templates — the reusable capture
      links behind `/l/{token}` (a compact JWT carrying the org and template
      slugs; the legacy `/l/{org}/{slug}` keeps resolving). Callable with a
      secret key; each publish snapshots a versioned capture spec (GET-83).
  - name: Databases
    description: >-
      Create, update, inspect and synchronize tenant-scoped databases used by
      reusable verification templates. Callable with a dashboard session or
      secret API key.
paths:
  /v1/verifications/{id}/events:
    get:
      tags:
        - Verifications
      summary: Get the event log
      description: What happened to this verification, in order.
      parameters:
        - schema:
            type: string
            pattern: ^vfy_[0-9A-HJKMNP-TV-Z]{26}$
            description: ULID with `vfy_` prefix.
            example: vfy_01HXYZABCDEFGHJKMNPQRSTVWX
          required: true
          name: id
          in: path
      responses:
        '200':
          description: Audit entries in chronological order.
          content:
            application/json:
              schema:
                type: object
                properties:
                  items:
                    type: array
                    items:
                      type: object
                      properties:
                        id:
                          type: string
                        type:
                          type: string
                        occurred_at:
                          type: string
                          format: date-time
                        payload:
                          type: object
                          properties: {}
                      required:
                        - id
                        - type
                        - occurred_at
                required:
                  - items
              example:
                items:
                  - id: evt_01HXYZABC
                    type: verification.created
                    occurred_at: '2026-05-28T13:00:00.000Z'
                  - id: evt_01HXYZDEF
                    type: verification.capture.persisted
                    occurred_at: '2026-05-28T13:02:15.000Z'
                  - id: evt_01HXYZGHI
                    type: verification.completed
                    occurred_at: '2026-05-28T13:05:00.000Z'
        '404':
          description: Unknown id OR cross-tenant.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  code: not_found
                  message: Resource not found
      security:
        - bearerApiKey: []
components:
  schemas:
    ErrorResponse:
      type: object
      properties:
        error:
          type: object
          properties:
            code:
              type: string
            message:
              type: string
            fields:
              type: array
              items:
                type: object
                properties:
                  path:
                    type: string
                  message:
                    type: string
                required:
                  - path
                  - message
          required:
            - code
            - message
      required:
        - error
      description: >-
        Uniform error envelope. `code` is the stable string SDKs branch on
        (`invalid_request`, `unauthorized`, `not_found`, `expired`, `step_full`,
        `unknown_step`, `steps_incomplete`, `already_finalized`,
        `too_many_requests`, `storage_unavailable`, `internal_error`). `fields`
        is only present on `invalid_request` validation failures.
  securitySchemes:
    bearerApiKey:
      type: http
      scheme: bearer
      bearerFormat: rk_secret_<key>
      description: >-
        Secret API key, created in the dashboard under Settings → API. Send it
        as `Authorization: Bearer rk_secret_…` from your server only.
        Publishable keys (`pk_live_…`) are for the native SDKs and reach the
        capture endpoints alone. An unknown key returns 401.

````