> ## Documentation Index > Fetch the complete documentation index at: https://docs.stableyard.fi/llms.txt > Use this file to discover all available pages before exploring further. # Get Vault spend usage > Read how much of a Vault's delegated payment allowance is used and available. Returns the Vault's delegated payment limit, set by the Vault's on-chain spending policy, with the consumed, pending and currently available amounts, the exact reset time and the supported assets. Pending amounts are Vault payments that are in flight. USDC and USDT consume the same limit. Transfers the Vault owner makes directly do not count against this limit. ## OpenAPI ````yaml openapi.json GET /v2/accounts/{accountId}/vault/spend-usage openapi: 3.1.0 info: title: Stableyard Partner API version: 2.0.0 x-stableyard-api-version: '2026-09-09' x-stableyard-supported-api-versions: - '2026-09-09' summary: Backend API for UPAs, Payments, activity, and optional financial products. description: > Use this API from a trusted partner backend with an app ID and app secret. ## Recommended integration 1. Call `GET /v2/partners/config` to verify credentials and discover enabled capabilities. 2. Create a UPA only when your product needs a persistent Stableyard account. 3. Create a receive or send Payment with `POST /v2/payments`. 4. Redirect a payer to the returned `paymentUrl` or pass the Payment credentials to an official Stableyard interface SDK. 5. Process signed webhooks and fetch the Payment by ID for reconciliation. Checkout execution and account-bound browser endpoints are documented in the separate Interfaces & SDKs reference. x-stableyard-documentation-surface: partner servers: - url: https://prod-api.stableyard.fi description: Production - url: https://staging-api-v2.stableyard.fi description: Sandbox security: [] tags: - name: Authentication x-displayName: API authentication description: Verify your app ID and app secret before calling UPA APIs. - name: Accounts x-displayName: UPA Accounts description: Create Universal Payment Accounts and manage account settings. - name: Deposit Addresses description: Create reusable receive addresses and verify inbound deposits. - name: Identity & KYC description: >- Verify the UPA email and run identity verification. Managed vaults and fiat payment rails use this same verified UPA identity. - name: Vaults description: >- Create policy-controlled stablecoin vaults and manage policy updates for accounts. - name: Payments description: >- Create escrow-first payments, issue partner-authenticated send instructions or executions, power public checkout, and reconcile collection through final account settlement. - name: Balances & Transactions description: >- Read Stableyard-posted financial activity. Balances are ledger projections of activity Stableyard processed; they are not live balances of externally controlled wallets. paths: /v2/accounts/{accountId}/vault/spend-usage: get: tags: - Vaults summary: Get Vault spend usage description: >- Returns the Vault's delegated payment limit, consumed amount, pending amount, currently available amount, exact reset time, and supported assets. Pending payments count against the limit. USDC and USDT consume the same limit. Transfers the Vault owner makes directly do not consume this delegated allowance. operationId: getVaultSpendUsage parameters: - name: accountId in: path required: true schema: type: string example: acct_123 description: Canonical account id returned by the Accounts API. - name: Stableyard-Version in: header required: false schema: type: string enum: - '2026-09-09' description: >- Optional contract-version assertion. Omit it to use the app environment's pinned version. A different supported version is accepted only after that environment is explicitly migrated. responses: '200': description: Vault spend usage headers: Stableyard-Version: description: >- Effective date-based Stableyard API contract version for this response. schema: type: string enum: - '2026-09-09' content: application/json: schema: $ref: '#/components/schemas/VaultSpendUsage' examples: example: summary: Get Vault spend usage 200 response value: vaultId: vault_123 status: active reason: Requested by partner period: fixed_30_day periodSeconds: 2592000 supportedAssets: - symbol: USDC chainId: 42161 tokenAddress: '0xaf88d065e77c8cC2239327C5EDb3A432268e5831' decimals: 6 '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '409': $ref: '#/components/responses/Conflict' '424': $ref: '#/components/responses/FailedDependency' '429': $ref: '#/components/responses/TooManyRequests' '502': $ref: '#/components/responses/BadGateway' security: - partnerBasicAuth: [] components: schemas: VaultSpendUsage: type: object additionalProperties: false required: - vaultId - status - period - periodSeconds - supportedAssets properties: vaultId: type: string example: vault_123 status: type: string enum: - active - not_active reason: type: string description: Present when status is not_active. period: type: string const: fixed_30_day periodSeconds: type: integer const: 2592000 limitUsdAtomic: type: string pattern: ^[0-9]+$ limitAtomic: type: string pattern: ^[0-9]+$ consumedAtomic: type: string pattern: ^[0-9]+$ onchainConsumedAtomic: type: string pattern: ^[0-9]+$ settledRecordedAtomic: type: string pattern: ^[0-9]+$ pendingAtomic: type: string pattern: ^[0-9]+$ availableAtomic: type: string pattern: ^[0-9]+$ windowStartedAt: type: string format: date-time resetsAt: type: string format: date-time observedAt: type: string format: date-time supportedAssets: type: array items: type: object additionalProperties: false required: - symbol - chainId - tokenAddress - decimals properties: symbol: type: string enum: - USDC - USDT chainId: type: integer example: 42161 tokenAddress: type: string example: '0xaf88d065e77c8cC2239327C5EDb3A432268e5831' decimals: type: integer const: 6 ErrorResponse: type: object additionalProperties: false required: - error properties: error: type: object additionalProperties: false required: - code - message properties: code: type: string minLength: 1 maxLength: 128 example: bad_request message: type: string minLength: 1 maxLength: 1000 example: The request is invalid details: {} responses: BadRequest: description: Bad request headers: Stableyard-Version: description: >- Effective date-based Stableyard API contract version for this response. schema: type: string enum: - '2026-09-09' content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: example: summary: bad_request value: error: code: bad_request message: The request is invalid Unauthorized: description: Unauthorized headers: Stableyard-Version: description: >- Effective date-based Stableyard API contract version for this response. schema: type: string enum: - '2026-09-09' content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: example: summary: unauthorized value: error: code: unauthorized message: Authentication is required Forbidden: description: The app secret does not include the required scope headers: Stableyard-Version: description: >- Effective date-based Stableyard API contract version for this response. schema: type: string enum: - '2026-09-09' content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: example: summary: forbidden value: error: code: forbidden message: The credential does not allow this operation NotFound: description: Not found headers: Stableyard-Version: description: >- Effective date-based Stableyard API contract version for this response. schema: type: string enum: - '2026-09-09' content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: example: summary: not_found value: error: code: not_found message: The resource was not found Conflict: description: Conflict headers: Stableyard-Version: description: >- Effective date-based Stableyard API contract version for this response. schema: type: string enum: - '2026-09-09' content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: example: summary: idempotency_conflict value: error: code: idempotency_conflict message: >- The Idempotency-Key was already used with a different request FailedDependency: description: This feature is not configured for your app or environment headers: Stableyard-Version: description: >- Effective date-based Stableyard API contract version for this response. schema: type: string enum: - '2026-09-09' content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: example: summary: chain_config_missing value: error: code: chain_config_missing message: The requested network is not configured for this environment TooManyRequests: description: Too many requests. Retry after the `Retry-After` interval. headers: Stableyard-Version: description: >- Effective date-based Stableyard API contract version for this response. schema: type: string enum: - '2026-09-09' Retry-After: description: Seconds until the caller should retry. schema: type: integer minimum: 1 RateLimit-Limit: description: Quota for the most constrained policy. schema: type: integer minimum: 1 RateLimit-Remaining: description: Requests remaining in that policy window. schema: type: integer minimum: 0 RateLimit-Reset: description: Seconds until that policy window resets. schema: type: integer minimum: 0 content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: example: summary: rate_limited value: error: code: rate_limited message: Too many requests BadGateway: description: An upstream service returned an error. Retry later. headers: Stableyard-Version: description: >- Effective date-based Stableyard API contract version for this response. schema: type: string enum: - '2026-09-09' content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: example: summary: provider_failure value: error: code: provider_failure message: An upstream service returned an error securitySchemes: partnerBasicAuth: type: http scheme: basic description: >- HTTP Basic auth. Username is the Stableyard app ID. Password is the app secret. The optional Stableyard-Version request header must match the environment pin. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.