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's Changed?
  • API Authorization
  • Rotating your API Credentials
  • Transitioning from Twilio Standard and Main API Keys
  • Building Clients from OpenAPI Spec
  • API Reference Documentation
  • Get Started!

Was this helpful?

  1. Twilio to KORE Migration Guides

Migrating to KORE's APIs

PreviousMigrating to KORE ConsoleNextMigrating to KORE Callbacks

Last updated 5 months ago

Was this helpful?

You must migrate to KORE's APIs by May 1, 2025.

This documentation will explain the differences between interacting with Twilio APIs and KORE. If you have questions, you can reach out to support@korewireless.com.

To learn more about the overall experience KORE offers, dig into our developer docs.

What's Changed?

The request parameters you send to our APIs and the responses you get back have remained unchanged to minimize the work needed to migrate your code for managing Super SIMs and Programmable Wireless SIMs to KORE's REST APIs. For example, you will continue to see the same SIDs (string IDs) on all of your resources.

The biggest challenge you will likely face is switching from using Twilio's static auth tokens and API keys to OAuth workflows if you aren't already familiar with them. Learn more below.

KORE does not have static auth tokens or API keys like Twilio uses. Our APIs are secured using OAuth workflow with expiring access tokens which may require additional development to adopt when migrating. Ensure you account for this in your planning.

Another large change to account for in your planning if you use Twilio's SDKs (aka "helper libraries") today is that KORE does not publish similar prebuilt SDKs. Instead, we publish OpenAPI specification files that you can use to generate clients in whichever languages you use. You can download the latest specification files from our Github.

API Authorization

Twilio's APIs are secured through auth tokens or API Keys, which use HTTP Basic Auth. Regardless of the approach, every API call with Twilio sends the username and password.

KORE's APIs are . You can generate as many API clients as you want. Each API Client will contain API Credentials, a Client-ID and Client-Secret which you use to obtain an expiring token based on the . You must before it expires.

Rotating your API Credentials

With Twilio, you can manage your API Keys and rotate your Auth Tokens through the Twilio Console, specifically the API keys & tokens section of your account.

KORE has a dedicated portal specifically for developers to manage their developer experience with KORE. We call it our Developer Portal, where you generate new API clients and obtain API Credentials to make API calls. Going forward, the developer portal will also be the home to other developer tools, such as managing your webhook secrets and event streams.

KORE uses , which require you to rotate them based on your set expiry time. We have provided of how to do it.

Transitioning from Twilio Standard and Main API Keys

Building Clients from OpenAPI Spec

KORE does not publish prebuilt SDKs. Instead, you can use our OpenAPI specification files to generate clients in whatever programming language you use.

API Reference Documentation

Get Started!

Here's a high level overview of the steps you'll need to take to begin using KORE's APIs to manage your SIMs:

  1. Log into the KORE Console.

  2. Go to the Developer Portal.

  3. Create an API Client that can access Super SIM, Programmable Wireless, or both.

  4. Save your client ID and secret.

  5. Use your client ID and secret to create an access token.

  6. Use your access token to authenticate to KORE APIs and access your SIMs and related resources.

If you want to dive into our API docs, you can head to the API reference docs.

With KORE, you can create a API Client, similar to Twilio's Standard Keys, that gives you access to KORE's products' APIs and restricts access to managing global resources like other API credentials and accounts.

You can also create an API client of type , similar to Twilio's Main Keys, that gives you the same access as Standard Keys and allows you to access global resources.

We've migrated our API documentation for and to KORE. Use these going forward. We will not be making any new updates to the API documentation (or any other documentation) for these products at Twilio.

Head to our developer docs for more details on managing your API integration with KORE. These docs will detail how our and some examples of .

We suggest you follow our to creating your first API Client and calling the , which will familiarize you with KORE's API ecosystem.

secured using OAuth 2.0 Client Credentials Flow
settings you define
refresh the token
expiring tokens
examples
Standard
Admin
APIs respond
refreshing your tokens
getting started guide
Super SIM
Programmable Wireless
PING endpoint