Pre-Built Tooling
| Category | Details |
|---|---|
| Authentication | API Key (Header: apiKey) + Store ID (Header: store) |
| Two-Way Sync | No |
| Events Supported | No |
| Realtime | Polling |
| Supports Rate Limiting | Yes |
| Authentication Scopes Supported | N/A (API Key) |
Objects Supported
Alloy Automation supports syncing the following objects from Reviews.io:- Product Reviews
- Company Reviews
- Customers
- Review Invitations
- Ratings
Set Up Guide
Trial Access
| Question | Answer |
|---|---|
| Offers free trial? | Yes. Reviews.io offers a free trial for new users. Start free trial |
| Requires paid sandbox? | No. The trial account can be used for testing and development. |
| Requires partnership to obtain authentication? | No. Any Reviews.io user can generate API keys from their account. |
Authentication (API Key + Store ID)
For customers who want to completely whitelabel their authentication experience, you can provide your own developer keys instead of using Alloy Automation’s. For API documentation, visit Reviews.io API Documentation.Use Cases
1) Review collection automation
Automatically send review requests through Reviews.io after order fulfillment or product delivery by syncing order data from your e-commerce platform.2) Review display integration
Pull product and company reviews from Reviews.io to display on your website, product pages, or marketing materials for social proof and increased conversions.3) Customer feedback analysis
Sync review data from Reviews.io into your analytics platform or data warehouse to analyze customer sentiment, identify product issues, and track satisfaction trends.4) Multi-channel review management
Aggregate reviews from Reviews.io with feedback from other sources to create a unified view of customer sentiment across all channels.5) Review response automation
Monitor new reviews from Reviews.io and trigger automated workflows to alert customer service teams about negative reviews or thank customers for positive feedback.API Gotchas
- Dual authentication required: Reviews.io requires both an API key and a Store ID to be provided in separate headers. Both must be present for API requests to succeed.
- Store-specific data: All data retrieved is scoped to the Store ID provided. If you manage multiple stores, ensure you’re using the correct Store ID for each integration.
- Rate limiting: The API enforces rate limits to protect system performance. Implement proper retry logic with exponential backoff when you receive rate limit responses.
- Review moderation: Reviews may go through a moderation process before appearing in API results. Don’t assume newly submitted reviews will be immediately available via the API.
- Date formats: Pay attention to date format requirements when filtering reviews by date ranges. Use ISO 8601 format for consistency.
For questions or troubleshooting, contact support@runalloy.com.