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

# Post transaction hash after broadcast

> After broadcasting a signed transaction on-chain, post the txHash back to Mandate. This transitions the intent to `broadcasted` and triggers asynchronous envelope verification (for raw-validated intents).



## OpenAPI

````yaml /openapi.json post /api/intents/{intentId}/events
openapi: 3.1.0
info:
  title: Mandate API
  version: 1.2.0
  description: >-
    Non-custodial agent wallet policy layer. Enforces spend limits, allowlists,
    and approval workflows for AI agent transactions without ever receiving
    private keys.
  contact:
    name: Mandate
    url: https://mandate.md
    email: support@mandate.md
  license:
    name: MIT
    url: https://opensource.org/licenses/MIT
servers:
  - url: https://app.mandate.md
    description: Production
security: []
tags:
  - name: Registration
    description: >-
      Agent registration and claiming. No auth required for register; Sanctum
      auth for claim.
  - name: Agent API
    description: >-
      Endpoints authenticated with a runtime key (Bearer mndt_live_... or
      mndt_test_...). Used by agents to validate transactions, post events, and
      poll status.
  - name: Intent Lifecycle
    description: >-
      Post transaction hashes after broadcast and poll intent status until
      confirmed.
  - name: Dashboard
    description: >-
      Dashboard endpoints for human operators. Authenticated via Sanctum
      (cookie-based session).
  - name: Policies
    description: >-
      Policy management for agents. List, create, and view policy
      configurations.
  - name: Approvals
    description: Approval queue for transactions that require human review.
paths:
  /api/intents/{intentId}/events:
    post:
      tags:
        - Intent Lifecycle
      summary: Post transaction hash after broadcast
      description: >-
        After broadcasting a signed transaction on-chain, post the txHash back
        to Mandate. This transitions the intent to `broadcasted` and triggers
        asynchronous envelope verification (for raw-validated intents).
      operationId: postIntentEvent
      parameters:
        - name: intentId
          in: path
          required: true
          description: The intent ID returned from validation.
          schema:
            type: string
            format: uuid
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PostEventRequest'
            example:
              txHash: >-
                0x9f2e4a5b6c7d8e9f0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e3f
      responses:
        '200':
          description: Event recorded, intent transitioned to broadcasted.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PostEventResponse'
              example:
                intentId: 9e5f1a2b-3c4d-5e6f-7a8b-9c0d1e2f3a4b
                status: broadcasted
                txHash: >-
                  0x9f2e4a5b6c7d8e9f0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e3f
        '401':
          description: Invalid or missing runtime key.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '404':
          description: Intent not found.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error: Intent not found.
        '409':
          description: Intent is in terminal state or wrong status for posting events.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ConflictResponse'
              example:
                error: Intent must be in reserved or approved state to post a txHash.
                status: confirmed
      security:
        - RuntimeKeyAuth: []
components:
  schemas:
    PostEventRequest:
      type: object
      required:
        - txHash
      properties:
        txHash:
          type: string
          pattern: ^0x[a-fA-F0-9]{64}$
          description: The on-chain transaction hash.
    PostEventResponse:
      type: object
      required:
        - intentId
        - status
        - txHash
      properties:
        intentId:
          type: string
          format: uuid
        status:
          type: string
          enum:
            - broadcasted
        txHash:
          type: string
    ErrorResponse:
      type: object
      required:
        - error
      properties:
        error:
          type: string
          description: Human-readable error message.
    ConflictResponse:
      type: object
      required:
        - error
      properties:
        error:
          type: string
        status:
          type: string
          description: Current intent status.
  securitySchemes:
    RuntimeKeyAuth:
      type: http
      scheme: bearer
      description: >-
        Runtime key issued at agent registration. Prefixed with `mndt_live_`
        (mainnet) or `mndt_test_` (testnet). Pass as `Authorization: Bearer
        mndt_test_...`.

````