> ## 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.

# Get Transaction Purposes

> Lists the transaction purposes you can declare when creating a ramp (`transactionPurpose`).

This endpoint is public: it does not require an access token.

#### Response

An array ordered by `displayOrder`:

| Field | Description |
| --- | --- |
| id | Purpose identifier. |
| label | Purpose shown to users (e.g. "Pago de proveedores"). |
| status | `active` or `inactive`. |
| displayOrder | Suggested display order. |
| registerDate | Creation date. |



## OpenAPI

````yaml /business/openapi.json get /api/parameters/transactionpurposes
openapi: 3.1.0
info:
  title: Kravata Business API
  version: '1.0'
  description: >-
    Kravata Business API: on-ramp and off-ramp orders, accounts and wallets,
    users, custody wallets and transfers.
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: Users
  - name: Ramp Orders
  - name: Custody
  - name: Webhooks
paths:
  /api/parameters/transactionpurposes:
    get:
      tags:
        - Ramp Orders
      summary: Get Transaction Purposes
      description: >-
        Lists the transaction purposes you can declare when creating a ramp
        (`transactionPurpose`).


        This endpoint is public: it does not require an access token.


        #### Response


        An array ordered by `displayOrder`:


        | Field | Description |

        | --- | --- |

        | id | Purpose identifier. |

        | label | Purpose shown to users (e.g. "Pago de proveedores"). |

        | status | `active` or `inactive`. |

        | displayOrder | Suggested display order. |

        | registerDate | Creation date. |
      operationId: get-transaction-purposes
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                type: array
                items:
                  type: object
                  properties:
                    displayOrder:
                      type: integer
                    id:
                      type: integer
                    label:
                      type: string
                    registerDate:
                      type: string
                    status:
                      type: string
              examples:
                get-transaction-purposes:
                  summary: Get Transaction Purposes
                  value:
                    - displayOrder: 1
                      id: 1
                      label: Pago de proveedores
                      registerDate: '2026-05-25 15:22:01.585743'
                      status: active
                    - displayOrder: 2
                      id: 2
                      label: Remesas
                      registerDate: '2026-05-25 15:22:01.585743'
                      status: active
                    - displayOrder: 3
                      id: 3
                      label: Ahorro
                      registerDate: '2026-05-25 15:22:01.585743'
                      status: active
      security: []
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: Access token from POST /api/token (valid 5 minutes).

````