GET
POST
GET
PATCH
DELETE
GET
POST
GET
DELETE
PUT
DELETE
GET
GET
GET
PUT
DELETE
GET
POST
DELETE
GET
PATCH
DELETE
GET
POST
DELETE
GET
PATCH
DELETE
GET
POST
PUT
DELETE
GET
DELETE
GET
POST
PUT
DELETE
GET
POST
PUT
DELETE
GET
POST
PUT
DELETE
POST
GET
GET
PUT
DELETE
GET
GET
GET
PATCH
DELETE
GET
GET
GET
POST
GET
GET
GET
GET
GET
GET
GET
PUT
DELETE
GET
GET
POST
GET
DELETE
GET
POST
GET
POST
GET
GET
PUT
DELETE
GET
POST
GET
POST
GET
PATCH
DELETE
GET
PATCH
GET
GET
POST
POST
POST
GET
PATCH
DELETE
GET
POST
GET
DELETE
GET
PUT
DELETE
POST
POST
GET
POST
PUT
DELETE
GET
POST
GET
GET
GET
GET
GET
GET
POST
GET
PATCH
DELETE
POST
GET
GET
GET
PATCH
DELETE
GET
POST
GET
GET
GET
GET
GET
POST
GET
GET
GET
GET
PUT
GET
GET
GET
GET
POST
GET
PUT
DELETE
GET
POST
GET
GET
POST
GET
PATCH
DELETE
GET
You can use this endpoint to trigger a webhook event called repository_dispatch
when you want activity that happens outside of GitHub to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the repository_dispatch
event occurs. For an example repository_dispatch
webhook payload, see "RepositoryDispatchEvent."
The client_payload
parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the client_payload
can include a message that a user would like to send using a GitHub Actions workflow. Or the client_payload
can be used as a test to debug your workflow.
This endpoint requires write access to the repository by providing either:
repo
scope. For more information, see "Creating a personal access token for the command line" in the GitHub Help documentation.metadata:read
and contents:read&write
permissions.This input example shows how you can use the client_payload
as a test to debug your workflow.