Skip to main content
Use sandbox credentials while you build. Sandbox partner API responses use the same JSON shape as production but return synthetic reviews.

​
Who this is for

Marketplace engineers wiring shop upsert and SSR review APIs before production traffic.

​
Create sandbox keys

In the EthioReview business dashboard:
1

Open Digital platform

Go to Integrations → Digital platform.
2

Enter allowed origins

Include http://localhost:3000 for local widget work.
3

Create sandbox API client

Click Create sandbox API client (or equivalent). Copy the secret (sk_test_*) immediately — it is shown once. Keep the publishable key (pk_test_*) for browser widgets.
You can also create a sandbox client under Integrations → API keys with:

​
Auth header

Base URL: https://api.ethioreview.com/api/v1 Never put sk_* in browser JavaScript, mobile apps, or public repos.

​
What sandbox returns

​
One failure mode

Using pk_test_* as a Bearer secret — partner routes require sk_test_*. Publishable keys are only for X-Widget-Key browser calls.

​
Go live

  1. Create a PRODUCTION API client under Integrations → API keys (or Digital platform) with live domains in allowed origins
  2. Swap sk_test_* → sk_live_* on your server
  3. Swap pk_test_* → pk_live_* in embeds
  4. Remove sandbox secrets from production env files
Environments → · Provision shops →