Skip to main content

Webhook

Updates to monitoring topics will be notified through webhook deliveries. To enable this, it is necessary to configure—through the support team—an endpoint address where we will send update notifications, as well as a signature_key that will be used to sign the request. It is important to note that all webhook deliveries will be sent to a single endpoint.

Attention

For security reasons, all Webhook requests will only be made to endpoints served over HTTPS.

Webhook Signature

To guarantee that the request received at your endpoint came from our servers, we send an HMAC signature in the Signature header. You recompute that signature on your side and compare it with the one received — if they match, the request is trustworthy.

How the signature is computed

Signature = HMAC-SHA1(signature_key, endpoint + method + payload) → hexadecimal

The three components are concatenated in this order, with no separator:

ComponentWhat it is
endpointThe full URL of your webhook, exactly as configured with support (including https:// and any query string).
methodThe HTTP verb in uppercasePUT for these notifications.
payloadThe request body exactly as received, byte for byte.
signature_keyThe secret you agreed on with support (also called secret_token). It is the HMAC key, not part of the message.
Use the raw body, never re-serialized JSON

The signature is computed over the exact bytes of the body. If you deserialize the JSON and serialize it again before validating, key order and whitespace change, and the signature will never match.

Read the body as a raw string/bytes first, validate the signature, and only then parse it. In the examples below this appears as request.get_data(), file_get_contents('php://input'), express.raw() and so on.

Accented characters in the payload

The body is serialized with ensure_ascii=False, meaning accented characters are sent as literal UTF-8 ("João") rather than escaped. Treat the body as UTF-8 when computing the HMAC — this is the default in every language below, but it is the most common cause of a mismatched signature when a field contains an accent.

Validation examples

import hashlib
import hmac

SIGNATURE_KEY = "YOUR_SECRET_TOKEN"
WEBHOOK_URL = "https://seu-dominio.com/webhooks/qitech"
HTTP_METHOD = "HTTP_VERB" # see the table above


def calculate_signature(endpoint: str, method: str, payload: str) -> str:
hmac_obj = hmac.new(
SIGNATURE_KEY.encode("utf-8"),
(endpoint + method + payload).encode("utf-8"),
hashlib.sha1,
)
return hmac_obj.hexdigest()


def is_valid(received_signature: str, raw_body: str) -> bool:
expected = calculate_signature(WEBHOOK_URL, HTTP_METHOD, raw_body)
# compare_digest prevents timing attacks
return hmac.compare_digest(expected, received_signature)


# Exemplo com Flask
from flask import Flask, request

app = Flask(__name__)


@app.route("/webhooks/qitech", methods=[HTTP_METHOD])
def receive_webhook():
raw_body = request.get_data(as_text=True) # raw body, no parsing
received = request.headers.get("Signature", "")

if not is_valid(received, raw_body):
return "", 401

event = request.get_json() # parse only after validating
print(event)
return "", 200
Signature not matching? Check in this order
  1. Was the body re-serialized? This is the most frequent cause. Use the raw body.
  2. Is the URL identical? A trailing slash added or removed changes the signature. Use exactly the URL configured with support.
  3. Is the method correct and uppercase? For these notifications it is PUT.
  4. Is the concatenation order right? It is endpoint + method + payload, in that order.
  5. Is the digest lowercase hexadecimal? It is not Base64.

Retries

The notification is considered successfully delivered when an HTTP 200 status is returned. If delivery fails, up to 7 retry attempts will be made with the following intervals, until a 200 response is received or all attempts are exhausted:

  • 10 seconds
  • 40 seconds
  • 160 seconds
  • 640 seconds
  • 2560 seconds
  • 10240 seconds
  • 40960 seconds