Connect Okendo to Rig

    Sync your Okendo product reviews into Rig, so review text and ratings sit next to the products and orders they belong to. Okendo connects with a User ID and a 32-character API key from the Okendo app.

    Before you start

    • You need access to the integration settings in the Okendo app.
    • Rig uses Okendo's Merchant REST API, which Okendo describes as the authenticated API for merchants. Okendo lists it as available to enterprise customers, so check that your plan includes it.

    Step 1: Find your Okendo credentials

    1. Sign in to the Okendo app.
    2. Open the integration settings section. Okendo's documentation says your User ID and your 32-character API key are both there.
    3. Copy both values. The User ID is the username for the API and the key is the password.

    Step 2: Connect it in Rig

    Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source.

    1. In Rig, open Connections, choose the Connectors tab and go to Sources & actions.
    2. Search for Okendo, open the card and click Connect.
    3. Okendo User ID: paste your User ID.
    4. API key: paste the 32-character key.
    5. Click Continue. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click Connect.
    6. The source then syncs on its schedule, which is nightly unless you change it. To load data straight away, click Sync on its row; Test pulls a small sample first if you want to check the connection.

    What Rig pulls in

    Okendo lands in its own okendo schema in your warehouse:

    • Reviews: your account-wide product reviews, newest first.

    Okendo's reviews endpoint returns approved reviews by default, so pending and rejected reviews do not sync.

    Good to know

    • Okendo allows about two requests per second on the Merchant API, so Rig paces itself and a large first sync takes a while.
    • Okendo has no server-side date filter for reviews. Rig reads newest first and stops once it reaches reviews it already holds, which keeps later syncs short.
    • Keep the key private. Okendo says the Merchant API must never be called from client-side code.
    • To disconnect Okendo, click the bin icon on the source's row under Sources & actions. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse.

    What people use this for

    • Find the products reviews are warning you about
    • Measure what reviews are worth
    • Read review text at scale

    More ideas for using Okendo

    Okendo documentation

    Was this guide helpful?