Sign in

Webhook (inbound from provider)

POST https://{organization}.myguper.com/api/sender/webhook/{token}

Inbound webhook endpoint that providers (Twilio, SendGrid, WhatsApp Business, etc.) post delivery/status callbacks to. The token in the URL is a Guper-issued JWT that carries { o: organization, d: dispatcher_id } — it authenticates the caller without an x-guper-authorization header (providers can't sign requests on our behalf).

The handler validates the JWT, checks that the organization in the token matches the subdomain, enqueues the raw payload in webhook_queue for asynchronous processing, and returns 200 immediately. Actual status-event handling happens out-of-band in a worker.

Try-it values populated from environment ACME (Demo)


Authentication

Jwt

Bearer-style JWT carried in the URL path. Issued by Guper when the provider integration is set up.

Headers

Name Type Description
Content-Type * string Always `application/json` for endpoints that accept a JSON body.

Path parameters

Name Type Description
token * string JWT issued at integration setup. Carries `o` (organization) and `d` (dispatcher id).

Request body

Content-Type: application/json

Responses

{ "ok": true }
Copied to clipboard