iletiMerkezi vs Twilio: Sending SMS to Turkey compared

Twilio is a US-based global communications platform offering SMS, voice, WhatsApp, e-mail, and video across 180+ countries; iletiMerkezi is a Turkey-based, BTK-licensed SMS platform with direct integration to Turkish carriers. The two products solve different problems: Twilio is a multi-channel global communications backbone, while iletiMerkezi is a Turkey-localised platform focused on bulk and transactional SMS. This guide compares the practical differences when your goal is sending SMS to Turkey.

TL;DR

For sending SMS to Turkey, iletiMerkezi offers local compliance (İYS, BTK licence, sender ID approval), carrier reach, and price advantage.
For multi-country, multi-channel (SMS + WhatsApp + Voice + Video) global communications, Twilio's platform breadth is hard to match.
iletiMerkezi has integrated İYS consent management (iys-register, iys-check) and BTK-approved sender ID workflow; Twilio leaves these local obligations to the customer.
Pricing for Turkey is credit-based at iletiMerkezi (local currency), generally cheaper per unit than global providers, with undelivered SMS free of charge.
Turkish-language support, local invoicing in TRY, KEP/MERSİS-compatible accounting — native at iletiMerkezi; Twilio operates with international invoicing and English support.

Comparison table

| Dimension | iletiMerkezi | Twilio | |---|---|---| | Headquarters | Turkey | USA (San Francisco) | | Geographic focus | Turkey + 150+ countries international SMS | 180+ countries, multi-channel | | Local Turkey licence | BTK STH-195 — direct carrier integration | Local carrier reach via international routes | | Channels | SMS (bulk, OTP, transactional), e-mail-to-SMS, iim.to short links | SMS, WhatsApp, Voice, Video, Email (SendGrid), Verify, Conversations | | İYS consent management | Native (iys-register, iys-check, send-sms iys=1) | Not provided — customer must build/manage | | BTK sender ID approval | Panel-driven application, 1–2 business days | Customer handles via local carrier or partner | | Pre-approval testing | APITEST sender (account's own test number, free) | Magic numbers + trial credentials | | Turkish UI / support | Full | Limited (official support in English) | | Pricing (Turkey SMS) | Credit-based, scales with volume; undelivered SMS free | Per-unit USD; volume discounts under separate policy | | New-account credit | 100 free SMS welcome | $15 trial (typical) | | Invoicing / accounting | TRY invoice, local VAT, KEP-compatible | International invoicing, possible FX/banking overhead | | API style | REST + JSON, MCP server, SDKs in 5+ languages | REST, gRPC, SDKs in many languages, Studio/no-code | | MCP / LLM integration | Official MCP server (@iletimerkezi/mcp-server) on npm | No official MCP (community tools exist) |

Which one to pick?

Choose iletiMerkezi if:

Your audience is in Turkey, recipients on Turkish carriers.
You want a partner that solves İYS consent management end-to-end.
Turkish-language support, TRY invoicing, and local-regulation guidance matter.
Your primary use is bulk SMS, OTP, or transactional — other channels are not urgent.
You are price-sensitive; the credit + undelivered-free model lowers per-unit cost.

Choose Twilio if:

You send SMS in 50+ countries in parallel and Turkey is a small share.
You want WhatsApp Business, Voice, and Video managed under the same API.
You value Studio-style no-code orchestration and a wider ecosystem.
Your billing centre is USD and operations are international.

Some teams use both: Twilio for global SMS and iletiMerkezi for Turkey traffic. Treating Turkey traffic separately for compliance and cost gives you both global flexibility and local efficiency.

Turkey-specific differences that matter

İYS compliance

In Turkey, commercial SMS sending requires consent registered in İYS. iletiMerkezi exposes iys-register and iys-check so consent management is one API surface; passing iys=1 to send-sms validates consent automatically before dispatch. Twilio does not address this — the developer must build their own integration with İYS or manage it manually.

See: İYS guide.

Sender ID approval

To send branded SMS in Turkey, a BTK-approved sender ID is required. iletiMerkezi handles the application from the panel; the typical timeline is 1–2 business days, and APITEST lets you keep integration testing while approval is pending. With Twilio, Turkey sender ID work goes through local carrier processes or partners; timelines vary.

See: How to get an SMS sender ID.

Carrier reach

iletiMerkezi has direct carrier integrations with Turkcell, Vodafone, and Türk Telekom; delivery receipts come straight from the carrier DLR layer. Twilio routes Turkey traffic via international corridors; deliverability and latency depend on the carriers along that route.

Pricing structure

iletiMerkezi:

Credit-based, unit price decreases with volume.
100 free SMS welcome credits for new accounts.
Undelivered SMS is free.
Invoiced in TRY, VAT computed automatically.

Twilio:

Per-unit USD pricing; Turkey SMS billed at international tariffs.
Trial credit (~$15) on first sign-up.
Refunds for undelivered messages depend on the global provider/route policy.

Current pricing: iletiMerkezi pricing · Twilio pricing.

Developer experience

Both products provide REST + JSON.

iletiMerkezi:

SDKs for Node, Python, PHP, Go (Java/.NET variants in progress).
Official MCP server (@iletimerkezi/mcp-server) — send SMS from Claude Desktop, Cursor, Cline in a single conversation.
17+ docs pages in TR + EN, raw .md access, public API manifest (/api/manifest.json).

Twilio:

SDKs in 10+ languages, very rich SDK ecosystem.
Studio (no-code orchestration), Functions (serverless), Flex (contact centre).
No official MCP server (community tools exist).

Frequently asked questions

Q: How long does migration from Twilio to iletiMerkezi take? A simple send-SMS flow can be ported in a few hours. With webhooks, reporting, and retry logic, 1–3 business days. Pick the SDK, swap env vars, and add the sender ID and İYS flows.

Q: I also need WhatsApp — does iletiMerkezi cover that? Today, iletiMerkezi's primary channel is SMS. For multi-channel needs (WhatsApp + Voice + Video), Twilio or a channel-specific provider is more efficient under one API.

Q: Does Twilio require a separate account for Turkey? Twilio's Toll-Free and international SMS products live in one account, but local compliance for Turkey (İYS, sender ID) may require additional partner agreements. iletiMerkezi is one account, one bill.

Q: Which one integrates faster with Claude Code / Cursor? With iletiMerkezi's official MCP server, npx -y @iletimerkezi/mcp-server wires up tool calls in Claude Desktop / Cursor / Cline. For Twilio, community MCP tools exist but no official offering yet.

How to start with iletiMerkezi

Sign up (100 free SMS credits).
Test the API integration with APITEST: send-sms, test-mode.
Apply for a brand sender ID: How to get an SMS sender ID.
If you'll send commercial content, upload İYS consents: İYS guide.
Wire up webhooks and reporting: webhooks, get-report.
For LLM-client usage: MCP server guide.

Last updated: 2026-04-30 · Türkçe