IVR HTTP Request Node: Call Your API on Any Step

HTTP Request settings

Tokens you can use

Headers on every request

X-Edesy-Signature (sha256=<hex>), X-Edesy-Timestamp, X-Edesy-Idempotency-Key (the same value for the same visit to a step, so you can drop duplicates), X-Edesy-Call-Sid and User-Agent: edesy-ivr/1.0.

import hmac, hashlib, time

def verify(headers, raw_body: bytes, secret: str) -> bool:
    ts = headers["X-Edesy-Timestamp"]
    expected = "sha256=" + hmac.new(secret.encode(), ts.encode() + b"." + raw_body, hashlib.sha256).hexdigest()
    return abs(time.time() - int(ts)) < 300 and hmac.compare_digest(expected, headers.get("X-Edesy-Signature", ""))

Example flow: order confirmation by keypress

This is the Order confirmation (API + HTTP) template:

1. Play your recorded message, then Menu: "To confirm order {{var.order_id}}, press 1. To cancel, press 2. To speak to an agent, press 3."
2. Key 1: HTTP Request POST https://api.example.com/orders/{{var.order_id}}/confirm, then Say "Thank you. Your order {{var.order_id}} is confirmed."
3. Key 2: HTTP Request POST .../cancel, then Say "Your order {{var.order_id}} has been cancelled."
4. Key 3: Transfer to an agent. Timeout: Hangup.

Switch the cancel request to Wait for response and you can add a Failure branch that says "Please try again later".

Limits and safety

• Up to 20 requests a second per workspace; rendered body up to 16 KB; up to 64 KB of the response is read.
• At most 5 sync requests, and 4 seconds in total, between two caller interactions.
• Redirects are not followed, requests to private or internal addresses are refused, and secret-looking header values are masked in logs.
• The signing secret can be rotated in the portal.