Issue
You have encountered a 403 Forbidden error when triggering or updating a workflow via the API, even when using an API key with the Admin (Full Access) role.
Explanation
This error occurs when the Workflow is configured with run restrictions, meaning it can only be triggered or updated by users (or API keys) assigned specific custom roles. Only API keys or users that have one of those roles can interact with the workflow - even Admin-level keys are blocked if they don’t exactly match one or more of the assigned custom roles.
Solution
Use one of the following options:
Option 1: Create a new API key and assign it one (or more) of the custom roles assigned to this Workflow.
Option 2: Use a Personal Access Token (PAT) in place of an API key from a user who already has one of the required custom roles.
Once the key or token matches a role in the restriction list, the 403 error will be resolved.