Send Review Requests from Any App with Inbound Webhooks
Any tool that can POST JSON to a URL can add contacts to a review campaign. Forms, booking systems, CRMs, point-of-sale software and your own code all use the same endpoint, and EmbedMyReviews sends the request by SMS or email at the time you choose.
The endpoint lives on your own white-label domain. Send one test, map the fields visually, and activate.
POST https://reviews.youragency.com/api/webhooks/inbound/•••••
Content-Type: application/json
{
"name": "Sarah Kim",
"email": "[email protected]",
"appointment_end": "2026-09-12T15:45:00-07:00"
}Sends 2 hours after the appointment ends. "Hi Sarah, thanks for coming in today. Would you share a quick review?"
How It Works
Four steps in the setup wizard. The endpoint URL is generated for you, and the mapping is built from a real test submission.
Name the connection and choose a campaign
Give the connection a name your team will recognise and pick the review campaign that incoming contacts join.
Paste the URL and send a test
Copy the endpoint URL into your app's webhook settings and send one request. The payload is captured so you can map from real data.
Map fields
Point first name, last name or full name, email and phone at the matching fields. Email or phone is required. Optionally map an appointment or order date.
Choose when to send
Straight away, a set time after the anchor date, or the next morning at a chosen time. Then activate.
What triggers a request, and how it is timed
The trigger is whatever your app sends. EmbedMyReviews does not define event names for inbound webhooks, so a form submission, a closed job or a completed sale all look the same at the endpoint.
Built for Tools That Have No Dedicated Integration
If the software can send a webhook, it can start a review request. No automation platform sits in the middle unless you want one.
Practice and booking software
Clinic, salon and studio systems that fire a webhook on appointment completion. Map the end time and the request follows the visit.
Point of sale and payments
POS platforms with webhook support send the buyer's details after a sale. The contact joins the campaign the same minute.
Form builders
Gravity Forms, Typeform, Jotform and similar tools can post each submission to a URL. Name, email and phone map in seconds.
Field-service and job management
When a job is closed in your dispatch system, its webhook can ask the customer for a review that evening or the next morning.
In-house systems and custom code
A single POST from your own application is enough. No SDK, no API token to manage, and an optional signing secret when you want it.
Agencies with mixed client stacks
Each client gets its own connection and endpoint under its own account, whatever software they run. Nothing is shared between clients.
Integration Features
One inbound engine behind the generic endpoint and every automation-platform preset.
Endpoint on your own domain
The URL is built from your white-label domain. Whoever configures the sending app sees your platform, not a third party.
Test-payload capture and visual mapping
Send one request and pick fields from what arrived. Nested values use dot-notation paths, and a single full-name field is split into first and last automatically.
Date-anchored timing
Straight away, 15 minutes to 7 days after the appointment or order date, or the next morning at a chosen time. Without a mapped date, the delay runs from arrival.
Signing secret and instant token rotation
Add an optional HMAC-SHA256 signing secret so only your app can post. Regenerate the endpoint token at any time and the old URL stops immediately.
Presets for automation platforms
Zapier, Make, n8n and Pabbly Connect presets use this same engine with guided steps written for each platform's HTTP action.
Lost-job recovery
A request anchored to a date weeks away sits in the queue for a long time. Every six hours, any send that went missing is re-dispatched from the stored record.
Technical details
The endpoint is deliberately plain so that any HTTP client can reach it. You need a configured domain on the EmbedMyReviews account and a review campaign with SMS or email set up through your own provider.
- POST with a JSON body. Form-encoded bodies are accepted as well.
- Maximum body size 256 KB.
- Optional X-Webhook-Signature header: hex HMAC-SHA256 of the raw body using the signing secret. If you also send X-Webhook-Timestamp (Unix seconds), sign
timestamp.bodyinstead. Timestamps more than 5 minutes from the server clock are rejected. - An identical payload received again within 5 minutes is treated as a sender double-fire and ignored.
- The endpoint URL is built from your primary domain, and the token in the path can be regenerated at any time.
curl -X POST https://reviews.youragency.com/api/webhooks/inbound/••••• \
-H "Content-Type: application/json" \
-H "X-Webhook-Signature: $SIG" \
-d '{"name":"Sarah Kim","email":"[email protected]","phone":"+14155550142"}'Inbound, not outbound
Inbound webhooks let other apps push contacts into a review campaign. Outbound webhooks are the reverse: EmbedMyReviews pushes review events out to your systems, such as a new review arriving. The REST API covers both directions with authenticated calls.
REST API, outbound webhooks and MCPYour providers. Wholesale rates.
Review requests triggered by inbound webhooks are sent through your own Twilio (SMS) or SMTP (email) accounts. You pay wholesale rates directly, with no EmbedMyReviews markup on messaging.
Common questions
What is the difference between inbound and outbound webhooks?
Inbound webhooks are covered on this page: another app sends a POST to an endpoint on your domain, and the contact in that payload is added to a review campaign. Outbound webhooks run the other way: EmbedMyReviews sends an event to a URL you own when something happens on the review side, such as a new review arriving. Outbound webhooks and the REST API are documented on the API and Webhooks page.
What must the payload contain?
At minimum an email address or a phone number. Name fields are optional but recommended so the request can be personalised, and a single full-name field is split into first and last automatically. You do not need to match any field names: send one test and map whichever fields your app already uses, including nested values addressed with dot-notation paths. Submissions with neither an email nor a phone are logged as skipped.
How do I time the request around an appointment?
Map a date field from the payload as the appointment or order date. The delay you choose, from 15 minutes up to 7 days, or the next morning at a set time, is then measured from that moment rather than from when the request arrived. Fields such as end_time, appointment_date, completed_at and order_date are suggested automatically when the test payload contains one. If a later submission is missing the field, the arrival time is used instead.
Can I secure the endpoint?
Yes. The token in the URL is unguessable and can be regenerated at any time, which stops the old URL immediately. For a stronger guarantee, add a signing secret and have your app send an X-Webhook-Signature header containing the hex HMAC-SHA256 of the raw body. If you also send an X-Webhook-Timestamp header, sign the timestamp and body joined by a dot; timestamps more than 5 minutes old are rejected. Requests that fail the check are refused.
Does the client see EmbedMyReviews branding?
No. The endpoint URL is built from your own domain, and the setup instructions the client follows live on your white-label dashboard. Nothing in their form builder, booking system or POS references a third party.
Which platforms have presets?
Zapier, Make, n8n and Pabbly Connect. Each preset uses this same inbound engine and the same four-step wizard, with guidance written for that platform's HTTP action. If your tool is not on the list, use the generic connection on this page: any app that can send a POST will work.
Related integrations
Zapier
Guided steps for Webhooks by Zapier on paid Zapier plans.
Make
Guided steps for the HTTP module on every Make plan, including free.
n8n
Guided steps for the HTTP Request node, cloud or self-hosted.
Pabbly Connect
Guided steps for the API by Pabbly action in any workflow.
API & Webhooks
The REST API, outbound webhooks for review events, and the MCP server.
All Integrations
CRMs, calendars, payments, and automation platforms.
Point any app at one URL and let it ask for the review.
Included in the flat $99/month plan for unlimited clients and connections. No per-connection fees.
No credit card required. Explore the platform for 14 days.