Multi-store API clients
Use one API client to integrate the stores that belong to the same Revi business. The client never creates a store and only sees stores granted by the business owner.
1. List authorized stores
curl https://api.revi.io/api/2026-10/stores \
-H "Authorization: Bearer $REVI_API_TOKEN" \
-H "Accept: application/json"2. Operate on one store
Every store write names exactly one store in the path:
curl https://api.revi.io/api/2026-10/stores/123/orders \
-H "Authorization: Bearer $REVI_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{"orders":[{"id_order":"A-1001","status":"ready"}]}'Do not send a business or store identifier in the JSON body. A store outside the client's grants returns the same 404 store_not_found as an unknown store.
Permissions
Start with a preset and restrict it further when possible. Sensitive scopes such as personal_data:read and invitation_suppressions:write must be selected explicitly. Without personal_data:read, personal customer fields are omitted. Anonymous reviews never reveal reviewer identity, even with that advanced scope.
Rotation
Issue a second active credential, deploy it to your server, verify requests, and then revoke the old credential. A client supports at most two active credentials during this rotation window.