Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Okendo (BYOK) icon

Okendo (BYOK)

Read your Okendo product reviews, loyalty earning and redemption rules, webhook subscriptions and review translation blocklists with your own Okendo user ID and API key

Unify Dynamics LLC

Tools7read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderOkendounofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

What are the latest reviews of my Okendo store?
Tools called
list_reviews
Show Okendo review 5f1c2c7e-1111-4a2b-9c3d-000000000001
Tools called
get_review
How do customers earn loyalty points in my Okendo store?
Tools called
list_earning_rules
What rewards can customers redeem points for in my Okendo store?
Tools called
list_redemption_rules
Which webhooks are set up in my Okendo account?
Tools called
list_webhook_subscriptions
Which terms does my Okendo store keep untranslated in reviews?
Tools called
get_review_translation_blocklist

About

Okendo (BYOK) lets an AI assistant read your own Okendo data through the Okendo API with a key you supply (Okendo user ID). Read-only: 7 tools (list_reviews, get_review, list_earning_rules, list_redemption_rules, list_webhook_subscriptions, get_review_translation_blocklist, get_product_translation_blocklist). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.okendo.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Okendo. Okendo and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Okendo API (api.okendo.io) with a BYOK key; documentation: https://docs.okendo.io/docs/merchant-rest-api/usage. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

7 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data7 tools
  • List reviewsList the product reviews of the store, newest first by default, with product, title, text, star rating, status, sentiment, helpful votes, reply…
  • Get reviewGet one review by id with product, title, text, star rating, status, sentiment, helpful votes, reply and reviewer display name.
  • List earning rulesList the ways customers earn loyalty points in the store: rule type, points amount and caps.
  • List redemption rulesList the ways customers redeem loyalty points for rewards: rule id, reward type, points cost, minimum purchase, expiry and the product offered.
  • List webhook subscriptionsList the webhook subscriptions of the account: id, topics, API version, whether enabled and dates.
  • Get review translation blocklistGet the terms the store never translates in reviews (subscriber-wide blocklist).
  • Get product translation blocklistGet the terms kept untranslated in the reviews of one product.

Information

PublisherUnify Dynamics LLC
CategoryMoney & business
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-okendo.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 7 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-okendo.connectorbay.com/mcp
RESTPOST https://byok-okendo.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-okendo.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your Okendo user ID in the X-Upstream-Key header (get one at docs.okendo.io).
  • Ask a question; the agent picks the right tool and answers from the live data.

Okendo connector: questions and answers

What is the Okendo connector?

Okendo (BYOK) lets an AI assistant read your own Okendo data through the Okendo API with a key you supply (Okendo user ID). It is a hosted MCP server with 7 tools such as List reviews, Get review, List earning rules, List redemption rules, List webhook subscriptions, Get review translation blocklist, published by Unify Dynamics LLC. It is independent and not affiliated with Okendo.

How do I connect Okendo to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-okendo.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-okendo.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-okendo.json.

Do I need a Okendo account or API key?

Yes: this is a bring-your-own-key connector. Create a Okendo user ID at https://docs.okendo.io/docs/merchant-rest-api/quick-start and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is Okendo read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the Okendo connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

Inflow Inventory (BYOK)

Read your inFlow products, stock levels, customers, vendors, sales orders, purchase orders, transfers and manufacturing orders with your own API key

Live · MCP + REST12 tools

Infosec Exchange (BYOK)

Read timelines, profiles, hashtags, trends, notifications and search on infosec.exchange (information security community) with your own access token

Live · MCP + REST12 tools

Infura (BYOK)

Read Ethereum mainnet node data (blocks, balances, transactions, receipts, gas prices, contract calls) over JSON-RPC with your own Infura key

Live · MCP + REST11 tools

IntaSend (BYOK)

Read your IntaSend account in Africa: wallets and balances, wallet transactions, collections (invoices), payout status, chargebacks, payment links and FX rates with your own secret key

Live · MCP + REST10 tools

Intrinio (BYOK)

Read Intrinio securities, stock prices, company profiles, news, fundamentals and financial statements with your own Intrinio key

Live · MCP + REST12 tools

Inventory Planner (BYOK)

Read your Inventory Planner replenishment data: variants with forecast metrics, stock orders (purchase, transfer, assembly) and line items, with your own API key and account ID

Live · MCP + REST6 tools

Documentation

Back to top

Okendo (BYOK) — connector documentation

  • MCP endpoint: https://byok-okendo.connectorbay.com/mcp
  • REST API: POST https://byok-okendo.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-okendo.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Okendo Okendo user ID, sent in the X-Upstream-Key header and the Okendo API key (32 characters) in X-Upstream-Key-2 of every request (never stored, logged or cached)
  • Health: https://byok-okendo.connectorbay.com/health · Tool schemas: https://byok-okendo.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-okendo · agent@connectorbay.com

What Okendo (BYOK) is for

Okendo (BYOK) lets an AI assistant read your own Okendo data through the Okendo API with a key you supply (Okendo user ID). Read-only: 7 tools (list_reviews, get_review, list_earning_rules, list_redemption_rules, list_webhook_subscriptions, get_review_translation_blocklist, get_product_translation_blocklist). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.okendo.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Okendo. Okendo and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "What are the latest reviews of my Okendo store?"
  • "Show Okendo review 5f1c2c7e-1111-4a2b-9c3d-000000000001"
  • "How do customers earn loyalty points in my Okendo store?"
  • "What rewards can customers redeem points for in my Okendo store?"
  • "Which webhooks are set up in my Okendo account?"
  • "Which terms does my Okendo store keep untranslated in reviews?"

What it does

  • list_reviews: List the product reviews of the store, newest first by default, with product, title, text, star rating, status, sentiment, helpful votes, reply and reviewer display name. Page with the cursor in nextUrl.
  • get_review: Get one review by id with product, title, text, star rating, status, sentiment, helpful votes, reply and reviewer display name.
  • list_earning_rules: List the ways customers earn loyalty points in the store: rule type, points amount and caps.
  • list_redemption_rules: List the ways customers redeem loyalty points for rewards: rule id, reward type, points cost, minimum purchase, expiry and the product offered.
  • list_webhook_subscriptions: List the webhook subscriptions of the account: id, topics, API version, whether enabled and dates. Endpoint URLs are left out.
  • get_review_translation_blocklist: Get the terms the store never translates in reviews (subscriber-wide blocklist).
  • get_product_translation_blocklist: Get the terms kept untranslated in the reviews of one product.

BYOK key

You bring your own Okendo Okendo user ID (https://docs.okendo.io/docs/merchant-rest-api/quick-start). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.okendo.io over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Notices

Find the user ID and API key in the Okendo app under integration settings. The Merchant API is part of Okendo's enterprise plan. Reviewer emails are left out of the answers.

Data sources

Live from the Okendo API (api.okendo.io) with a BYOK key; documentation: https://docs.okendo.io/docs/merchant-rest-api/usage. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Okendo. Okendo and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Okendo account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Okendo (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Okendo (BYOK) is. Okendo (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Okendo data: Read your Okendo product reviews, loyalty earning and redemption rules, webhook subscriptions and review translation blocklists with your own Okendo user ID and API key. You bring your own Okendo Okendo user ID; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Okendo call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.okendo.io, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Okendo rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Okendo receives. The request we make on your behalf, including the key and the arguments, under Okendo's own terms and privacy policy. Okendo acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Okendo gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Okendo data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Okendo (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Okendo at any time to end all access.

Children. Okendo (BYOK) is a general-audience service operated by the adult using the assistant, under Okendo's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

Okendo (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Okendo (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. Okendo (BYOK) provides: Read your Okendo product reviews, loyalty earning and redemption rules, webhook subscriptions and review translation blocklists with your own Okendo user ID and API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own Okendo credentials and only access data you are allowed to access. Okendo's terms apply to your use of Okendo; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Okendo. Okendo and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data Okendo returns, lightly trimmed; it may be incomplete, delayed or changed by Okendo. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Okendo account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Okendo's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Okendo may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Okendo key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Okendo takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-okendo

Okendo (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Okendo (BYOK) never asks for them.

Get Okendo (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Okendo Okendo user ID. Create one at https://docs.okendo.io/docs/merchant-rest-api/quick-start, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Okendo. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Okendo.