Skip to main content
Cap how much you and each of your agents can move per transaction, per day, and per month. For how the levels combine, read the Limits overview. Each limit applies to a single payment (perTransaction), a UTC calendar day (perDay), or a calendar month (perMonth).
A limit never automatically fails a payment. A payment that breaches a limit returns a normal 2xx, no money moves, and it holds as an approval until someone approves or denies it. See Approve or deny a held payment.

Account limits

Your account limits are the backstop over everything you and every agent do.

Read your limits

GET /parties/me/limits returns the current limits. When no limit is set, limits is null.

Set your limits

PUT /parties/me/limits replaces all three windows at once. It requires party.update; agent keys cannot call it.

Remove all limits

DELETE /parties/me/limits clears every window in one call. To clear just one window, PUT that window as null and keep the others. Removing your account limits does not touch an agent’s own limits or a limit a customer set on your agent; clear those where you set them.

Agent limits

Give one agent (agt_*) a tighter budget than the rest of your account. Set limits when you create the agent with limits on POST /agents. To change them afterward, PATCH /agents/{agentId}. limits is a full replacement: sending it resets every window to what you pass.

How limits compose

A payment can pass through several limits: your account limit, the agent limit, and limits set by your customer. They are independent gates with no precedence: every applicable one must clear, so in effect the tightest limit wins. A payment that breaches any limit holds for approval. All limits must clear or be approved for a payment to complete.