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.

Summary

• 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 for batch consent uploads, iys-check for single-recipient lookups, plus a real-time İYS check on every send-sms iys=1 call) 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

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 for batch consent uploads (up to 5,000 records per request), iys-check for single-recipient status lookups (ONAY / RET / source / date), and performs a real-time İYS lookup on every send-sms iys=1 call, dropping non-consented recipients automatically. 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

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

Sign up, API overview, MCP server

Related

• What is bulk SMS?
• İYS guide
• How to get an SMS sender ID
• API overview
• MCP server guide

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