You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use the REST API to interact with workflows in GitHub Actions
You can use the REST API to view workflows for a repository in GitHub Actions. Workflows automate your software development life cycle with a wide range of tools and services.
These endpoints are available for authenticated users, OAuth Apps, and GitHub Apps. Access tokens require repo scope for private repositories and public_repo scope for public repositories. GitHub Apps must have the actions permission to use these endpoints. For more information, see REST-API-Workflows.
Create a workflow dispatch event
You can use this endpoint to manually trigger a GitHub Actions workflow run. You can replace workflow_id with the workflow file name. For example, you could use main.yaml.
Header parameters
Info
Required
access_token
Github Access token. Access tokens require repo scope for private repositories and public_repo scope for public repositories.
Yes
Path parameters
Info
Required
owner
The account owner of the repository. The name is not case sensitive.
Yes
repo
The name of the repository without the .git extension. The name is not case sensitive.
Yes
workflow_id
The ID of the workflow. You can also pass the workflow file name as a string.
Yes
Body parameters
Info
Required
ref
The git reference for the workflow. The reference can be a branch or tag name.
Yes
inputs
Input keys and values configured in the workflow file. The maximum number of properties is 10. Any default properties configured in the workflow file will be used when inputs are omitted.