curl --request PATCH \
--url https://{domain}/wp-json/sagescreen/v1/zapier/user/{user_id} \
--header 'Content-Type: application/json' \
--header 'X-API-Key: <api-key>' \
--data '
{
"email_product_updates": true,
"email_product_marketing": false
}
'{
"success": true,
"data": {
"user_id": 42,
"updated": {
"email_product_updates": true,
"council_id": "new-council-uuid",
"role": "council_power_user"
}
}
}User – REST
Update user data via Zapier
Partial update — only supplied fields are modified. Supports email preferences, council assignment, and role changes.
Requires the X-API-Key header (Zapier API key).
PATCH
/
zapier
/
user
/
{user_id}
curl --request PATCH \
--url https://{domain}/wp-json/sagescreen/v1/zapier/user/{user_id} \
--header 'Content-Type: application/json' \
--header 'X-API-Key: <api-key>' \
--data '
{
"email_product_updates": true,
"email_product_marketing": false
}
'{
"success": true,
"data": {
"user_id": 42,
"updated": {
"email_product_updates": true,
"council_id": "new-council-uuid",
"role": "council_power_user"
}
}
}Authorizations
SageScreen API key stored in ss_zapier_api_key option
Path Parameters
Example:
"42"
Body
application/json
Partial update — only supplied fields are modified
Example:
true
Example:
false
Reassign to a different council (must exist)
Example:
"c9d8e7f6-5a4b-3c2d-1e0f-a1b2c3d4e5f6"
Set role (invalid values silently ignored with log)
Available options:
council_admin, council_power_user, council_member, member Example:
"council_power_user"
If false and no role given, sets role to member (deactivated)
Example:
false