---
updatedAt: 2026-10-16T08:11:00.482Z
---

Fetch the complete documentation index at: https://docs.avvio.xyz/llms.txt. Use this file to discover all available pages before exploring further. Append .md to any documentation page URL to get its markdown version.

# Get funding instructions

`GET https://api.avvio.xyz/business/api/v1/payments/organizations/{orgId}/payouts/{payoutId}/funding`

How to fund a payout that needs it.

Some routings price a payout and then wait for you to fund it from your
own wallet. You will know because the payout came back with
`requiresFunding: true`.

**We hold no key to your funds and cannot move them for you.** Send the
amount to the address on the network given, then confirm.

This is a pure read; poll it as often as you like. It returns only the
deposit details a business needs to broadcast funding from its own
wallet.

`expiresAt` is normally `null`. There is no client-side countdown on the
deposit address: the rail decides when an unfunded payout is over, and
it reports that as the payout's own status. Check `GET /orders/{id}`
before sending against instructions you fetched a while ago, rather than
watching a clock.

## Parameters

- `orgId` (path, required) — The opaque organization id issued to you, normally CUID-shaped (for example `cmsx…`). It is not an `org_`-prefixed alias. Pass it unchanged in every organization-scoped path.
- `payoutId` (path, required) — Opaque `payoutId` returned by create or accept. Pass it unchanged.

## Example

```bash
curl -s "$AVVIO_BASE_URL/payments/organizations/$AVVIO_ORG_ID/payouts/$payoutId/funding" \
  -H "x-api-key: $AVVIO_API_KEY"
```

## Responses

- `200` — Where to send, how much, on which network, and by when.
- `400` — `BAD_REQUEST` (sandbox): this payout settles from your balance and needs no funding.
- `401` — The key was refused. Nothing ran. - `UNAUTHORIZED`: missing, invalid or revoked, or a key on a route that does not accept one. - `KEY_EXPIRED`: the key passed the expiry it was issued with. Issue a new one; an expired key cannot be rotated. - `KEY_IP_NOT_ALLOWED`: the key is pinned to source addresses and this request came from another.
- `403` — A valid key that may not make this call. Nothing ran. - `FORBIDDEN`: the key belongs to a different organization. - `ACCOUNT_BLOCKED`: API access for your organization is suspended, and every key is refused until we lift it. Contact support.
- `404` — `NOT_FOUND`: no payout with this id belongs to your organization.
- `429` — Too many requests. The default ceiling is **100 requests per minute per API credential** on a 60-second window. High-volume payout and reconciliation routes declare a 600/minute override, and batch submission a 30/minute ceiling. A separate 2,000/minute per-source-IP abuse ceiling always applies. Obey `Retry-After`; it is in seconds and is authoritative. A 429 means the request was refused before the handler ran. Retry reads normally; retry an idempotent mutation with its same `Idempotency-Key`.
- `501` — `FUNDING_NOT_APPLICABLE`: this payout settles from your balance on a routing where there is nothing to fund. Not an error in your integration; do not retry.

Machine contract: [partner-payouts.openapi.yaml](/partner-payouts.openapi.yaml), operation `getPayoutFunding`.