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

# Create Pool Buy Transaction (v1)

> Create Pool Buy Transaction

---

**Field notes (recovered from legacy docs)**

**Create Pool Buy Transaction**

**Price lock (`quote_id`)**

Pass `quote_id` to create this transaction against a price-locked quote previously issued by the Pool Buy Quote endpoint (`POST /api/v2/wallet/p/quote`). When `quote_id` is supplied, the locked currency pair, payment method, amounts, and fees are resolved from the stored quote; the matching request fields become optional and any values sent for them are ignored. When `quote_id` is absent the endpoint behaves as before and the original fields remain required.

```json
{
  "quote_id": "421b9fb7-6800-4d9d-ba17-083ad662733b",
  "source_id": "94b00193-301d-4750-b310-207393d987c9",
  "bank_transaction_id": "501610337776"
}
```

**Response field values**

| Field | Possible Values |
| --- | --- |
| `transaction_type` | `POOL_BUY` |
| `status` | Typically `PROCESSING` immediately after creation |



## OpenAPI

````yaml /openapi-v1.json post /api/v2/wallet/transaction/pool/buy
openapi: 3.1.0
info:
  title: Saber Money API (v1)
  version: v1
  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/pool/buy:
    post:
      tags:
        - Onramp
      summary: Create Pool Buy Transaction (v1)
      description: >-
        Create Pool Buy Transaction


        ---


        **Field notes (recovered from legacy docs)**


        **Create Pool Buy Transaction**


        **Price lock (`quote_id`)**


        Pass `quote_id` to create this transaction against a price-locked quote
        previously issued by the Pool Buy Quote endpoint (`POST
        /api/v2/wallet/p/quote`). When `quote_id` is supplied, the locked
        currency pair, payment method, amounts, and fees are resolved from the
        stored quote; the matching request fields become optional and any values
        sent for them are ignored. When `quote_id` is absent the endpoint
        behaves as before and the original fields remain required.


        ```json

        {
          "quote_id": "421b9fb7-6800-4d9d-ba17-083ad662733b",
          "source_id": "94b00193-301d-4750-b310-207393d987c9",
          "bank_transaction_id": "501610337776"
        }

        ```


        **Response field values**


        | Field | Possible Values |

        | --- | --- |

        | `transaction_type` | `POOL_BUY` |

        | `status` | Typically `PROCESSING` immediately after creation |
      operationId: create-pool-buy-transaction-v1
      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: The from_currency field
                to_currency:
                  type: string
                  description: The to_currency field
                from_amount:
                  type: number
                  description: The from_amount field
                payment_method:
                  type: string
                  description: The payment_method field
              required:
                - from_currency
                - to_currency
                - from_amount
                - payment_method
            example:
              from_currency: EUR
              to_currency: USDT
              from_amount: 12
              payment_method: open_banking
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                  data:
                    type: object
                    properties:
                      id:
                        type: string
                      transaction_type:
                        type: string
                        enum:
                          - POOL_BUY
                      status:
                        type: string
                        enum:
                          - PROCESSING
                      fiat_amount:
                        type:
                          - string
                          - integer
                      crypto_amount:
                        type:
                          - string
                          - number
                      fiat_symbol:
                        type: string
                      crypto_symbol:
                        type: string
                      exchange_rate:
                        type:
                          - string
                          - number
                      failure_code:
                        type: string
                      failure_desc:
                        type: string
                      created_at:
                        type: integer
                      _links:
                        type:
                          - string
                          - 'null'
                      redirect_url:
                        type: string
                      payment_intent:
                        type: string
              example:
                success: true
                data:
                  id: 019680e1-c74f-79b7-9a0b-cc316731bfd4
                  transaction_type: POOL_BUY
                  status: PROCESSING
                  fiat_amount: '12'
                  crypto_amount: '13.333333'
                  fiat_symbol: EUR
                  crypto_symbol: USDT
                  exchange_rate: '0.9000000225000006'
                  failure_code: ''
                  failure_desc: ''
                  created_at: 1745919002000
                  _links: null
                  redirect_url: >-
                    https://checkout.sand.getivy.de/?session=68109c1a1bbd722699fd25ec&ivyAuthCode=01JT0E3J778BW34PX1YN2751H4

````

## Related topics

- [Create Buy Transaction (v1)](/api-reference/onramp/create-buy-transaction-v1.md)
- [Pool buy success v1](/api-reference/webhooks/pool-buy-success-v1.md)
- [Create Pool Sell Transaction (v1)](/api-reference/offramp/create-pool-sell-transaction-v1.md)
- [Get Buy Transaction Details (v1)](/api-reference/onramp/get-buy-transaction-details-v1.md)
- [Create Sell Transaction (v1)](/api-reference/offramp/create-sell-transaction-v1.md)
