> ## Documentation Index > Fetch the complete documentation index at: https://docs.yativo.com/llms.txt > Use this file to discover all available pages before exploring further. # Get Deposit > Retrieve one deposit and confirm its status Returns one of your deposits. Pass the deposit's `id` or its `deposit_id` reference. ``` GET https://api.yativo.com/api/v1/wallet/deposits/{depositId} ``` Use it to confirm a deposit before you fulfil an order. Check `status` after a `deposit.updated` webhook, or when the payer returns to your `return_url`. The query string on `return_url` isn't proof of payment. ```bash cURL theme={null} curl 'https://api.yativo.com/api/v1/wallet/deposits/b3150e03-d27e-4de3-a0ff-16ebeb55683c' \ -H 'X-Api-Key: YOUR_API_KEY' \ -H 'X-Api-Secret: YOUR_API_SECRET' ``` ```javascript Node.js theme={null} const res = await fetch(`https://api.yativo.com/api/v1/wallet/deposits/${depositId}`, { headers: { 'X-Api-Key': process.env.YATIVO_API_KEY, 'X-Api-Secret': process.env.YATIVO_API_SECRET }, }); const { data } = await res.json(); if (data.status === 'success') { // fulfil the order } ``` `404 Deposit not found` means the ID isn't one of your deposits. ## OpenAPI ````yaml openapi-fiat.yaml GET /wallet/deposits/{depositId} openapi: 3.0.3 info: title: Yativo Fiat API description: > The Yativo Fiat API enables businesses to manage customers, run KYC/KYB, send and receive cross-border payments, issue virtual accounts and virtual cards, manage beneficiaries, and more. **Base URLs** | Environment | URL | |---|---| | Production | `https://api.yativo.com/api/v1` | | Sandbox | `https://smtp.yativo.com/api/v1` | **Authentication** Send `X-Api-Key` and `X-Api-Secret` on every request. Create keys in the dashboard under **Developers → API Keys**. Each key only works from the server IPs listed on it (enforced since 14 October 2026). Keys don't expire and there's no login call or token refresh. Login tokens (`POST /auth/login` with an Account ID and App Secret, and `Authorization: Bearer`) have been discontinued and don't work for API requests. Endpoints that change how a person signs in (passkeys, two-factor authentication, PIN) or delete the account can't be called with an API key. Use the dashboard for those. API keys and IP whitelists can only be managed in the dashboard. **Rate limits** Per business account: 20 writes (`POST`, `PUT`, `PATCH`, `DELETE`) and 50 reads (`GET`) a second. Some plans set their own limit. Enterprise plans have no general limit. **Idempotency** Send an `Idempotency-Key` header on every `POST`, `PUT`, `PATCH` and `DELETE` request. A retry with the same key and body within 60 minutes returns the original response without running again. Reusing a key with a different body returns `409`. **KYC endpoints** are hosted on a separate platform at `https://kyc.yativo.com`. They are documented here for completeness but use that base URL, not the main API base. version: 1.0.0 contact: name: Yativo Support url: https://yativo.com servers: - url: https://api.yativo.com/api/v1 description: Production - url: https://smtp.yativo.com/api/v1 description: Sandbox security: - apiKey: [] apiSecret: [] tags: - name: Customers description: Create and manage customer profiles. - name: KYC / KYB description: > Identity verification for individual customers (KYC) and business customers (KYB). Submission endpoints are on `https://kyc.yativo.com/api`. - name: KYC Lookups description: > Lists your KYC and KYB forms need: countries, subdivisions, postal code formats, ID types, occupations, industries and allowed values. Served from `https://kyc.yativo.com/api`. - name: Payments & Transfers description: Exchange rates, quotes, payout methods, and wallet payouts. - name: Deposits description: Initiate and retrieve payin deposits. - name: Virtual Accounts description: Issue and manage virtual bank accounts for customers. - name: Wallets description: View balances, create wallets, and list wallet payouts. - name: Beneficiaries description: >- Save recipients' account details as beneficiaries and reuse them in payouts. - name: Transactions description: List, retrieve, track, and download receipts for all transaction types. - name: Virtual Cards description: >- Issue, manage, and terminate prepaid virtual cards. Every card request works only on your own cards. Any other card ID returns `404` with `Card not found`. - name: Payouts description: Single payouts to beneficiaries. - name: Currency Swap description: Swap balance between your own currency wallets. - name: IP Whitelist description: Check whether your server's IP can use your API key. - name: Corporate Cards description: >- Employees, their KYC, cards, card balances, memos and the USDC funding address. By invitation only. - name: Corporate Card Transactions description: Card activity on your corporate cards, with disputes, notes and invoices. - name: Corporate Card Links description: >- Each corporate card's employee-only page for card details and PIN, employee card sign-in, and branding. - name: Webhooks description: Register and manage webhook endpoints for real-time event notifications. - name: Sandbox description: Endpoints that exist only on the sandbox host. Production refuses them. - name: Developer description: Webhook event inspection. paths: /wallet/deposits/{depositId}: get: tags: - Deposits summary: Get Deposit description: > Returns one of your deposits, by its `id` or its `deposit_id` reference. The object is the same as an item from `GET /wallet/deposits`. Use it to confirm a deposit's `status` before you fulfil an order, for example after a `deposit.updated` webhook or when the payer returns to your `return_url`. parameters: - name: depositId in: path required: true schema: type: string example: b3150e03-d27e-4de3-a0ff-16ebeb55683c description: >- The deposit's `id` (`deposit_data.id` from Create Deposit, `payload.id` in `deposit.*` webhooks) or its `deposit_id` reference. responses: '200': description: The deposit content: application/json: schema: type: object properties: status: type: string example: success status_code: type: integer example: 200 message: type: string example: Request successful data: type: object properties: id: type: string deposit_id: type: string nullable: true gateway: type: string currency: type: string deposit_currency: type: string amount: type: number receive_amount: type: number status: type: string enum: - pending - processing - success - failed - cancelled - expired customer_id: type: string nullable: true transaction_id: type: string nullable: true created_at: type: string format: date-time updated_at: type: string format: date-time deposit_gateway: type: object nullable: true description: The payin method used. properties: id: type: integer method_name: type: string country: type: string currency: type: string example: status: success status_code: 200 message: Request successful data: id: b3150e03-d27e-4de3-a0ff-16ebeb55683c deposit_id: null gateway: '22' currency: CLP deposit_currency: USD amount: 10000 receive_amount: 9.36 status: success customer_id: 948a039f-9883-4b1c-88a6-2f1d3c4b5a69 transaction_id: TXN-00123456 created_at: '2026-10-22T15:52:43.000000Z' updated_at: '2026-10-22T15:58:10.000000Z' deposit_gateway: id: 22 method_name: Bank Transfer country: CHL currency: CLP '404': description: Not one of your deposits content: application/json: example: status: failed status_code: 404 message: Request failed. data: error: Deposit not found components: securitySchemes: apiKey: type: apiKey in: header name: X-Api-Key description: >- Your API key (`yativo_pk_...`) from Developers → API Keys. Send together with X-Api-Secret. apiSecret: type: apiKey in: header name: X-Api-Secret description: Your API secret (`yativo_sk_...`), shown once when the key is created. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.