Skip to main content
POST
Create a recipient through Zapier

Authorizations

Authorization
string
header
required

Passport bearer token authentication for legacy admin sessions.

Body

application/json

Validated input accepted by this Zapier transport.

program_id
integer
required

Program containing the recipient or sponsorship. Validation: required|integer.

Example:

11

sp_num
any | null

Sponsor-count target accepted by the recipient program. Compatibility input retains the primitive accepted numeric/string or tag-list representation. Validation: nullable.

Example:

1

sp_amount
any | null

Sponsorship funding target accepted by the recipient program. Compatibility input retains the primitive accepted numeric/string or tag-list representation. Validation: nullable.

Example:

25

is_visible
boolean | null

Whether the recipient is visible in public sponsorship listings. Validation: nullable|boolean.

Example:

true

email
string<email> | null

Profile email address. Validation: nullable|email.

Example:

"jane@example.org"

json_fields
object | null

Custom-field values keyed by the configured form field names. Validation: nullable|array.

tags
string[] | null

Tag names assigned to the recipient; names cannot contain commas. Validation: nullable|array.

idempotency_key
string | null

Stable caller key used by the selected mutation to prevent duplicate records. Validation: nullable|string|max:191.

Maximum string length: 191
Example:

"external-record-001"

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.

id
integer<int64>
required

Internal entity ID.

Example:

4711

client_id
integer<int64>
required

Owning Gratona client (multi-tenant scope).

Example:

207

program_id
integer<int64>
required

Program this entity belongs to. The program's hysform_id defines which custom fields appear in json_fields.

Example:

11

status

Recipient sponsorship state, commonly0unsponsored or1sponsored. Compatibility serializers may retain the numeric string.

is_visible

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.

json_fields

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.

batch_id
integer<int64> | null

Set when the entity was created via CSV import.

Example:

null

created_at
string<date-time>
Example:

"2025-09-01T14:00:00Z"

updated_at
string<date-time>
Example:

"2025-12-30T09:12:00Z"

deleted_at
string<date-time> | null
Example:

null