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

# Feed an on-chain trigger event

> Post an on-chain event to start matching automations. For EVM contracts you usually don't need this (the platform watches for you); use it for Solana or your own indexer. Always send `txHash` so retries are de-duplicated.



## OpenAPI

````yaml /api-reference/openapi.json post /v2/automations/runtime/triggers/onchain-event
openapi: 3.0.3
info:
  title: Onchain Suite API
  version: 1.0.0
  description: >-
    The server-to-server API. Authenticate with a secret (`sk_`) key and call
    these endpoints from your backend to register contacts, send events, message
    users, ingest consented captures, and feed automations. Secret keys are
    server-only: never ship one to a browser, a mobile app, or a public repo.
servers:
  - url: https://api.onchainsuite.com/api/v1
    description: Production
security:
  - secretKey: []
tags:
  - name: Contacts
    description: Register and list contacts.
  - name: Events
    description: Send product events that drive automations and segments.
  - name: Messaging
    description: Send in-app pushes and launch campaigns.
  - name: Forms
    description: Ingest consented captures from your backend.
  - name: Automation
    description: Feed trigger events into the automation runtime.
paths:
  /v2/automations/runtime/triggers/onchain-event:
    post:
      tags:
        - Automation
      summary: Feed an on-chain trigger event
      description: >-
        Post an on-chain event to start matching automations. For EVM contracts
        you usually don't need this (the platform watches for you); use it for
        Solana or your own indexer. Always send `txHash` so retries are
        de-duplicated.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - chain
                - event
              properties:
                chain:
                  type: string
                  example: base-mainnet
                event:
                  type: string
                  example: Transfer
                walletAddress:
                  type: string
                contractAddress:
                  type: string
                txHash:
                  type: string
                sourceEventId:
                  type: string
                payload:
                  type: object
                  additionalProperties: true
      responses:
        '200':
          description: Matched against your live automations.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/TriggerResult'
components:
  schemas:
    TriggerResult:
      type: object
      properties:
        matchedAutomations:
          type: integer
        entries:
          type: array
          items:
            type: object
            properties:
              automationId:
                type: string
              entryId:
                type: string
              queued:
                type: boolean
              duplicate:
                type: boolean
  securitySchemes:
    secretKey:
      type: http
      scheme: bearer
      description: >-
        Your secret key, for example `sk_live_...`. Send it as `Authorization:
        Bearer sk_live_...`. A `sk_test_...` key runs in test mode.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.