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

# Add Transaction Hash

> ### Post /AddHash

By consuming this endpoint you will be able to add the Hash ID corresponding to the order/ ramp created.

#### Request

| Field | **Type** | Required | Description |
| --- | --- | --- | --- |
| Authorization | Header | Yes | The access token, valid for 5 minutes, is used to authenticate requests to other endpoints. |
| clientId | Query | Yes | Include your assigned **ID** in the URL, obtainable through the **Get infoClient** endpoint. |

#### Request Body

| **Field** | **Type** | **Required** | **Description** |
| --- | --- | --- | --- |
| rampId | String | Yes | The ID of the Off Ramp for which you made the funds transfer. |
| number | String | Yes | The Hash ID generated when you transferred your asset. Please include only the ID, not the complete URL. |

> The `clientId` query parameter is required: requests without it are rejected with 401.

#### Response

Returns `true`. The ramp moves to status `received` and Kravata starts verifying the transfer. The hash is rejected if the ramp is not `pending`/`waitingfounds`, has expired, or the hash was already used.



## OpenAPI

````yaml /business/openapi.json post /api/addhash/ramps
openapi: 3.1.0
info:
  title: Kravata Business API
  version: '1.0'
  description: >-
    Kravata Business API: on-ramp and off-ramp orders between fiat and
    stablecoins for your own accounts and wallets.
servers:
  - url: https://testapi.kravata.co
    description: Test
  - url: https://apiv2.kravata.co
    description: Production
security:
  - bearerAuth: []
tags:
  - name: Authentication
  - name: Accounts
  - name: Wallets
  - name: Ramp Orders
  - name: Webhooks
paths:
  /api/addhash/ramps:
    post:
      tags:
        - Ramp Orders
      summary: Add Transaction Hash
      description: >-
        ### Post /AddHash


        By consuming this endpoint you will be able to add the Hash ID
        corresponding to the order/ ramp created.


        #### Request


        | Field | **Type** | Required | Description |

        | --- | --- | --- | --- |

        | Authorization | Header | Yes | The access token, valid for 5 minutes,
        is used to authenticate requests to other endpoints. |

        | clientId | Query | Yes | Include your assigned **ID** in the URL,
        obtainable through the **Get infoClient** endpoint. |


        #### Request Body


        | **Field** | **Type** | **Required** | **Description** |

        | --- | --- | --- | --- |

        | rampId | String | Yes | The ID of the Off Ramp for which you made the
        funds transfer. |

        | number | String | Yes | The Hash ID generated when you transferred
        your asset. Please include only the ID, not the complete URL. |


        > The `clientId` query parameter is required: requests without it are
        rejected with 401.


        #### Response


        Returns `true`. The ramp moves to status `received` and Kravata starts
        verifying the transfer. The hash is rejected if the ramp is not
        `pending`/`waitingfounds`, has expired, or the hash was already used.
      operationId: add-transaction-hash
      parameters:
        - name: clientId
          in: query
          required: true
          description: ''
          schema:
            type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                rampId:
                  type: string
                number:
                  type: string
            example:
              rampId: '{{rampId}}'
              number: <transaction hash>
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                type: boolean
              examples:
                api-addhash:
                  summary: api/addhash
                  value: true
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: Access token from POST /api/token (valid 5 minutes).

````