Locale Summary
| Locale name | Turkey |
|---|---|
| ISO code | TR |
| Region | Middle East & Africa |
| Mobile country code | 286 |
| Dialing code | +90 |
Guidelines
| Two-way SMS supported | No |
|---|---|
| Number portability available | Yes |
| Twilio concatenated message support | Yes |
| Message length | 160 characters |
| Twilio MMS support | Converted to SMS with embedded URL |
| Sending SMS to landline numbers | SMS cannot be sent to landline destination number. The Twilio REST API will throw a 400 response with error code 21614, the message will not appear in the logs and the account will not be charged. |
| Compliance considerations | Because Turkish carriers filter traffic with Numeric and unregistered Alphanumeric Sender IDs, be sure to pre-register your Alphanumeric Sender ID to ensure message delivery. Person-to-person (P2P) traffic, as well as content related to gambling, politics, and religion are prohibited. From February 15, 2021 — and until further notice — submission of promotional traffic to Turkey will be prohibited. Please do not submit such traffic as it may result in your messages and your registered Sender ID being blocked. It may also result in financial penalties. |
Phone Numbers & Sender ID
| Alphanumeric | Long Code | Short Code | |||
|---|---|---|---|---|---|
| Pre-registration | Dynamic | Domestic | International | ||
| Operator network capability | Required | Not Supported | Not Supported | Not Supported | Not Supported |
| Twilio supported |
Required
Learn more | Not Supported | --- | Supported | --- |
| Sender ID preserved | Yes | --- | --- | No | --- |
| Provisioning time | 2 weeks | N/A | N/A | N/A | N/A |
| UCS-2 support | Supported | N/A | N/A | Supported | N/A |
| Use case restrictions | P2P, gambling, political, or religious content is prohibited. Unsolicited messages will not be sent to end-users. | N/A | N/A | SMS delivery to the Turkish Republic of Northern Cyprus is not supported. | N/A |
| Best practices | N/A | N/A | N/A | Numeric Sender IDs may be overwritten, with delivery attempted on a best-effort basis. We recommend you pre-register an Alphanumeric Sender ID to ensure message delivery. | N/A |
| Alphanumeric - Pre-registration | |
|---|---|
| Operator network capability | Required |
| Twilio supported |
Required
Learn more |
| Sender ID preserved | Yes |
| Provisioning time | 2 weeks |
| UCS-2 support | Supported |
| Use case restrictions | P2P, gambling, political, or religious content is prohibited. Unsolicited messages will not be sent to end-users. |
| Best practices | N/A |
| Alphanumeric - Dynamic | |
|---|---|
| Operator network capability | Not Supported |
| Twilio supported | Not Supported |
| Sender ID preserved | --- |
| Provisioning time | N/A |
| UCS-2 support | N/A |
| Use case restrictions | N/A |
| Best practices | N/A |
| Long Code - Domestic | |
|---|---|
| Operator network capability | Not Supported |
| Twilio supported | --- |
| Sender ID preserved | --- |
| Provisioning time | N/A |
| UCS-2 support | N/A |
| Use case restrictions | N/A |
| Best practices | N/A |
| Long Code - International | |
|---|---|
| Operator network capability | Not Supported |
| Twilio supported | Supported |
| Sender ID preserved | No |
| Provisioning time | N/A |
| UCS-2 support | Supported |
| Use case restrictions | SMS delivery to the Turkish Republic of Northern Cyprus is not supported. |
| Best practices | Numeric Sender IDs may be overwritten, with delivery attempted on a best-effort basis. We recommend you pre-register an Alphanumeric Sender ID to ensure message delivery. |
| Short Code | |
|---|---|
| Operator network capability | Not Supported |
| Twilio supported | --- |
| Sender ID preserved | --- |
| Provisioning time | N/A |
| UCS-2 support | N/A |
| Use case restrictions | N/A |
| Best practices | N/A |
For the benefit of all our customers, these guidelines are provided to help you comply with applicable requirements and to help ensure Twilio's platform remains compliant with global telecommunications ecosystem requirements. These guidelines represent our current understanding of common compliance requirements generally applicable to Twilio and its customers, and do not constitute legal advice. By posting these guidelines, Twilio makes no assurances regarding the legal compliance of your application built using our APIs. You are expected to understand and abide by all compliance obligations applicable to your specific application. You should check these pages regularly for updates as telecommunications ecosystem requirements continue to evolve and change, and the information below may be updated or changed without notice.