Skip to main content

Possibility to validate the origin of requests via webhook

As of today, at least I have not found a way for the webhooks sent by rebill to be authenticated with any signature or hash.

As equivalent comparisons, MercadoPago includes an x-signature header which allows to validate that the incoming request is officially from MercadoPago. It would improve a little more the security of webhooks that are usually unprotected.

Another alternative would be to be able to configure headers from the Dashboard and have Rebill resend them when sending notifications via webhook. This way, each user could include an x-api-key header, for example, and keep the endpoints protected.

Nowadays, the only alternative I found was to include a signature in the "metadata" attribute of the body of some endpoints, for example, to create a payment link for a subscription. Maybe there is something that I did not see in the documentation, so I would be grateful if you could share this information with me.

3 comments

Log in to comment and vote

Comments3

  • Nahuel Candia

    Team•

    Nov 29, 2025

    Today we offer a validation over IP:

    https://docs.rebill.com/guides/webhooks#security-and-validation
    Would you add a custom header anyways?

    • Marcos Sequeira

      •

      Nov 29, 2025

      Sí, vi esa validación extra y la posibilidad de agregar un WAF en la infra de quién consume Rebill para habilitar o no peticiones de esas ips. El problema es que quedás atado a posibles cambios de infra de parte de Rebill.

      Colocando un header customizable por cliente o un signature entre una llave privada y pública, compartida automáticamente por rebill en su dashboard, podría ser más flexible.

      • Nahuel Candia

        Team•

        Nov 30, 2025

        Muchas gracias por el feedback, vamos a revisar cuando es el mejor momento para implementarlo.