Tutorial

Sending Webhooks With Gin

4 min read December 08, 2022

Written by

Daniel Oluojomu
Daniel Oluojomu

Share

Describe Webhooks

Webhooks are messages ( or payload ) sent from an application after the execution of an operation. They are also used to communicate between a chain of services; for example, a payment provider emits webhook events to an e-commerce application’s endpoint after a payment operation. Collectivis can be used to send webhook events from your application to your clients by serving as a reliable egress.

In this article i will show, we will build a Todo API in Go using the Gin HTTP Router Library and use Collectivis to publish webhook events for each operation on our Todo items; create, update & delete.

Prerequisites

To follow along you would need the following

  1. A Collectivis Cloud account.
  2. An Outgoing Project ID & API Key.

For the sake of brevity, we created an additional resource to help with creating user endpoints, usually users will supply this information to you via your dashboard. [2] We have also left out other aspects of the code not necessary for this guide.

API Spec

Our API looks like this:

  • Endpoint

    GET    /endpoints
GET    /endpoints/:id
POST   /endpoint
PUT    /endpoint/:id
DELETE /endpoint/:id

  • Todo

    GET    /todos
GET    /todos/:id
POST   /todos
PUT    /todos/:id
DELETE /todos/:id

Every time we create, update and delete a todo item, we would generate the following events — todo.created, todo.updated, and todo.deleted respectively.

Let’s Build Our API

  1. Project Setup

    mkdir convoy-todo-api && cd convoy-todo-api && go mod init

  2. Endpoints API

    import (
	"net/http"
	"os"

	convoy "github.com/frain-dev/convoy-go"
	"github.com/gin-gonic/gin"
)

type Error struct {
	ErrMsg string `json:"err_msg"`
}

var convoyClient = convoy.New(convoy.Options{
	APIKey:      os.Getenv("CONVOY_API_KEY"),
	APIEndpoint: os.Getenv("CONVOY_API_ENDPOINT"),
	ProjectID:   os.Getenv("CONVOY_PROJECT_ID"),
})

func GetEndpoint(c *gin.Context) {
	endpointID, ok := c.Params.Get("id")
	if !ok {
		c.JSON(http.StatusBadRequest, &Error{ErrMsg: "endpoint id is required"})
		return
	}

	endpoint, err := endpointDB.Find(endpointID)
	if err != nil {
		c.JSON(http.StatusInternalServerError, &Error{ErrMsg: "failed to fetch convoy endpoint"})
		return
	}

	c.JSON(http.StatusOK, endpoint)
}

func AddEndpoint(c *gin.Context) {
	e, err := parseEndpointFromBody(c)
	if err != nil {
		c.JSON(http.StatusBadRequest, &Error{ErrMsg: "failed to read request body"})
		return
	}

	createEndpoint := &convoy.CreateEndpointRequest{
		URL:         e.URL,
		Secret:      e.Secret,
		Description: e.Description,
	}

	resp, err := convoyClient.Endpoints.Create(createEndpoint, nil)
	if err != nil {
		c.JSON(http.StatusInternalServerError, &Error{ErrMsg: "failed to create convoy endpoint"})
		return
	}

	e.ID = resp.UID

	err = endpointDB.Save(e)
	if err != nil {
		c.JSON(http.StatusInternalServerError, &Error{ErrMsg: "failed to save convoy endpoint"})
		return
	}

	c.JSON(http.StatusOK, e)
}

func UpdateEndpoint(c *gin.Context) {
	endpointID, ok := c.Params.Get("id")
	if !ok {
		c.JSON(http.StatusBadRequest, &Error{ErrMsg: "endpoint id is required"})
		return
	}

	update, err := parseEndpointFromBody(c)
	if err != nil {
		c.JSON(http.StatusBadRequest, &Error{ErrMsg: "failed to read request body"})
		return
	}

	updatendpoint := &convoy.CreateEndpointRequest{
		URL:         update.URL,
		Secret:      update.Secret,
		Description: update.Description,
	}

	resp, err := convoyClient.Endpoints.Update(endpointID, updatendpoint, nil)
	if err != nil {
		c.JSON(http.StatusInternalServerError, &Error{ErrMsg: "failed to update convoy endpoint"})
		return
	}

	err = endpointDB.Update(update)
	if err != nil {
		c.JSON(http.StatusInternalServerError, &Error{ErrMsg: "failed to update convoy endpoint"})
		return
	}

	c.JSON(http.StatusOK, e)
}

func DeleteEndpoint(c *gin.Context) {
	endpointID, ok := c.Params.Get("id")
	if !ok {
		c.JSON(http.StatusBadRequest, &Error{ErrMsg: "endpoint id is required"})
		return
	}

	err := convoyClient.Endpoints.Delete(endpointID, nil)
	if err != nil {
		c.JSON(http.StatusInternalServerError, &Error{ErrMsg: "failed to delete convoy endpoint"})
		return
	}

	err = endpointDB.Delete(endpointID)
	if err != nil {
		c.JSON(http.StatusInternalServerError, &Error{ErrMsg: "failed to delete convoy endpoint"})
		return
	}

	c.JSON(http.StatusOK, e)
}

  3. Todos API

    import (
	"encoding/json"
	"net/http"

	convoy "github.com/frain-dev/convoy-go"
	"github.com/gin-gonic/gin"
)

type Todo struct {
	Title       string `json:"title"`
	Description string `json:"description"`
}

func GetTodo(c *gin.Context) {
	todoID, ok := c.Params.Get("id")
	if !ok {
		c.JSON(http.StatusBadRequest, &Error{ErrMsg: "todo id is required"})
		return
	}

	todo, err := todoDB.Find(todoID)
	if err != nil {
		c.JSON(http.StatusInternalServerError, &Error{ErrMsg: "failed to fetch todo"})
		return
	}

	c.JSON(http.StatusOK, todo)
}

func CreateTodo(c *gin.Context) {
	todo, err := parseTodoFromBody(c)
	if err != nil {
		c.JSON(http.StatusBadRequest, &Error{ErrMsg: "failed to read request body"})
		return
	}

	err = todoDB.Save(todo)
	if err != nil {
		c.JSON(http.StatusInternalServerError, &Error{ErrMsg: "failed to save todo"})
		return
	}

	err = sendWebhookEvent("todo.created", todo)
	if err != nil {
		c.JSON(http.StatusInternalServerError, &Error{ErrMsg: "failed to send todo.created event"})
		return
	}

	c.JSON(http.StatusOK, e)
}

func UpdateTodo(c *gin.Context) {
	todoID, ok := c.Params.Get("id")
	if !ok {
		c.JSON(http.StatusBadRequest, &Error{ErrMsg: "todo id is required"})
		return
	}

	update, err := parseTodoFromBody(c)
	if err != nil {
		c.JSON(http.StatusBadRequest, &Error{ErrMsg: "failed to read request body"})
		return
	}

	err = todoDB.Update(update)
	if err != nil {
		c.JSON(http.StatusInternalServerError, &Error{ErrMsg: "failed to save todo"})
		return
	}

	err = sendWebhookEvent("todo.updated", todo)
	if err != nil {
		c.JSON(http.StatusInternalServerError, &Error{ErrMsg: "failed to send todo.udpate event"})
		return
	}

	c.JSON(http.StatusOK, e)
}

func DeleteTodo(c *gin.Context) {
	todoID, ok := c.Params.Get("id")
	if !ok {
		c.JSON(http.StatusBadRequest, &Error{ErrMsg: "todo id is required"})
		return
	}

	err := todoDB.Delete(todoID)
	if err != nil {
		c.JSON(http.StatusInternalServerError, &Error{ErrMsg: "failed to delete todo"})
		return
	}

	err = sendWebhookEvent("todo.deleted", todo)
	if err != nil {
		c.JSON(http.StatusInternalServerError, &Error{ErrMsg: "failed to send todo.deleted event"})
		return
	}

	c.JSON(http.StatusOK, e)
}

func sendWebhookEvent(eventType string, todo *Todo) error {
	data, err := json.Marshal(todo)
	if err != nil {
		return err
	}

	r := &convoy.CreateEventRequest{
		EventType: eventType,
		Data:      data,
	}

	resp, err := convoyClient.Events.Create(r, &convoy.EventQueryParam{
		EndpointID: "<your-endpoint-id>",
	})

	return err

}

Publish Webhook Events

It’s time to publish your first webhook!

  1. To begin, we start our app

    $ go run main.go

  2. Second, we create an endpoint with the cURL command below:

    $ curl --request POST \
	--url "localhost:8000/endpoints" \
	-H "Content-Type: application/json" \
	-d '{
		"user_id": "1",
		"url": "https://webhook.site/f60fa8c4-6f69-4447-bf02-ac5d317aa4ca"
	}'

  3. Finally, we create a Todo item, that in turn generates the webhook item. Let's use the cURL command below:

    curl --request POST \
  --url "localhost:8000/todos' \
  -H 'Content-Type: application/json' \
  -d '{
	  "title": "Complete Laravel Guide",
		"date": "2022-11-28",
		"user_id": "1"
	}'

    The API returns a successful response:

    {
  "id": 4,
  "title": "Complete Go Gin Guide",
  "date": "2022-12-02",
  "user_id": 1,
  "created_at": "2022-12-02T06:16:50.000000Z",
  "updated_at": "2022-12-02T06:16:50.000000Z"
}

Let’s see our event deliveries dashboard.

Deliveries dashboard

Let’s also see our webhooks endpoint

Webhooks.site endpoint page

Appendix

  1. In production environments, Endpoints should be scoped to each user/business/customer or whatever makes sense in your case because at the point of generating webhooks
  2. Users can supply their endpoints through multiple means — your dashboard, the portal link
  3. In this article, we publish webhooks in our controllers, in an ideal production environment, you should publish them from your workers.

Conclusion

Collectivis provides the ability the send webhooks to one endpoint as well as multiple endpoints. In this article, you learned how to send webhooks from a Go Gin API. We hope you enjoyed reading this, and you get to try it out and give us some feedback!

Getting started with Collectivis?

Want to add webhooks to your API in minutes? Sign up to get started.

Related Posts

What I’ve learned from talking to users as a Technical Founder

April 23, 2025

It’s widely accepted that the two most important things a startup needs to get right are building a great product and talking to users. As a technical founder, building has always come naturally to me. Talking to users? Not so much. In this post, i’ll share some of the misconceptions I had about talking to users—and the surprising benefits I’ve discovered from doing it consistently.

Subomi Oluwalana
Subomi Oluwalana

Transactional Outbox: How to reliably generate webhook events

April 17, 2025

In the world of distributed systems, ensuring reliable event delivery is crucial, especially when dealing with webhooks. The transactional outbox pattern has emerged as a robust solution to this challenge. In this post, we'll explore how to implement this pattern to guarantee reliable webhook delivery, even in the face of system failures.

Subomi Oluwalana
Subomi Oluwalana