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

# Validate Transaction

> Validate whether a transaction is within the user's configured limits before executing it.



## OpenAPI

````yaml openapi-v2.json POST /api/v2/wallet/transaction/validate
openapi: 3.1.0
info:
  title: Saber Money API (v2)
  version: v2
  description: >-
    ## Authentication


    There is no standalone API-key auth — every request must be **signed**. An
    API key by itself authenticates nothing. Each call requires four headers
    together: `X-Api-Key` (your key), `X-Signature` (HMAC-SHA256 of `apiKey +
    timestamp` — or `apiKey + timestamp + userId` when `X-User-Id` is required —
    keyed with your API secret), `X-Timestamp` (unix seconds), and
    `X-Request-Id` (any unique string per request). The signature must be
    computed by a client script; there is no way to derive it by hand. Use the
    HMAC Generator flow to compute valid values for manual testing.


    ## Common Authentication Errors


    - **Invalid Client ID**: {"error_code":6092,"message":"X-Client-Id
    invalid","success":false}

    - **Invalid Secret**: {"error_code":6090,"message":"invalid
    secret","success":false}

    - **Timestamp (Older than 10 secs)**:
    {"errors":{"error_code":6093,"text":"timestamp expired"},"success":false}
servers:
  - url: https://api.saber.money
security: []
paths:
  /api/v2/wallet/transaction/validate:
    post:
      tags:
        - Limits
      summary: Validate Transaction
      description: >-
        Validate whether a transaction is within the user's configured limits
        before executing it.
      operationId: validate-transaction-v2
      parameters:
        - name: X-Api-Key
          in: header
          required: true
          description: Your API key (configured in credentials)
          schema:
            type: string
        - name: X-Signature
          in: header
          required: true
          description: >-
            HMAC-SHA256 signature (auto-generated) To test manually: HMAC-SHA256
            of `apiKey + timestamp` (or `apiKey + timestamp + userId` when
            X-User-Id is required), keyed with your API secret. The HMAC
            Generator flow computes this for you.
          schema:
            type: string
        - name: X-Timestamp
          in: header
          required: true
          description: >-
            Unix timestamp in seconds (auto-generated) Unix seconds, e.g.
            `Math.floor(Date.now() / 1000)`. Must match the timestamp used in
            the X-Signature computation.
          schema:
            type: string
        - name: X-Request-Id
          in: header
          required: true
          description: >-
            Unique request identifier (auto-generated) Any unique string per
            request, e.g. a UUID.
          schema:
            type: string
        - name: X-User-Id
          in: header
          required: true
          description: User UUID (set above)
          schema:
            type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                from_currency:
                  type: string
                  description: Source currency code (e.g. INR)
                from_amount:
                  type: number
                  description: Amount in the source currency to validate
                transaction_type:
                  type: string
                  description: Type of transaction (e.g. pool_buy, sell)
                payment_method:
                  type: string
                  description: Payment method to use (e.g. bank_transfer)
                to_currency:
                  type: string
                  description: Destination currency code (e.g. USDT)
              required:
                - from_currency
                - from_amount
                - transaction_type
                - payment_method
                - to_currency
            example:
              from_currency: INR
              from_amount: 1000000
              transaction_type: pool_buy
              payment_method: bank_transfer
              to_currency: USDT
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                  data:
                    type: object
                    properties:
                      message:
                        type: string
                      status:
                        type: string
              example:
                success: true
                data:
                  message: Transaction is within limits and can proceed
                  status: APPROVED

````

## Related topics

- [Triggering Limit Upgrade and EDD](/users/limits-edd/widget.md)
- [Initiating Transaction](/onramp/operations/initiate-transaction.md)
- [Fetching Transaction Status](/offramp/operations/fetch-status.md)