API reference / Messaging
post
/v2/messaging/{provider}/inboundInbound messaging callback (STOP / START)
- Operation
messagingInboundWebhook- Authentication
- None — public
Called by the messaging provider, not by partners. **Unauthenticated** — Twilio cannot present a Haavisa API key, so the request is authenticated by its `X-Twilio-Signature` header instead. The endpoint fails closed: without `TWILIO_AUTH_TOKEN` and `PUBLIC_API_URL` there is no way to verify the signature, and an unverified request may not change a consent record.
Only `OptOutType` of STOP or START is recorded — Twilio sends its own confirmation reply, so this endpoint answers 200 and sends nothing. Redeliveries are deduplicated on the message sid.
Request
Parameters
providerpathrequiredstringResponses
200Acknowledged. `recorded` says whether a consent change was stored.
receivedbooleanrequiredrecordedbooleanrequired400Signature verification failed, or the signature could not be checked.
errorobjectrequiredExample
curl -X POST https://api.haavisa.com/v2/messaging/<provider>/inboundSomething unclear? The eligibility guide explains the model behind the answers; the errors guide covers the envelope.