Get started

Welcome to TI's Developer Portal.


Our APIs offer these benefits:

  • Get started right away: Explore our Developer Portal to learn what our APIs do, how they work, and what you need to do to interface with them. Use our sandboxes and get building now. Our APIs need just a few lines of code to run in your applications.
  • Have a clear overview: Always know what's happening. Use our API analytics to track user activity in your applications and adjust your tactics if necessary.

The TI API Developer Portal contains a wealth of information about our business-ready APIs. Take some time to familiarize yourself with the portal before building your apps.

Step 1: How to use
Step 2: How to go live
Step 3: Authentication
Step 4: Error handling
Step 5: Support

How to use


To use our API products, you need a myTI account. A myTI account associated with your company email address is required to view some areas of this Developer Portal. It is also needed to subscribe to APIs and create applications that use TI APIs. More information about myTI accounts is available at  

To request a myTI account:

  • Contact your company’s Partner Administrator for the TI Enterprise API Gateway. The Partner Administrator will be able to explain the partner user process and register your company email address and role, which are required to obtain a myTI account.
  • Go to to learn about registering for an account. 


API Access

To request access to an API:

  • Log in to the Developer Portal using your myTI account
  • Select 'Apps' in the upper right corner 
  • Register an application and select the products you would like to access 
  • Your access should be granted quickly

How to go live

Once you have tested your application and related proposition(s) in our sandbox environment, you can submit a request to go live.

  • First, create a new Team App for production. When doing so, you will get a different API key that you can use for your production environment.
  • To get production access, both your account and App details must be registered correctly.
  • Subscribe to the API products you would like to use in the production environment.
  • Submit your request and contact us to request production access. Depending on the API, our API Services team may contact you to discuss the details of your request.
  • Once approved, you will be ready to use our API in a live environment.


The authentication for this API is based on access tokens. To obtain an access token, you need to call our OAuth API. The authentication mechanism may vary by API depending on the required authentication level.


These URLs provide the endpoints needed to retrieve tokens:

OAuth flows

Our APIs are secured using OAuth 2.0. This means you will need to pass an access token when making your request to the APIs.  We use the client credentials flow.

Here is an example:

POST /v1/oauth/accesstoken HTTP/1.1

The response should look like this:

    "access_token": "MTQ0NjJkZmQ5OTM2NDE1ZTZjNGZmZjI3",
    "token_type": "bearer",
    "expires_in": 3599,
    "scope": "",
    "application_name": "app_name",
    "": "",
    "issued_at": "1582220284531",
    "client_id": "IwOGYzYTlmM2YxOTQ5MGE3YmNmMDFkNTVk"

Finally, your API call would look as following (would change based on API specs but Authorization would remain consistent):

Authorization: Bearer MTQ0NjJkZmQ5OTM2NDE1ZTZjNGZmZjI3

If you are having trouble, please note that:

  • The request parameters (grant_type, client_id, client_secret) need to be sent in the request body
  • You must send the 'User-Agent' Header (for example, 'User-Agent': 'Mozilla/5.0'). Some libraries do not set or send one by default

If you would like more information about the OAuth protocol, take a look at the OAuth RFC located here.


Error handling

This section provides an overview of TI's Developer API error model.

Error format

With the exception of the OAuth endpoint, all TI APIs throw errors using the following JSON format:

    "Errors": [
            "Code": "Unique Error Code",
            "Message": "Error Message"

The OAuth endpoint follows the OAuth RFC for error responses:


  "error": "invalid_request",
  "error_description": "Request was missing the 'redirect_uri' parameter.",
  "error_uri": "See the full API docs at"


Questions or problems? We are happy to help. Please check our FAQ page for the answers to frequently asked questions.

Can’t find the answer you need? Please get in touch and we will get back to you as soon as possible.