Store test screen ID during build
Sage – REST
Store test screen ID during build
Called by the Python service during the transcending_training
build step to store the test screen ID created for the sage.
The front-end polls for this value via sagescreen_get_step_status
and uses it to embed the test screen.
Requires the X-API-Key header matching the stored
sage_screen_api_key option.
GET
Store test screen ID during build
Authorizations
SageScreen API key stored in ss_zapier_api_key option
Query Parameters
Python council_sage UUID
Example:
"a1b2c3d4-e5f6-7890-abcd-ef1234567890"
Test screen ID created by Python
Example:
"scr_abc123def456"