Can anyone clarify the correct payload structure for the POST /api/v2/scripting/scripts endpoint when injecting dynamic content blocks via a multi-org Premium AppFoundry integration?
We are encountering a 400 Bad Request error with the following response body:
{
"code": "badRequest",
"message": "Invalid script structure. Dynamic content references must be resolved within the tenant context."
}
Our application attempts to push standardized script templates to multiple client organizations using a single OAuth token. The script definition includes dynamic placeholders intended to be resolved at runtime by the Genesys Cloud platform. However, the API validation fails during the initial POST request, suggesting that the platform expects static content or pre-resolved values for dynamic fields in this specific API version.
The integration uses the latest Platform API SDK (v2.0.185) and adheres to the standard script JSON schema. We have verified that the OAuth token has the scripting:manage scope. Is there a specific requirement for dynamic content handling in multi-tenant scenarios that differs from single-org deployments? Or should we be using a different endpoint to handle template-based script distribution?