APIGit Custom Webhooks

At Apigit, we understand that streamlining the lives of developers is essential. To this end, we have a growing list of integrations that are commonly used, and our custom webhooks let developers customize their workflow by triggering actions. This way, we make accessing the necessary data and automating their workflows simple and efficient.

What is a Custom Webhook?

Custom webhooks (also known as web callbacks) are used by applications to connect with other applications to get instant notifications about an update or an event that is being monitored. However, unlike regular API calls that pull data at regular intervals, webhooks allow you to get real-time updates.

Apigit Custom Webhooks

Webhooks are available on the Enterprise plan. To create a webhook for your repository, open the Settings tab of your repository, go to Webhooks and click Add WebHook.

To understand how webhooks work, follow these steps:

1. Publish a mock server using Apigit.
2. Fill the Remote Url field with the URL of the mock server.
3. Monitor the Logs view of the mock server for any changes made in your repository.

Here is part of the request that arrives when an issue is opened.

Content-Type: application/json
X-Gitea-Delivery: 3fdcd42d-5bcb-45c5-b01a-27a2e5e23b00
X-Gitea-Event: issues
X-Gitea-Signature: <sha256 signature>
X-Gogs-Delivery: 3fdcd42d-5bcb-45c5-b01a-27a2e5e23b00
X-Gogs-Event: issues
X-Hub-Signature-256: sha256=<sha256 signature>
X-GitHub-Delivery: 3fdcd42d-5bcb-45c5-b01a-27a2e5e23b00
X-GitHub-Event: issues

{
  "action": "opened",
  "number": 5,
  "issue": {
    "number": 5,
    "title": "5",
    "body": "5",
    "state": "open"
  },
  "repository": {
    "name": "test",
    "full_name": "xx/test",
    "private": true
  },
  "sender": {
    "login": "xxxx"
  }
}

See Webhooks for the details.