What data does Datadrew pull from Okendo?
Connecting Okendo to Datadrew gives you access to your reviews and customer feedback data, including product reviews, star ratings, review requests, media content, and customer attributes. This helps you analyze review sentiment trends, correlate review volume with sales, identify products needing more social proof, and measure the impact of reviews on conversion rates.
⚠️ Plan requirement: Okendo API access requires the Advanced plan or higher. Essential and Growth plans do not include API access.
Prerequisites
- An Okendo account on the Advanced plan or higher
- Admin access to your Okendo account
- An active Datadrew account (any plan)
Step-by-step: Find your Okendo API credentials
- Log in to your Okendo admin panel.
- Navigate to Settings in the left sidebar.
- Click Integrations.
- Select Credentials.
- Your User ID and API Key are displayed on this page.
- Copy both the User ID and API Key.
Tip: Okendo uses Basic authentication, which requires both a User ID and an API Key. Make sure to copy both values -- you will need them in Datadrew.
What to enter in Datadrew
- In Datadrew, go to Settings → Integrations.
- Find Okendo and click Connect.
- Enter both credentials as described in the table below.
- Click Save to complete the connection.
| Field | Value |
| API Key | Your Okendo API Key |
| User ID | Your Okendo User ID |
Official documentation
For more details on Okendo API authentication, see the Okendo Merchant REST API Quick Start.
Troubleshooting
- "Unauthorized" error: Verify that your Okendo plan includes API access (Advanced plan or higher). Lower-tier plans do not expose API credentials.
- Missing User ID or API Key: Both fields are required. Okendo uses Basic authentication with both values. Make sure neither field is left blank.
- "Credentials" not visible in settings: This section only appears on the Advanced plan or higher. If you do not see it, check your plan level with Okendo.
- Swapped credentials: The User ID and API Key are different values. Make sure you enter the User ID in the User ID field and the API Key in the API Key field -- do not mix them up.