The short version
- Send review requests and read your Google reviews from your own code or Zapier.
- Hear about every new Google review the minute it comes in, with signed webhooks.
- Connect Housecall Pro, GoHighLevel or HubSpot with no code, and Jobber through Zapier.
Quick start
Make a key in reviewwed under Settings, Developers, API keys. Send it as a bearer token. Everything is JSON.
curl https://dash.reviewwed.co/api/v1/google-reviews \
-H "Authorization: Bearer vrk_your_key" The base address is https://dash.reviewwed.co/api/v1.
Keys
A key works as the person who made it, and only while they still have access and the account is on a paid plan. Remove it under Settings, Developers and it stops at once. Keep keys private, like a password.
When a key opens more than one business, pass business (the business's link name, like brightside-plumbing) with each call. GET /businesses lists them.
| Call | What it does |
|---|---|
GET /me | Who the key belongs to, and its businesses with their Google rating. |
GET /businesses | Every business the key can use. |
Google reviews
| Call | What it does |
|---|---|
GET /google-reviews | The business's Google reviews, newest first. limit up to 100. |
{
"id": "k3x9q2m7a1b4c8d0",
"author": "Dana Kim",
"rating": 5,
"text": "Marco found the leak in ten minutes and cleaned up after.",
"reply": null,
"review_url": "https://www.google.com/maps/reviews/…",
"reviewed_at": "2026-11-17T17:00:00.000Z",
"dashboard_url": "https://dash.reviewwed.co/reviews?open=k3x9q2m7a1b4c8d0"
}
Review requests
Each request goes out from one of the business's campaigns, by email, by SMS on plans with SMS, or both, with the campaign's reminders. Anyone who already reviewed, was asked in the last 30 days, or opted out is skipped. Email requests are capped at 200 a day per location.
| Call | What it does |
|---|---|
POST /requests | Send one. name, and email or phone (or both). Optional campaign (its link name); leave it out for the first campaign that's on. |
GET /requests | Newest first, with status: scheduled, sent, opened, clicked, reviewed or failed. |
GET /requests/{id} | One request. |
POST /requests/{id}/remind | One reminder now (or a retry, for one that failed). |
curl -X POST https://dash.reviewwed.co/api/v1/requests \
-H "Authorization: Bearer vrk_your_key" \
-H "Content-Type: application/json" \
-d '{ "name": "Dana Kim", "email": "[email protected]", "phone": "+16195550142", "campaign": "after-every-job" }'
Campaigns and stats
| Call | What it does |
|---|---|
GET /campaigns | The business's campaigns, with their link names and whether each is on. |
GET /stats | Pass days to choose how far back (default 30). Requests sent, opened and reviewed. |
Webhooks
Add an address under Settings, Developers, Webhooks (or POST /webhooks with url and events). We POST JSON to it when:
google_review.new: a new Google review came in.request.sent: a review request went out.request.opened: a customer opened their request for the first time.
{ "id": "evt_123", "type": "google_review.new", "created": "…", "business": { "id": "…", "name": "Brightside Plumbing", "slug": "brightside-plumbing" }, "data": { …the review… } } Every body is signed. Check the signature header t=<seconds>,v1=<hex>: the HMAC-SHA256 of <t>.<body> with your webhook's secret.
const [t, v1] = header.split(',').map((p) => p.split('=')[1])
const ok = crypto.createHmac('sha256', secret).update(`${t}.${rawBody}`).digest('hex') === v1 Answer with any 2xx. Failures retry for a day (1 minute, 5, 30, then hours apart). After 50 failures in a row the webhook turns off; Send a test turns it back on.
Zapier
Connect reviewwed in Zapier with an API key. Triggers: New Google Review (you can pick which stars) and Review Request Opened. Action: Send Review Request, from the campaign you pick. That covers Jobber, ServiceTitan, Square, Google Sheets, Slack and thousands more apps.
Job software and CRMs
No code needed: connect your software in a campaign's Integrations, then pick what sends a request. When it fires, the customer is asked at the right time, with the campaign's reminders.
| Software | Sends a request when |
|---|---|
| A job is complete | |
| An opportunity is marked Won, or reaches a stage | |
| A deal reaches a stage | |
| A job is closed, or an invoice is paid |
Only jobs and deals from after you turn it on count, so nobody from before gets a request. Using something else? Connect it through Zapier.
Errors and limits
Errors come back as { "error": { "status": 400, "message": "…" } } with a message you can show a person.
| Status | Means |
|---|---|
| 400 | Something in the call is missing or wrong; the message says what. |
| 401 | Missing, unknown or removed key. |
| 403 | The account isn't on a paid plan. |
| 404 | No such request, campaign or call. |
| 409 | Not possible right now, like SMS asked for on a plan without it. |
| 422 | The day's limit is reached. |
| 429 | More than 120 calls a minute on one key. |