Error notifications
Find out why a location stopped collecting reviews or posting responses, and track what you've done about it.
Find out why a location stopped collecting reviews or posting responses, and track what you've done about it.
When something breaks — a site connection expires, a saved login stops working, a URL goes dead, a site starts rate-limiting us — an error notification is created for the affected location. This page lists them, lets you read the details, add notes as you work them, and mark them resolved. Think of it as the inbox for connection problems across every location you manage.
Most problems are fixed by sending the owner a new connection link (Connect review sites) or updating the URL. The notification tells you which. If you'd rather be pushed than poll, subscribe to the connection events on Webhooks; they carry the same reason text.
You'll need a partner token.
Prerequisites
- A bearer token in the
Authorizationheader. Any endpoint that needs no token says so on its own page. - The id of each record the call targets. Every endpoint page lists the ids it needs.
Errors
| Status | Meaning |
|---|---|
401 | The bearer token is missing, expired or invalid |
403 | The token is valid but the record sits outside your account |
422 | The request failed validation — the response names the fields |
500 | Unexpected server error |
Individual endpoints may return more; each page lists its own.
Endpoints
GET — Get the current problems across your locations: which location, which site, what went wrong, when, and whether it's been looked at.
GET — Get everything about a single problem: the error, the affected location and site, history, and notes.
POST — Change the status of one or many problems at once.
POST — Send the details of a problem by email, to your team or to the affected business owner.
Updated 17 days ago
