Skip to main content
An agency often needs the client’s yes before a change goes out, and the client should not need an Attensira account to give it. The client reviewer link is that yes.

​
What the reviewer sees

There is one link per workspace. Whoever holds it can see that workspace’s suggested changes: what the change is, why, where it lands, the current and proposed text, and the source links (only http and https links are shown). For each one they can approve, or decline with a reason: wrong, not now, already done, or never touch this. They cannot see settings, billing, analytics, tasks, outreach contacts, or any other workspace.

​
Creating and revoking it

Create it from the workspace’s card on Clients, under Client link.
  • The link is valid for 90 days.
  • New link replaces it. The old link stops working immediately.
  • Turn off revokes it.
It is separate from the shared receipt link. Rotating either one does not affect the other.

​
What an approval does

An approval through the link is the same approval as one in the workspace, recorded as Client reviewer (shared link) so you can tell who said yes.
  • Approvals are refused when the org’s credits are used up.
  • Declines always go through.

​
Over the API

Dashboard routes (signed-in session):
  • GET, POST and DELETE /v2/projects/{id}/reviewer-link read, create or replace, and revoke the link. Each answers {active, token?, url?, issued_at?, expires_at?}.
Public routes, where the token is the credential:
  • GET /v1/review/{token}: the suggested changes.
  • POST /v1/review/{token}/items/{itemId}/approve
  • POST /v1/review/{token}/items/{itemId}/decline with {"reason": "wrong" | "not_now" | "already_done" | "never_touch"}.
These review routes are not MCP tools.