LogoLogo
ProductsDevelopersAPI ReferenceContact Us
Twilio IoT Acquisition
Twilio IoT Acquisition
  • Twilio IoT is now part of KORE
    • Link Your Twilio & KORE Accounts
    • Self-Service Limitations
    • IoT Customer Support Migration to KORE
    • Frequently Asked Questions (FAQ)
  • Twilio to KORE Migration Guides
    • Migrating to KORE Console
    • Migrating to KORE's APIs
    • Migrating to KORE Callbacks
    • Migrating to KORE Super SIM Connection Events
    • Migrating to KORE's Status Page
    • Migrating to SIM Ordering at KORE
    • Migrating to the New Super SIM Hardware
  • Advisories
    • Upcoming Changes to Developer Experience for Super SIM & Programmable Wireless – April 2024
    • New UI and APIs Available at KORE & More for Super SIM & Programmable Wireless - August 2024
    • KORE Callbacks Available - September 2024
    • KORE Event Streams Available - September 2024
    • KORE Child Accounts Created and Linked to Your Twilio Subaccounts - October 2024
    • Update on Our Migration to KORE - November 2024
    • More on Super SIM and Programmable Wireless Migration to KORE - December 2024
    • KORE Shop, API migration, Programmable Wireless Console - January 2025
    • More on Super SIM migration to KORE - March 2025
    • New Super SIM hardware and applets updates - April 2025
On this page
  • What do you need to know?
  • Why is this happening?
  • What do you need to do?
  • What happens if you do nothing?

Was this helpful?

  1. Advisories

KORE Callbacks Available - September 2024

PreviousNew UI and APIs Available at KORE & More for Super SIM & Programmable Wireless - August 2024NextKORE Event Streams Available - September 2024

Last updated 8 months ago

Was this helpful?

Hello,

You are receiving this message because you use Super SIM or Programmable Wireless.

What do you need to know?

If you currently receive callbacks for Super SIM or Programmable Wireless, you may have to make changes to your application to ensure there is no disruption when we shift from using Twilio’s callback infrastructure to KORE’s. We have released all the functionality necessary for you to plan and test receiving your webhooks from KORE. We have extended the date on which all callbacks will be sent from KORE by default to October 15, 2024 (previously October 1, 2024). Any changes, if necesssary, need to be completed by November 1, 2024, after which you will have no option to receive callbacks from Twilio for Super SIM and Programmable Wireless.

Why is this happening?

on June 1, 2023. Since then, KORE has been busy integrating Twilio IoT into KORE. Part of the Super SIM and Programmable Wireless user experience entails leveraging callbacks to receive events asynchronously and perform follow-up actions. Today, callbacks are sent through Twilio’s callback infrastructure, which was not part of the acquisition. We’re migrating to KORE’s callback services to ensure the same workflows can continue uninterrupted.

What do you need to do?

Plan to perform testing and make changes to your applications as needed with the following timeline in mind:

  • Until October 15, 2024, we will continue to use Twilio's callback infrastructure by default. The current payloads and headers you've been receiving will remain unchanged. However, you can begin receiving callbacks from KORE by and specifying the fragment #cbs=kore.

  • After October 15, 2024, we will change the default callback infrastructure from Twilio to KORE. If you need more time to complete the changes, you can continue to receive callbacks from Twilio's infrastructure by and specifying the fragment #cbs=twilio to instruct us to continue using Twilio's infrastructure. This will work until November 1, 2024.

  • After November 1, 2024, all callbacks will be sent from KORE regardless of what you provide for the “cbs” URL fragment.

We encourage you to transition to KORE callbacks as early as possible before the November 1, 2024, deadline. We have created a guide to help you through the transition. You can also review the following guides for more details:

What happens if you do nothing?

Beginning October 15, 2024, all callbacks will be sent from KORE’s callback infrastructure by default. If you did not test that your application properly accepts and processes the callbacks sent by KORE ahead of time, you may reject requests or encounter unexpected errors. You will experience issues if you are validating requests by checking Twilio’s signatures and have not made changes to also validate KORE’s signatures. If you have any questions, please contact your account executive or

KORE acquired Twilio IoT
editing the callback URL
editing the callback URL
Overview of KORE Webhooks
Get started with KORE Webhooks
Validating Webhook Signatures
KORE’s support team.