curl --request POST \
--url https://{domain}/wp-json/sagescreen/v1/intake/set-ticket \
--header 'Content-Type: application/json' \
--header 'X-API-Key: <api-key>' \
--data '
{
"intake_item_id": 4821,
"ticket_id": "TKT-00312",
"ticket_url": "https://support.sagescreen.com/tickets/312"
}
'{
"success": true,
"data": {
"intake_item_id": 4821,
"ticket_id": "TKT-00312",
"ticket_url": "https://support.sagescreen.com/tickets/312",
"status": "intake_escalated",
"new_owner_id": 5
}
}Intake
Set ticket info on an intake item
Called by Zapier after a support ticket is created or updated. Can set ticket ID/URL, change status, and reassign the owner — all in a single call.
Requires the X-API-Key header (Zapier API key from plugin settings).
POST
/
intake
/
set-ticket
curl --request POST \
--url https://{domain}/wp-json/sagescreen/v1/intake/set-ticket \
--header 'Content-Type: application/json' \
--header 'X-API-Key: <api-key>' \
--data '
{
"intake_item_id": 4821,
"ticket_id": "TKT-00312",
"ticket_url": "https://support.sagescreen.com/tickets/312"
}
'{
"success": true,
"data": {
"intake_item_id": 4821,
"ticket_id": "TKT-00312",
"ticket_url": "https://support.sagescreen.com/tickets/312",
"status": "intake_escalated",
"new_owner_id": 5
}
}Authorizations
Zapier API key stored in ss_zapier_api_key option
Body
application/json
intake_item_id and at least one action field must be provided.
WordPress post ID of the intake item
Example:
4821
Support ticket ID to store
Example:
"TKT-00312"
Support ticket URL to store
Example:
"https://support.sagescreen.com/tickets/312"
Custom post status for ss_intake_item
Available options:
intake_open, intake_done, intake_escalated Support-tool numeric status. Mapped to IntakeStatus:
4 or 5 → intake_done, anything else → intake_escalated.
Ignored if status is also provided.
Example:
4
WordPress user ID to reassign to
Example:
5
Email to look up the new owner user
Example:
"jane@example.com"