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

Telr (BYOK)

Read your Telr payment gateway accounts, payouts, pending settlements and order status (UAE, Saudi Arabia, Middle East) with your own store id and API key

Unify Dynamics LLC

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

Try asking

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

What is the balance of my Telr accounts and when is the next payout?
Tools called
list_accounts
What payouts did Telr make to account 12345 in September 2026?
Tools called
list_payouts
Which transactions were included in Telr payout 987?
Tools called
list_payout_transactions
How much is Telr holding for my next payout on account 12345?
Tools called
get_pending_payout
Which Telr transactions are still pending payout on account 12345?
Tools called
list_pending_transactions
What is the status of Telr order 4A5B6C7D8E?
Tools called
get_order

About

Telr (BYOK) lets an AI assistant read your own Telr data through the Telr API with a key you supply (store id (the user name of the API login)). Read-only: 6 tools (list_accounts, list_payouts, list_payout_transactions, get_pending_payout, list_pending_transactions, get_order). 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 secure.telr.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Telr. Telr and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Telr API (secure.telr.com) with a BYOK key; documentation: https://telr-api.readme.io/reference/getaccounts-1. 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

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

OpenAPI
Read your data6 tools
  • List accountsList the merchant's Telr accounts with store id, currency, balance, payout interval, next payment date, minimum payout and payout fee.
  • List payoutsList payouts of one account, optionally between two dates, with total amount and the credit and debit breakdown (sales, refunds, fees, tax).
  • List payout transactionsList the transactions that make up one payout: reference, date, type, authorised and settled amounts, fees, tax and net.
  • Get pending payoutShow the amount waiting for the next payout of one account with the credit and debit breakdown.
  • List pending transactionsList transactions not yet paid out for one account with settlement amounts, fees, tax, net and due date.
  • Get orderGet one order by its Telr order reference: status, cart id, amount and currency, and the payment type, card scheme, status and message.

Information

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

Connect it to your agent

Three ways in, the same 6 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-telr.connectorbay.com/mcp
RESTPOST https://byok-telr.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-telr.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 store id (the user name of the API login) in the X-Upstream-Key header (get one at telr-api.readme.io).
  • Ask a question; the agent picks the right tool and answers from the live data.

Telr connector: questions and answers

What is the Telr connector?

Telr (BYOK) lets an AI assistant read your own Telr data through the Telr API with a key you supply (store id (the user name of the API login)). It is a hosted MCP server with 6 tools such as List accounts, List payouts, List payout transactions, Get pending payout, List pending transactions, Get order, published by Unify Dynamics LLC. It is independent and not affiliated with Telr.

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

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

Do I need a Telr account or API key?

Yes: this is a bring-your-own-key connector. Create a store id (the user name of the API login) at https://telr-api.readme.io/reference/getaccounts-1 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 Telr read-only?

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

Is the Telr 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

VAT Sense (BYOK)

Look up VAT and GST rates for 179 countries, validate VAT and EORI numbers against official registers and convert currencies with your own VAT Sense key

Live · MCP + REST12 tools

Vatstack (BYOK)

Read VAT rates, your saved VAT number validations and VAT price quotes from Vatstack with your own API key

Live · MCP + REST7 tools

Veeqo (BYOK)

Read your Veeqo orders, products and stock levels, customers, purchase orders, suppliers, warehouses, stores and tracking events with your own API key

Live · MCP + REST12 tools

Vindi (BYOK)

Read your Vindi recurring billing catalog: products with pricing, plans and plan items, and the payment methods enabled on the account, with your own API key

Live · MCP + REST7 tools

Virtuous (BYOK)

Read your Virtuous nonprofit CRM campaigns, projects, segments, events, gifts, grants and volunteer opportunities with your own API key

Live · MCP + REST12 tools

vivenu (BYOK)

Read your vivenu ticketing events, ticket types, tickets sold, orders, products and sales channels with your own vivenu API key

Live · MCP + REST9 tools

Documentation

Back to top

Telr (BYOK) — connector documentation

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

What Telr (BYOK) is for

Telr (BYOK) lets an AI assistant read your own Telr data through the Telr API with a key you supply (store id (the user name of the API login)). Read-only: 6 tools (list_accounts, list_payouts, list_payout_transactions, get_pending_payout, list_pending_transactions, get_order). 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 secure.telr.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Telr. Telr 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 is the balance of my Telr accounts and when is the next payout?"
  • "What payouts did Telr make to account 12345 in September 2026?"
  • "Which transactions were included in Telr payout 987?"
  • "How much is Telr holding for my next payout on account 12345?"
  • "Which Telr transactions are still pending payout on account 12345?"
  • "What is the status of Telr order 4A5B6C7D8E?"

What it does

  • list_accounts: List the merchant's Telr accounts with store id, currency, balance, payout interval, next payment date, minimum payout and payout fee. Bank details are not returned.
  • list_payouts: List payouts of one account, optionally between two dates, with total amount and the credit and debit breakdown (sales, refunds, fees, tax).
  • list_payout_transactions: List the transactions that make up one payout: reference, date, type, authorised and settled amounts, fees, tax and net.
  • get_pending_payout: Show the amount waiting for the next payout of one account with the credit and debit breakdown.
  • list_pending_transactions: List transactions not yet paid out for one account with settlement amounts, fees, tax, net and due date.
  • get_order: Get one order by its Telr order reference: status, cart id, amount and currency, and the payment type, card scheme, status and message. Customer details are not returned.

BYOK key

You bring your own Telr store id (the user name of the API login) (https://telr-api.readme.io/reference/getaccounts-1). 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 secure.telr.com 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.

Data sources

Live from the Telr API (secure.telr.com) with a BYOK key; documentation: https://telr-api.readme.io/reference/getaccounts-1. 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 Telr. Telr 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 Telr account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Telr (BYOK) — Privacy Policy

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

What Telr (BYOK) is. Telr (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Telr data: Read your Telr payment gateway accounts, payouts, pending settlements and order status (UAE, Saudi Arabia, Middle East) with your own store id and API key. You bring your own Telr store id (the user name of the API login); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Telr 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 secure.telr.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Telr 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 Telr receives. The request we make on your behalf, including the key and the arguments, under Telr's own terms and privacy policy. Telr acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Telr 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 Telr 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. Telr (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 Telr at any time to end all access.

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

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

Terms of service

Back to top

Telr (BYOK) — Terms of Service

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

  1. The Service. Telr (BYOK) provides: Read your Telr payment gateway accounts, payouts, pending settlements and order status (UAE, Saudi Arabia, Middle East) with your own store 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 Telr credentials and only access data you are allowed to access. Telr's terms apply to your use of Telr; 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 Telr. Telr 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 Telr returns, lightly trimmed; it may be incomplete, delayed or changed by Telr. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Telr 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 Telr'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; Telr 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 Telr 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 Telr 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-telr

Telr (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. Telr (BYOK) never asks for them.

Get Telr (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Telr store id (the user name of the API login). Create one at https://telr-api.readme.io/reference/getaccounts-1, 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 Telr. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Telr.