We are automating the initiation of an Architect flow from an external microservice using the Genesys Cloud REST API. The endpoint is POST /api/v2/flows/executions.
The request payload is straightforward:
{
"flowId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"parameters": {
"customerId": "98765"
}
}
The HTTP status returned is consistently 403 Forbidden. The response body indicates that the user does not have the necessary permissions to execute the flow. We have verified that the OAuth token is generated with the flow:execute scope and the user associated with the token has the flow:admin:execute role.
The Terraform configuration for the user role assignment is applied and confirmed in the UI. State drift checks pass without issue. The flow itself is active and can be triggered manually via the Architect UI without errors.
Is there a hidden dependency or a specific permission on the flow resource itself that prevents programmatic execution? The documentation mentions the scope requirement but does not clarify if flow-level access controls override user roles in this context. We are running this out of the EU-West region.