Help Center
Account, agencies & API

Setting up API access

For anyone connecting a shop, a till or their own software to Reputify: one access token per program, with only the rights it needs.

Who is this article for? For you if another program should work with Reputify automatically – for example your shop or till system, your own software or a reporting tool – and you are setting up access for it that your developer or service provider will enter. The technical part further down is meant for them.

For WordPress you do not need any of this: there is a ready-made way without keys, see The WordPress plugin.

What is an access token?

An access token (also called an API key) is a long, random password for a program. The program presents it with every request; from it, Reputify knows who is asking and what they may do. The API is the interface through which programs talk to Reputify. There are two kinds of tokens:

KindStarts withCanWhere to issue
Team tokenrpf_live_whatever the ticked rights allowAPI Access → API Keys (page “API & integrations”)
Survey tokenrpf_inv_only invite to this one survey – read nothing, delete nothingin the review survey, tab Integration (every plan)

Before you start

  • You are the owner or an admin of the team. Other roles do not see the API Keys menu item – issuing a token opens a door into your account.
  • For most rights (reading reviews, projects and analysis, replying) you need at least the Pro plan. Embeds, seals and invitations work on every plan.
  • For a survey token: a review survey where, under Wie kommen die Leute zur Bewertung? (How do people get to the review?), the access Aus meinem System (Shop, Kasse, MCP) (From my system) is ticked (see Collecting reviews with surveys).

1. Issue a team token

  1. In the sidebar on the left, right at the bottom under API Access, click API Keys. The API & integrations page opens. (Where the sidebar is: Finding your way around Reputify.)
  2. On the right under New token, enter under Name (2 in the screenshot) what the token is for, for example “Reporting export” or “Till system Graz branch”. Only you will see the name.
  3. Under Rights, tick only what the program really needs. If in doubt, ask your developer. Rights your plan does not include are marked “Your plan does not cover this.”
  4. Optional: under Valid for (days), enter how long the token should be valid. Empty means no expiry.
  5. Click Issue.
  6. The token now appears once only, with the note “Copy it now — it cannot be shown again”. Copy it and pass it on to your developer securely. Then click Copied.
Screenshot: the “API & integrations” page with the “New token” form
The “API & integrations” page: on the right the “New token” form with the “Name” field (2) and the rights to tick below.

How to tell it worked

The token appears in the list on the left with Name, the beginning of the Token, the Rights, Last used and Calls. Once the program is connected, the calls count up.

Give every program its own token. Then you can revoke one without disturbing the others, and Last used and Calls show which ones are still in use.

The rights

RightPlan
Read your projects and figuresfrom Pro
Read your reviewsfrom Pro
Reply to reviewsfrom Pro
Read video and audio reviewsfrom Pro
Create social exports and feature reviewsfrom Pro
See which surveys exist and whether they are runningfrom Pro
Read the AI analysis of your projectsfrom Pro
Read your awardsfrom Pro
Read internal feedbackfrom Pro
Create and change review surveysfrom Pro
Create and change embedsevery plan
Invite customers to leave a reviewevery plan
Display your seals and review blocksevery plan

Reply to reviews works through the API for the same reviews as in the dashboard: those that came in through Reputify, and Google reviews when the Google account is officially connected. For all others you reply on the platform itself (see Replying to reviews).

No right can delete or hide a review. Creating projects, platforms or reviews is not possible through the API – the Not available yet box on the page lists these rights. Whether your plan covers a right is checked on every call: after a plan change the new state applies immediately.

2. Sending requests (for developers)

The token is sent with every request in the Authorization header:

Authorization: Bearer rpf_live_…

Lists return at most 100 entries per page. Responses carry an ETag; with If-None-Match you save data when nothing has changed. How many requests per minute are allowed depends on the plan: Free 30, Starter 60, Pro 120, Agency Light 300, Agency 600. They are counted for the whole account – for agencies including their clients. All endpoints are listed in the API documentation – in Reputify on the left under API Access → Docs.

With a ready-made library (SDK)

Instead of building the requests by hand, your developer can use one of the official packages – for PHP (8.1 and later) and for JavaScript/TypeScript (Node 18+, Deno, Bun, Cloudflare Workers). They know every endpoint, page through lists on their own, wait when the plan limit is reached and verify webhook signatures:

composer require reputify/reputify-php
npm install @reputify/sdk
$reputify = new Reputify\Reputify('rpf_live_…');
$reviews  = $reputify->reviews->list(42, ['min_rating' => 4]);

Both packages are open source (MIT licence); the documentation is on Packagist and npm. Important: the token belongs on the server only, never in the source of a web page.

3. Inviting customers from a shop or till

If your system should only trigger a review invitation after a purchase, you do not need a team token but a survey token. It works on every plan.

  1. In the sidebar on the left, under Review Extras, click Review Surveys and then Edit next to the survey you want.
  2. At the top, click the tab Integration (1 in the screenshot). If it is missing, the access From my system (shop, till, MCP) is not ticked in the Basics tab.
  3. Under New token, enter a name, for example “WooCommerce main shop”, and click Generate (2 in the screenshot).
  4. Copy the token right away – it, too, is shown only once – and pass it on to your developer. Below, under How your system calls us, there is a ready-made example for them.
Screenshot: review survey, “Integration” tab with “New token” and “Generate”
The survey editor: 1 the “Integration” tab, 2 the “Generate” button next to the “New token” field.

Technically: the system calls POST https://api.reputify.io/v1/invite with the token. When the invitation goes out is set in the survey’s Email tab; a single call may override that delay with delay_hours. Pass an order number – the same number never creates a second invitation. The order’s products can be sent along and later appear on the review.

4. AI assistants (MCP)

With the same survey token you connect AI assistants such as Claude or Cursor via https://api.reputify.io/v1/mcp. The assistant can fetch information about the survey, invite customers and see the status of an invitation – it cannot read review texts or delete anything. The ready-made configuration is in the Integration tab under For AI agents (MCP). MCP is available from the Pro plan.

5. Webhooks

A webhook is the other direction: Reputify contacts your system as soon as something happens. To set one up, enter a Webhook URL in the survey’s After submission tab (from the Pro plan). Reputify reports new reviews (review.submitted), redirects to platforms (review.handover) and internal feedback (feedback.received). Every delivery carries the header X-Reputify-Signature: sha256=… – an HMAC-SHA256 signature over the body. Failed deliveries are retried up to three times and logged.

Revoking and disconnecting

You revoke a team token on the API & integrations page in the list with Revoke, and a survey token in the Integration tab with Revoke. Programs you approved through the connect dialog – such as the WordPress plugin – are listed on the API & integrations page under Connected applications and can be removed there with Disconnect.

Frequently asked questions

I do not see the “API Keys” menu item.

It is only visible to owners and admins of the team. Ask the owner to issue the token, or to give you the admin role (see Inviting your team and assigning roles).

I cannot tick a right.

Your plan does not include it – most read rights start with Pro. See Changing or cancelling your plan.

I did not copy the token.

It cannot be shown again. Revoke it and issue a new one.

Didn't find an answer?

Our support team is happy to help you.

Help