curl --request POST \
--url https://{domain}/wp-json/sagescreen/v1/callback/build-complete \
--header 'Content-Type: application/json' \
--header 'X-API-Key: <api-key>' \
--data '
{
"council_sage_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"status": "success"
}
'{
"success": true,
"message": "Sage build completed successfully",
"sage_id": 1234
}Sage – REST
Python build-complete callback
Called by the Python workflow service when a sage build finishes (success or failure).
On success: deducts credits from council ledger, advances sage to step 5, clears build flags, and sends a completion email.
On failure: rolls back sage to step 3 and clears build flags so the user can retry.
Requires the X-API-Key header matching the stored
sage_screen_api_key option.
POST
/
callback
/
build-complete
curl --request POST \
--url https://{domain}/wp-json/sagescreen/v1/callback/build-complete \
--header 'Content-Type: application/json' \
--header 'X-API-Key: <api-key>' \
--data '
{
"council_sage_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"status": "success"
}
'{
"success": true,
"message": "Sage build completed successfully",
"sage_id": 1234
}Authorizations
SageScreen API key stored in ss_zapier_api_key option
Body
application/json