Update a recipient through Zapier
Updates supplied recipient fields through entities.update. Requires manage_programs, program access and the primitive scope. Tags may use the compatibility list/string representation; names containing commas are rejected.
Authorizations
Passport bearer token authentication for legacy admin sessions.
Path Parameters
Identifier of the existing record in the authenticated organization.
Body
Validated input accepted by this Zapier transport.
Recipient sponsorship state:0unsponsored or1sponsored. Validation: nullable|integer|in:0,1.
0, 1, null 1
Sponsor-count target accepted by the recipient program. Compatibility input retains the primitive accepted numeric/string or tag-list representation. Validation: nullable.
1
Sponsorship funding target accepted by the recipient program. Compatibility input retains the primitive accepted numeric/string or tag-list representation. Validation: nullable.
25
Whether the recipient is visible in public sponsorship listings. Validation: nullable|boolean.
true
Profile email address. Validation: nullable|email.
"jane@example.org"
Tag names assigned to the recipient; names cannot contain commas. Compatibility input retains the primitive accepted numeric/string or tag-list representation. Validation: nullable.
Custom-field values keyed by the configured form field names. Validation: nullable|array.
Response
Created, updated or replayed record; this transport unwraps the primitive success envelope.
A sponsorship recipient — the 'who/what' a donor sponsors. Entities can represent children, families, animals, projects, or any other sponsorable thing depending on the program. Like donors, entities have standardized columns plus arbitrary json_fields defined by the program's Hysform. Donations target an entity through the historical donation.designation column.
Internal entity ID.
4711
Owning Gratona client (multi-tenant scope).
207
Program this entity belongs to. The program's hysform_id defines which custom fields appear in json_fields.
11
Recipient sponsorship state, commonly0unsponsored or1sponsored. Compatibility serializers may retain the numeric string.
Whether the recipient is publicly visible. Raw compatibility model responses may use0/1.
Whether the recipient is featured in public listings. Raw compatibility model responses may use0/1.
Custom profile/record fields. Raw model responses retain the encoded JSON string; projection endpoints may return a decoded map or list. Use the record form definition to interpret field keys.
Set when the entity was created via CSV import.
null
"2025-09-01T14:00:00Z"
"2025-12-30T09:12:00Z"
null