Apply a received gift to recipient coverage
Requires bearer or API-key authentication, current organization scope and access to every selected recipient program. Gift/funding administration also follows the donations/reports permission policy. Only qualified received gifts with retained money in the organization currency can fund recipients. Campaign, peer-to-peer and trip records are excluded. Money-need programs derive whole monthly periods, retain any unused remainder and allow partial first-month coverage; slot programs require an explicit coverage end. Replans under the gift lock and writes all rows atomically, preventing concurrent over-allocation. Any preview problems become 422. Records funding activity and refreshes coverage/search after commit. Repeating this request can allocate more remaining money; it is not an idempotency-key endpoint and does not charge another payment.
Authorizations
Passport bearer token authentication for legacy admin sessions.
Path Parameters
Donation id.
x >= 1123
Body
Request fields accepted by this operation. Omitted optional properties retain the behavior described above.
Organization-owned recipient IDs. Duplicates are removed before planning.
1 - 500 elementsx >= 1Optional inclusive start. Otherwise starts on the gift date or the day after existing funding, whichever is later.
Optional inclusive end, validated after_or_equal:covered_from. Required by planning when the program has no monthly monetary target.
Optional amount map keyed by recipient ID. If non-empty, omitted selected IDs receive zero. Otherwise remaining gift value is split evenly, with the minor-unit remainder on the first recipient.
Funder display preference saved by apply. Preview accepts but does not use this value.
inherit, named, anonymous, null