Migrating to KORE's APIs

This documentation will explain the differences between interacting with Twilio APIs and KORE. If you have questions, you can reach out to [e-mail].

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

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

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 secured using OAuth 2.0 Client Credentials Flow. 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 settings you define. You must refresh the token before it expires.

KORE does not support the Auth Token concept.

Future guides will provide details for validating webhooks without an Auth Token.

Transitioning from Twilio Standard and Main API Keys

With KORE, you can create a Standard 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 Admin, similar to Twilio's Main Keys, that gives you the same access as Standard Keys and allows you to access global resources.

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 expiring tokens, which require you to rotate them based on your set expiry time. We have provided examples of how to do it.

Get started!

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

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