Twilio to KORE Migration Guides

As we prepare to complete our migration activities and completely decouple our systems from Twilio, we will need you to make some updates to your applications to continue using Super SIM and Programmable Wireless. Below is an overview of changes you should consider as you are planning your remaining 2024 development roadmap and allocation of resources.

There are 2 critical deadlines: November 1, 2024, and May 1, 2025.

Resource IDs

To reduce the effort required to initially migrate to KORE, we will initially continue to use Twilio SIDs as resource IDs. However, please note that within the next 12 - 18 months we intend to deprecate the use of Twilio SIDs and introduce new KORE-styled IDs for each resource with new versions of the APIs. As an example, currently Super SIM’s have a SIM SID like HS9e729d48c812e9dd1859947095f86c21 generated by Twilio. New KORE-styled IDs like ssim_sim_2x4y6z8a0b1c2d3e4f5g6h7j8k that are consistent with IDs of other KORE resources will be introduced for your resources that you will eventually need to use instead of the Twilio SIDs.

You may be able to reduce the impact of this future change by setting the unique_name for resources that have that property to a unique internal identifier. You can then use that unique name in place of the Twilio SID or KORE ID when calling the API.

Migrating from Twilio Event Streams

Super SIM Connection Events are delivered via Twilio’s Event Streams product which we will no longer be connected to after November 1, 2024. To continue to receive Connection Events, you will need to integrate with KORE’s Streaming Product. We intend to simultaneously publish Super SIM Connection Events to both Twilio and KORE services until November 1, 2024. You can expect the Super SIM information of the event (i.e. the payload within the data property of the event) to be comparable to the events sent through Twilio Event Streams today. To not miss any events, you will likely need to subscribe to events from both Twilio and KORE at the same time and consolidate and dedupe the events within your application. We intend to publish a comprehensive guide with step-by-step instructions on how to subscribe to events from KORE and migrate from Twilio Event Streams in the coming months.

Expect us to stop publishing Super SIM Connection Events through Twilio's Event Streams starting November 1, 2024. Ensure you make the necessary changes to your applications before then to avoid any interruptions to your service.

Migrating Callbacks and Webhooks

Today, you can set a callback URL when making asynchronous requests to the Twilio APIs such as when you update a SIM resource or send an SMS Command. When the related resource changes, an HTTP request is sent to your callback URL to notify you. Similarly, you can configure a webhook on your Fleets to forward the payloads of SMS or IP Commands to you via an HTTP request. When the HTTP request is sent to your endpoint, multiple Twilio headers are provided including one that allows you to verify that the request came from Twilio.

We intend to stop sending any HTTP requests through Twilio services and instead send them via KORE services starting November 1, 2024, at which point no Twilio headers will be included. We are exploring options to allow you to verify that requests came from KORE. KORE will not be sending requests from a static range of IP addresses.

Additionally, we intend to introduce mechanisms that will allow you to control which service (Twilio or KORE) an HTTP request for your callback or webhook comes from to allow you to complete your development work before all requests are sent by KORE.

We will release a comprehensive migration guide on callbacks and webhooks in the coming months.

Expect all HTTP requests for callbacks and webhooks to come from KORE without any Twilio headers starting November 1, 2024. Ensure you make the necessary changes to your applications before then to avoid any interruptions to your service.

Helper Libraries (SDKs)

Twilio offers robust helper libraries (SDKs) in multiple languages (e.g. the python helper library) to easily interact with the Twilio REST APIs. KORE does not offer similar SDKs. Instead, we intend to publish an OpenAPI specification file which can be used to generate API clients in a variety of languages allowing you to quickly generate API clients to make requests to the KORE APIs. We will publish comprehensive examples of how to generate API clients from our OpenAPI file and use those clients to interact with KORE’s APIs.

You can begin familiarizing yourself with OpenAPI by using Twilio’s OpenAPI specification to generate clients to interact with Super SIM or Programmable Wireless’ APIs.

API Authentication

Twilio uses basic authentication to access REST APIs. KORE uses OAuth. While your Twilio authentication token can be used forever, to access KORE’s APIs you will need to generate an access token that will expire.

KORE recommends that you use relatively short expirations for access tokens in line with industry and your internal best practices and add the necessary logic to your applications to generate new tokens as needed; however, to minimize the changes you will need to make to your application to migrate to KORE’s REST APIs in the short term, you will be able to generate an access token with a very long expiration period (1 – 2 years). We will publish a comprehensive guide with suggestions to consider for your migration planning including additional functionality available to you via OAuth in the coming months.

API Endpoints

New API endpoints for Super SIM and Programmable Wireless will be released using KORE URLs. You will need to migrate your applications from making API requests to Twilio's endpoints to making your requests to KORE's endpoint. You do not need to make any changes for other Twilio products such as Messaging or Voice as those products were not acquired by KORE. We intend to make the KORE APIs as similar as we can to the existing Twilio APIs to minimize the changes required.

You will be able to make API requests to manage Twilio IoT products until May 1, 2025, but we encourage you to plan to migrate to KORE APIs by the end of 2024 or early 2025 to have extra time if you encounter challenges during the migration process.

If you have any questions or concerns about any of the concepts covered above, please contact KORE customer support or your KORE account representative.

Last updated