Okendo

connect your okendo reviews and survey data to chord okendo is the reviews, ratings, and customer survey platform that powers social proof and post purchase feedback for many chord brands chord ingests your product reviews and your survey responses, including nps, so you can analyze review sentiment, ratings, and customer feedback next to your orders, subscriptions, and the rest of your commerce data what chord ingests from okendo chord brings in two categories of okendo data each becomes its own table (or set of tables) in your chord snowflake schema, and both link back to your orders and customers product reviews every review left on your products star rating, review title and body, sentiment, the reviewer, the product and variant reviewed, verified and incentivized flags, helpful vote counts, any merchant reply, and any reward attached to the review chord pulls these from the okendo merchant rest api on your tenant's standard sync schedule survey responses your post purchase and nps survey submissions the survey and channel, each answered question (question text, question type, the answer, and any custom "other" answer), and the nps score and category where applicable every response links back to the originating order and customer these arrive continuously through okendo's webhook events, and historical responses are backfilled once (see below) heads up reviews and survey responses reach chord through different mechanisms okendo's api can list your reviews, but it has no endpoint to list your surveys the next section explains how each one flows in and what that means for the data you'll see how chord ingests okendo data three workflows sit behind your okendo data you don't operate any of them yourself this is here so you understand what data shows up, when, and why 1\ reviews, pulled from the api once you connect your okendo credentials in chord, chord calls the okendo merchant rest api on your regular ingestion schedule and pulls your reviews into the warehouse this is a normal scheduled sync, like your other connectors 2\ survey responses, captured through webhooks okendo's api can return reviews, but it has no way to list your surveys, so chord can't pull survey responses the way it pulls reviews instead, chord captures them through okendo's webhook events as customers submit responses, okendo sends an event that chord receives into its cdp ingestion and lands in your warehouse this is a going forward feed every new response flows in from the moment the webhook is live heads up the okendo survey webhook is configured as part of chord onboarding, not something you set up yourself if you're onboarding okendo surveys and you're unsure whether the webhook is already live for your account, confirm with your chord contact so you know when the going forward feed starts 3\ survey backfill for historical responses the webhook feed only covers responses submitted after it goes live to fill in everything before that, chord backfills your historical survey responses it requests the responses for each of your known surveys directly from okendo, then reconciles them against the live webhook feed so nothing is double counted the result is a single, deduplicated view of your survey responses that spans both history and everything arriving in real time heads up reviews and survey responses are modeled in chord and available for analysis next to your oms and commerce data nps is derived from the survey answers themselves, so it lives with your survey response data rather than in a separate feed generate your okendo api credentials you'll need two values from okendo your user id and a merchant rest api key okendo generates them together in the integration settings of the app, and chord uses them as a pair the user id acts as the username and the api key as the password for authenticating to the okendo merchant rest api there are no scopes or permission toggles to configure heads up generating api credentials is an account level action in okendo, so you'll typically need admin access to the app if you don't see the integration settings, ask an admin on your okendo account to generate the credentials for you log in to the okendo app go to settings → integrations under the api credentials section, click generate (or show , if credentials already exist) to reveal your user id and merchant rest api key copy both values the user id is a uuid that looks like 00000000 0000 0000 0000 000000000000 the merchant rest api key is a 32 character string connect the credentials in chord open chord hub and go to data sources → add source pick okendo from the data source list paste your okendo user id into the user id field paste your merchant rest api key into the api key field click save chord makes a test call against the okendo reviews endpoint to confirm the credentials work the first reviews sync kicks off automatically, and later syncs run on your tenant's standard ingestion schedule survey responses flow in through the webhook feed and the one time backfill described above troubleshooting what does the validate step actually check? chord makes a small read against https //api okendo io/enterprise/reviews?limit=1 using your user id and api key, and confirms it returns a 200 response it does not pull or store any records that happens on the first scheduled sync after you save the credentials the validate step failed what now? okendo credentials are a user id and key pair with no scopes, so a failure almost always means one of the two values is wrong, was regenerated in okendo, or was copied with extra whitespace go back to settings → integrations in the okendo app, reveal both values again, and re copy them carefully it's easy to grab the user id and the api key from the wrong rows paste both into the same chord credential entry and test again why do i only see reviews so far, and not survey responses? reviews are pulled from the api as soon as you connect your credentials, so they appear on the first sync survey responses depend on okendo's webhook feed plus the historical backfill, which are set up during onboarding rather than by connecting the api key if your reviews are landing but survey responses aren't, confirm with your chord contact that the survey webhook is live for your account where does nps come from? nps score and category come from the answers inside your survey responses okendo carries them on the survey submission itself once your survey response data is flowing, nps is available alongside it, with no separate nps feed to connect do okendo api credentials expire? okendo's public documentation doesn't state an expiration policy for merchant rest api credentials if a credential that worked before suddenly fails, check settings → integrations in the okendo app first to confirm the values are still present and haven't been regenerated, then re copy them into chord how do i rotate the credentials? regenerate the credentials in the okendo app, paste the new user id and api key into the same chord credential entry, and save chord uses the new values on the next scheduled sync confirm the new credentials validate and the next sync runs cleanly before you rely on them need help? if you hit a credential or connectivity issue you can't resolve, reach out to help\@chord co mailto\ help\@chord co with the exact error message we'll trace the request and tell you what's failing