Telr

Telr is a Dubai-headquartered online payment gateway operating across the MENA region (UAE, Saudi Arabia, Bahrain, Jordan), supporting 120+ currencies and 30 languages. Its HTTPS/JSON gateway exposes a Hosted Payment Page, a Remote (direct) card and wallet API, repeat-billing agreements, mobile SDKs, and a newer REST Payments API - all PCI DSS v4.0 Level 1 and NESA certified.

Telr publishes 7 API contracts indexed on the APIs.io network, including Agreements API, Hosted Payment Page API, Payments API, and 4 more. Tagged areas include Payments, Payment Gateway, Fintech, MENA, and United Arab Emirates.

The Telr catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

Telr’s developer surface includes authentication, documentation, engineering blog, sandbox, getting-started guide, support, pricing, and 32 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

65.7/100 strong ▬ flat Agent 33/100 agent ready Front door AI 1/6 silent Heartbeat 94/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessFreemiumSelf serve⚡ Free to try

1 published contract 3 Agent Skills

Payments Payment Gateway Fintech MENA United Arab Emirates

What this lets a business do 2

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Consumer Commerce

AE-140

Hosted Payment PagePayments API

POST /gateway/order.json POST /api/v1/orders GET /api/v1/orders/{ref}

Subscription Billing & Revenue Management

BC-4250

Remote

POST /gateway/remote.json

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 65.7/100 · strong

Contract Quality 10.5 / 19

Developer Ergonomics 11.2 / 15

Access Clarity 15.0 / 15

Operational Transparency 2.8 / 10

Contract Governance 2.9 / 9

Discoverability 5.5 / 8

Regulatory Posture 5.6 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 33/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 4 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/telr/"><img src="https://apis.io/badge/telr/card.svg" alt="Telr on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)

5 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 55.8 — up to +11.1 composite points
Operational Transparency scores 28.9 — up to +9.2 composite points
Contract Governance scores 31.8 — up to +8.2 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/telr/apis.yml: open an issue on github.com/api-evangelist/telr to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Gulf and Southeast Asia Open Finance	distribution	9.6 (thin)	-	-
Southeast Asia and National Fintech Registers (Taiwan, UAE, Malaysia remittance, Indonesia SNAP)	distribution	9.6 (thin)	-	-
Official SDKs on Packagist, pub.dev and Hex	distribution	9.6 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 7

Individual APIs this provider publishes, each with its own machine-readable definition.

Telr Accounts and Split Payments API

Marketplace / split-payment Service API for sub-merchant onboarding, multi-split payments, debit/credit of sub-merchant accounts, payouts, and transaction reconciliation. Authen...

Telr QuickLink and E-Invoicing API

Remote creation of QuickLink payment links and e-invoices with extra data fields, for merchants who collect payment without a full checkout integration.

Telr Click to Pay (C2P) API

EMV Secure Remote Commerce (Click to Pay) checkout, available as a seamless integration or through the remote JSON API for tokenized card-on-file payments.

Telr Agreements API

Repeat billing / recurring agreement management.

Telr Hosted Payment Page API

Redirect-based hosted checkout (order.json).

Telr Payments API

Newer REST order API with HTTP Basic auth.

Telr Remote API

Telr API pricing

Prices published by Telr, read 2026-10-28 from telr.com/pricing.

Plan	Price
Startup Plan (UAE)	AED 249 Includes: AED 0 - 9,999 volume per month
Entry Plan (UAE)	AED 199 Includes: AED 10,000 - 24,999 volume per month
Small Plan (UAE)	AED 99 Includes: AED 25,000 - 49,999 volume per month
Medium Plan (UAE)	AED 0 Includes: AED 50,000+ volume per month
Startup (KSA)	SAR 99 Includes: SAR 0 - 30,000 volume per month
SME (KSA)	SAR 79 Includes: SAR 30,001-80,000 volume per month (also shown as SAR 179 in detail view)
SME Plus (KSA)	SAR 259 Includes: SAR 80,001 - 300,000 volume per month
Volume pricing	Contact us for volume pricing Includes: selling more than AED 500,000 per month

Plan details, limits and sources →

Rate limits

Request Rate: not published requests
IP Allow-list: configurable source ips
Duplicate Transaction Protection: unique per order cart id

Compiled by API Evangelist, not yet checked against Telr's documentation. All 4 limits →

Billed by: monthly fee · FinOps profile →

Pricing Plans 1

Published pricing tiers and plan structures.

Telr Plans Pricing

8 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Telr Rate Limits

4 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Telr

SLA

FinOps 1

Cost, billing, and metering signals for API financial operations.

Telr Finops

FINOPS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Telr Webhooks

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Telr API Rules

60 rules · 58 errors 1 warnings 1 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Telr Openapi Overlay

4 actions · update · telr-openapi.yml

DERIVED

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Telr Authentication

http/custom · 2 schemes

SECURITY

Telr Domain Security

no transport/DNS hardening detected

SECURITY

Telr Vulnerability Disclosure

security.txt · contact published

SECURITY

Telr Trust Center

PCI DSS v4.0 Level 1, NESA, Central Bank of the UAE Retail Payment Services License, 3-D Secure, GDPR

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Telr Agentic Access

5 operations · 4 acting · 3 human-in-the-loop

5 operations · 4 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

Sandbox

DeveloperPortal

GettingStarted

SignUp

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

LLMsTxt

LLMsTxt

X-MCPServerCandidate

X-MCPServerCandidate

AgentSkill

AgentSkill

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conformance

ErrorCatalog

Lifecycle

Conventions

DataModel

Webhooks

Build 6

SDKs, sample code, and the tooling you integrate with

PostmanWorkspace

Packages

SDKs

DeclineCodes

Postman

GitHubOrganization

GitHubOrganization

Access & Security 5

Authentication, authorization, and security posture

TrustCenter

TrustCenter

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Authentication

Authentication

Compliance

Compliance

Operate 2

Status, limits, changes, and where to get help

RateLimits

RateLimits

Support

Support

Commercial 5

Pricing, plans, and the legal terms of use

Plans

FinOps

Pricing

TermsOfService

PrivacyPolicy

Company 4

The organization behind the API

BlogRSS

BlogRSS

Website

Website

LinkedIn

Blog

Blog

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: telr
url: https://raw.githubusercontent.com/api-evangelist/telr/refs/heads/main/apis.yml
name: Telr
kind: company
description: Telr is a Dubai-headquartered online payment gateway operating across the MENA region (UAE, Saudi Arabia, Bahrain,
  Jordan), supporting 120+ currencies and 30 languages. Its HTTPS/JSON gateway exposes a Hosted Payment Page, a Remote (direct)
  card and wallet API, repeat-billing agreements, mobile SDKs, and a newer REST Payments API - all PCI DSS v4.0 Level 1 and
  NESA certified.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Freemium · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/telr.png
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-17
tags:
- Payments
- Payment Gateway
- Fintech
- MENA
- United Arab Emirates
tags_raw:
- Payments
- Payment Gateway
- FinTech
- MENA
- UAE
created: '2026-07-17'
modified: '2026-10-06'
specificationVersion: '0.23'
apis:
- aid: telr:telr-accounts-split-payments-api
  name: Telr Accounts and Split Payments API
  tags:
  - Marketplace
  - Split Payments
  - Payouts
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://docs.telr.com/reference/split-payment
  baseURL: https://secure.telr.com/api/v1
  properties:
  - url: https://docs.telr.com/reference/split-payment
    type: Documentation
  - url: https://docs.telr.com/reference/authentication
    type: APIReference
  description: Marketplace / split-payment Service API for sub-merchant onboarding, multi-split payments, debit/credit of
    sub-merchant accounts, payouts, and transaction reconciliation. Authenticated with HTTP Basic auth (merchant id as username,
    API key as password).
- aid: telr:telr-quicklink-einvoicing-api
  name: Telr QuickLink and E-Invoicing API
  tags:
  - Invoicing
  - Payment Links
  - E-invoice
  tags_raw:
  - Invoicing
  - Payment Links
  - E-Invoice
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://docs.telr.com/reference/introduction-to-e-invoicing
  baseURL: https://secure.telr.com/gateway
  properties:
  - url: https://docs.telr.com/reference/introduction-to-e-invoicing
    type: Documentation
  - url: https://docs.telr.com/reference/remote-creation-of-invoices
    type: APIReference
  description: Remote creation of QuickLink payment links and e-invoices with extra data fields, for merchants who collect
    payment without a full checkout integration.
- aid: telr:telr-click-to-pay-api
  name: Telr Click to Pay (C2P) API
  tags:
  - Click to Pay
  - Tokenization
  - EMV SRC
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://docs.telr.com/reference/introduction-c2p
  baseURL: https://secure.telr.com/gateway
  properties:
  - url: https://docs.telr.com/reference/introduction-c2p
    type: Documentation
  - url: https://docs.telr.com/reference/c2p-remote
    type: APIReference
  description: EMV Secure Remote Commerce (Click to Pay) checkout, available as a seamless integration or through the remote
    JSON API for tokenized card-on-file payments.
- aid: telr:telr-agreements-api
  name: Telr Agreements API
  description: Repeat billing / recurring agreement management.
  humanURL: https://docs.telr.com/reference/how-the-hosted-payment-page-works
  baseURL: https://secure.telr.com/gateway
  tags:
  - Agreements
  properties:
  - type: OpenAPI
    url: openapi/telr-agreements-api-openapi.yml
  - type: Documentation
    url: https://docs.telr.com/reference/how-the-hosted-payment-page-works
  - type: APIReference
    url: https://docs.telr.com/reference/createorder
  - type: Documentation
    url: https://telr.com/support/knowledge-base/remote-api-integration-guide/
  - type: APIReference
    url: https://docs.telr.com/reference/post_gateway-remote-json
  - type: Documentation
    url: https://docs.telr.com/reference/payment-pages-v2-applepay-integration
  - type: APIReference
    url: https://docs.telr.com/reference/post_remote_applepay
  - type: Documentation
    url: https://docs.telr.com/reference/repeat-billing
  - type: APIReference
    url: https://docs.telr.com/reference/post_gateway-manageagreement-json
  - type: APIReference
    url: https://docs.telr.com/reference/getorder
  - type: Documentation
    url: https://docs.telr.com/reference/mobile-api-integration-guide
  - type: Documentation
    url: https://docs.telr.com/reference/introduction-to-mobile-sdks
- aid: telr:telr-hosted-payment-page-api
  name: Telr Hosted Payment Page API
  description: Redirect-based hosted checkout (order.json).
  humanURL: https://docs.telr.com/reference/how-the-hosted-payment-page-works
  baseURL: https://secure.telr.com/gateway
  tags:
  - Hosted Payment Page
  properties:
  - type: OpenAPI
    url: openapi/telr-hosted-payment-page-api-openapi.yml
  - type: Documentation
    url: https://docs.telr.com/reference/how-the-hosted-payment-page-works
  - type: APIReference
    url: https://docs.telr.com/reference/createorder
  - type: Documentation
    url: https://telr.com/support/knowledge-base/remote-api-integration-guide/
  - type: APIReference
    url: https://docs.telr.com/reference/post_gateway-remote-json
  - type: Documentation
    url: https://docs.telr.com/reference/payment-pages-v2-applepay-integration
  - type: APIReference
    url: https://docs.telr.com/reference/post_remote_applepay
  - type: Documentation
    url: https://docs.telr.com/reference/repeat-billing
  - type: APIReference
    url: https://docs.telr.com/reference/post_gateway-manageagreement-json
  - type: APIReference
    url: https://docs.telr.com/reference/getorder
  - type: Documentation
    url: https://docs.telr.com/reference/mobile-api-integration-guide
  - type: Documentation
    url: https://docs.telr.com/reference/introduction-to-mobile-sdks
- aid: telr:telr-payments-api-api
  name: Telr Payments API
  description: Newer REST order API with HTTP Basic auth.
  humanURL: https://docs.telr.com/reference/how-the-hosted-payment-page-works
  baseURL: https://secure.telr.com/gateway
  tags:
  - Payments API
  properties:
  - type: OpenAPI
    url: openapi/telr-payments-api-api-openapi.yml
  - type: Documentation
    url: https://docs.telr.com/reference/how-the-hosted-payment-page-works
  - type: APIReference
    url: https://docs.telr.com/reference/createorder
  - type: Documentation
    url: https://telr.com/support/knowledge-base/remote-api-integration-guide/
  - type: APIReference
    url: https://docs.telr.com/reference/post_gateway-remote-json
  - type: Documentation
    url: https://docs.telr.com/reference/payment-pages-v2-applepay-integration
  - type: APIReference
    url: https://docs.telr.com/reference/post_remote_applepay
  - type: Documentation
    url: https://docs.telr.com/reference/repeat-billing
  - type: APIReference
    url: https://docs.telr.com/reference/post_gateway-manageagreement-json
  - type: APIReference
    url: https://docs.telr.com/reference/getorder
  - type: Documentation
    url: https://docs.telr.com/reference/mobile-api-integration-guide
  - type: Documentation
    url: https://docs.telr.com/reference/introduction-to-mobile-sdks
- aid: telr:telr-remote-api
  name: Telr Remote API
  description: Direct server-to-server card and wallet transactions (remote.json).
  humanURL: https://docs.telr.com/reference/how-the-hosted-payment-page-works
  baseURL: https://secure.telr.com/gateway
  tags:
  - Remote
  properties:
  - type: OpenAPI
    url: openapi/telr-remote-api-openapi.yml
  - type: Documentation
    url: https://docs.telr.com/reference/how-the-hosted-payment-page-works
  - type: APIReference
    url: https://docs.telr.com/reference/createorder
  - type: Documentation
    url: https://telr.com/support/knowledge-base/remote-api-integration-guide/
  - type: APIReference
    url: https://docs.telr.com/reference/post_gateway-remote-json
  - type: Documentation
    url: https://docs.telr.com/reference/payment-pages-v2-applepay-integration
  - type: APIReference
    url: https://docs.telr.com/reference/post_remote_applepay
  - type: Documentation
    url: https://docs.telr.com/reference/repeat-billing
  - type: APIReference
    url: https://docs.telr.com/reference/post_gateway-manageagreement-json
  - type: APIReference
    url: https://docs.telr.com/reference/getorder
  - type: Documentation
    url: https://docs.telr.com/reference/mobile-api-integration-guide
  - type: Documentation
    url: https://docs.telr.com/reference/introduction-to-mobile-sdks
common:
- url: https://telr.com/blog/rss.xml
  type: BlogRSS
- type: CapabilityMap
  url: capabilities/telr-capability-edges.yml
  name: Telr Business Capability Map
- type: PostmanWorkspace
  url: https://www.postman.com/kinlaneapi/telr/overview
- type: AgenticAccess
  url: agentic-access/telr-agentic-access.yml
- type: TrustCenter
  url: security/telr-trust-center.yml
- type: VulnerabilityDisclosure
  url: security/telr-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/telr-domain-security.yml
- type: Authentication
  url: authentication/telr-authentication.yml
- type: Website
  url: https://telr.com/
- type: Documentation
  url: https://docs.telr.com/
- type: Plans
  url: plans/telr-plans-pricing.yml
- type: RateLimits
  url: rate-limits/telr-rate-limits.yml
- type: FinOps
  url: finops/telr-finops.yml
- type: LinkedIn
  url: https://www.linkedin.com/company/telr
- url: https://telr.com/blog/
  type: Blog
- type: Packages
  url: packages/telr-packages.yml
- type: SDKs
  url: packages/telr-packages.yml
- type: LLMsTxt
  url: llms/telr-llms.txt
- type: X-MCPServerCandidate
  url: mcp/telr-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: Overlay
  url: overlays/telr-openapi-overlay.yaml
- type: Conformance
  url: conformance/telr-conformance.yml
- type: Compliance
  url: https://telr.com/secure
- type: ErrorCatalog
  url: errors/telr-problem-types.yml
- type: DeclineCodes
  url: errors/telr-decline-codes.yml
- type: Lifecycle
  url: lifecycle/telr-lifecycle.yml
- type: Conventions
  url: conventions/telr-conventions.yml
- type: Sandbox
  url: sandbox/telr-sandbox.yml
- type: DataModel
  url: data-model/telr-data-model.yml
- type: Webhooks
  url: asyncapi/telr-webhooks.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Postman
  url: collections/telr.postman_collection.json
- type: GitHubOrganization
  url: https://github.com/Telr-PG
- type: DeveloperPortal
  url: https://docs.telr.com/
- type: GettingStarted
  url: https://docs.telr.com/reference/get-started
- type: Support
  url: https://telr.com/contact-us/
- type: Pricing
  url: https://telr.com/pricing/
- type: SignUp
  url: https://telr.com/get-started/
- type: TermsOfService
  url: https://telr.com/terms-and-conditions/
- type: PrivacyPolicy
  url: https://telr.com/privacy-policy/
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Telr API — frequently asked questions

Does Telr have an API?

Yes. APIs.io lists 7 APIs from Telr, including Telr Accounts and Split Payments API, Telr QuickLink and E-Invoicing API and Telr Click to Pay (C2P) API, and 4 more.

Is there an OpenAPI specification for the Telr API?

Yes. APIs.io indexes 4 OpenAPI specifications for Telr, each linked for download from this page.

How do I authenticate with the Telr API?

Telr uses bearer-token authentication (http/custom · 2 schemes). The details are profiled on APIs.io as Telr Authentication.

How much does the Telr API cost?

Telr publishes its prices; its Startup Plan (UAE) plan is AED 249 as of 2026-10-28. APIs.io lists 8 pricing plans for Telr, with each plan's price, limits and inclusions under Pricing on this page.

Is the Telr API ready for AI agents?

Telr has a Kin Score of 65.7 out of 100 (strong) and an Agent Readiness score of 33.2 (agent-ready), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/telr"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/telr/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/telr/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.