> ## Documentation Index > Fetch the complete documentation index at: https://docs.etherfuse.com/llms.txt > Use this file to discover all available pages before exploring further. # Get amount limits > Returns the organization's 30-day limit, its volume over the last 30 days, and how much it can still order, all in USD. The volume adds up the USD value of each order's source side, priced when we quoted it, for every order created in the last 30 days. We leave out orders that are `canceled`, `failed` or `refunded`. An unfunded order past its funding deadline counts until it is canceled. A business organization's volume includes its customer organizations' orders. A customer organization sees only its own orders, but an order has to fit under its own limit and its business organization's limit. So its remaining amount is the lower of the two. An order that would bring the volume above a 30-day limit returns `volume-limit-exceeded`. Per-order limits are on each rail of a payment account, in the rail's currency and in USD. ## OpenAPI ````yaml openapi-v2.json GET /organization/{organizationId}/amount_limits openapi: 3.1.0 info: title: Etherfuse FX API description: >- Partner-facing ramp API, version 2: payment accounts, quotes, orders and webhooks. license: name: Proprietary version: 2.0.0 servers: - url: https://api.sand.etherfuse.com description: Sandbox security: - ApiKeyAuth: [] tags: - name: Payment Accounts description: >- Register the bank accounts and wallets that money moves from and to, and read their readiness per rail. - name: Quotes description: Price a transfer between two registered payment accounts. - name: Orders description: Create orders from quotes and track them. - name: Webhook Subscriptions description: Subscribe to webhook events. - name: Webhook Events description: Payloads Etherfuse sends to your webhook subscriptions. - name: Sandbox description: Endpoints that work only in sandbox, for testing. - name: Assets description: The markets and tokens a quote can use, and the balances of a wallet. - name: Authentication description: >- Partner JWT authentication: exchange a JWT for an access token, or launch a user into the app. - name: KYC description: >- Submit a customer's verification data, documents and questionnaire answers, import a verification they already passed elsewhere, and check where their KYC stands. - name: KYB description: Check where a business organization's KYB stands. - name: Lookup description: >- Public reference data: exchange rates, stablebonds, bond costs, country codes. - name: Organizations description: >- Your organization, your default partner fee, and the customer organizations you create. - name: Members description: >- The people who belong to a customer business organization and complete its KYB. - name: Statements description: >- Monthly revenue share statements for closed months, as a list or as a CSV or PDF download. paths: /organization/{organizationId}/amount_limits: get: tags: - Organizations summary: Get amount limits description: >- Returns the organization's 30-day limit, its volume over the last 30 days, and how much it can still order, all in USD. The volume adds up the USD value of each order's source side, priced when we quoted it, for every order created in the last 30 days. We leave out orders that are `canceled`, `failed` or `refunded`. An unfunded order past its funding deadline counts until it is canceled. A business organization's volume includes its customer organizations' orders. A customer organization sees only its own orders, but an order has to fit under its own limit and its business organization's limit. So its remaining amount is the lower of the two. An order that would bring the volume above a 30-day limit returns `volume-limit-exceeded`. Per-order limits are on each rail of a payment account, in the rail's currency and in USD. operationId: v2GetAmountLimits parameters: - $ref: '#/components/parameters/OrganizationId' responses: '200': description: The organization's amount limits. content: application/json: schema: $ref: '#/components/schemas/AmountLimits' '400': $ref: '#/components/responses/InvalidRequest' '401': $ref: '#/components/responses/Unauthorized' '404': $ref: '#/components/responses/OrganizationNotFound' '500': $ref: '#/components/responses/InternalError' components: parameters: OrganizationId: name: organizationId in: path required: true description: >- The organization this call acts for: your API key's organization or one of its customer organizations. Any other id returns `404` `not-found`. schema: type: string format: uuid schemas: AmountLimits: type: object required: - volume30DayUsd - max30DayVolumeUsd - remaining30DayVolumeUsd properties: volume30DayUsd: type: string description: >- USD value of the orders created in the last 30 days, as a decimal string with at most two decimals. example: '1250.5' max30DayVolumeUsd: type: - string - 'null' description: >- The organization's own limit on its 30-day volume, in USD, as a decimal string. `null` when the organization has no 30-day limit of its own. example: '50000' remaining30DayVolumeUsd: type: - string - 'null' description: >- How much more the organization can order before it reaches a 30-day limit, in USD, as a decimal string. For a customer organization, this is the lower of what its own limit and its business organization's limit leave. Never below 0. `null` when no 30-day limit applies. example: '48749.5' Problem: type: object description: >- RFC 9457 problem details. Every v2 error uses this body with content type `application/problem+json`. `errors` is present only on `validation-error`. `required` and `missing` are present only on `registration-info-required`. required: - type - title - status - detail - instance properties: type: type: string format: uri description: >- `https://docs.etherfuse.com/ramp/v2/errors/` followed by the problem slug, for example `https://docs.etherfuse.com/ramp/v2/errors/quote-expired`. Switch on this value. example: https://docs.etherfuse.com/ramp/v2/errors/quote-expired title: type: string description: Short summary of the problem type. example: Quote expired status: type: integer description: The HTTP status code. example: 400 detail: type: string description: Human-readable explanation of this occurrence. Do not parse it. example: >- quote 5e6f7a8b-9c0d-4e1f-8a2b-3c4d5e6f7a8b has expired or does not exist instance: type: string description: Unique identifier for this occurrence. Quote it to support. example: >- tag:etherfuse.com,2026-08-28:R2-10120/0b1c2d3e-4f50-4a6b-8c7d-9e0f1a2b3c4d errors: type: array description: Present on `validation-error`. One entry per invalid field. items: $ref: '#/components/schemas/FieldViolation' required: type: array description: >- Present on `registration-info-required`. Every registration field the route requires, as JSON Pointers into the request, for example `#/registrationInfo/taxId`. items: type: string missing: type: array description: >- Present on `registration-info-required`. The required fields you must still send, as JSON Pointers into the request. items: type: string FieldViolation: type: object required: - pointer - detail properties: pointer: type: string description: >- JSON Pointer to the field in the request, for example `#/accountDetails/clabe`. example: '#/accountDetails/clabe' detail: type: string description: What is wrong with the field. example: This field is required. responses: InvalidRequest: description: >- `invalid-request`: a path, query or body value is malformed, or `pageSize` is 0 or over 100. content: application/problem+json: schema: $ref: '#/components/schemas/Problem' Unauthorized: description: >- `unauthorized`: the `Authorization` header is missing, not ASCII, or does not hold a valid API key. content: application/problem+json: schema: $ref: '#/components/schemas/Problem' OrganizationNotFound: description: '`not-found`: your API key cannot act for this organization.' content: application/problem+json: schema: $ref: '#/components/schemas/Problem' InternalError: description: >- `internal-error`: an unexpected error on our side. Retry with backoff, and quote `instance` to support if it persists. content: application/problem+json: schema: $ref: '#/components/schemas/Problem' securitySchemes: ApiKeyAuth: type: apiKey in: header name: Authorization description: API key sent in the Authorization header, with no `Bearer` prefix. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.