New to VisionScaper?
Start here
Help Center › Marketing & messaging › Incoming message webhook addresses
Incoming message webhook addresses
Every webhook address VisionScaper gives your text and email services, and where to find each one.
A webhook is an address VisionScaper listens on. Your text or email service calls it when a customer replies, a message is delivered, or an email bounces. This is a technical article for the site administrator.
All addresses start with your site’s REST address (your site URL plus /wp-json/). The code uses the namespace dreamscaper/v1.
The addresses
| Service | Address ends with | Where VisionScaper shows it |
|---|---|---|
| Twilio texts | dreamscaper/v1/crm/twilio |
Settings → VisionScaper, numbered Twilio list |
| Telnyx texts and events | dreamscaper/v1/msg/webhook/telnyx |
Settings → VisionScaper Messaging, Webhook address |
| Postmark email events | shown on the page as Postmark webhook | Settings → VisionScaper Marketing |
| Resend, SendGrid, Amazon SES | dreamscaper/v1/msg/webhook/resend, /sendgrid, /ses |
Built from the same pattern (the Messaging page lists only the Telnyx one) |
| Twilio missed-call voice | dreamscaper/v1/crm/voice |
Settings → VisionScaper Marketing, Missed-call text-back |
| AI Receptionist voice engines | dreamscaper/v1/receptionist/webhook/ENGINE |
Settings → VisionScaper AI Receptionist |
| AI Receptionist phone number | dreamscaper/v1/receptionist/voice |
Settings → VisionScaper AI Receptionist |
For the receptionist, ENGINE is retell, vapi or bland. Postcards have their own address, shown in Grow → Postcards → Settings.
Steps
- Copy the address from the screen listed above. Do not type it by hand.
- Paste it into your provider’s webhook setting. Follow the provider’s current instructions for where that is.
- Choose the events to send. For Postmark, tick Delivery, Bounce, Spam Complaint and Subscription Change.
- Where VisionScaper asks for a webhook secret, enter the same secret on both sides.
How the checks work
- Twilio requests are checked with Twilio’s signature using your Auth Token.
- The
msg/webhookaddresses check a headerx-ENGINE-signature(for examplex-telnyx-signature). The value must be the hex SHA-256 HMAC of the raw request body, made with the saved webhook secret. A missing secret or header always fails with “Bad signature.” The source says this is a generic stand-in and each provider’s own scheme is not implemented. Not verified against live provider traffic. - Each event is saved once. A repeated delivery is acknowledged and ignored, so nothing is counted twice.
What the events do
- delivered: the message shows as delivered.
- failed: shows “The carrier couldn’t deliver it”.
- bounced: the customer’s email is marked bounced.
- complained or unsubscribed: the customer is opted out of email.
- inbound text: logged on the customer, you get an alert “Text from (name)”, and the reply rules run.
If something goes wrong
- 403 “Bad signature”: the secret or header is wrong.
- Nothing arrives: your site must be reachable from the internet. A site behind a password or firewall will not receive webhooks.