apr_*) is a payment or transfer held for a human decision. Natural creates one when a movement breaches a Limit: the original call still succeeds, but nothing moves until someone approves. A limit is the rule; an approval is the hold it produces. You never create an approval; you resolve the ones Natural opens.
Lifecycle
An approval ispending until it is approved or denied, or canceled when the held movement is canceled first. Release one with POST /approvals/{approvalId}/approve. Refuse one with POST /approvals/{approvalId}/deny. See Approvals for the full flow.
Who resolves an approval
An approval belongs to the party behind the limit that was breached. You resolve holds triggered by your own party and agent limits. When a hold comes from a limit a customer set on their connection with you, that customer resolves it. If a single movement breaches limits owned by more than one party, it must be approved by each of those parties before the money moves. An agent can never clear a hold, by design. An owner or admin resolves approvals in the dashboard, or an API key withpayments.create resolves them through the API, never the agent that triggered them.