TI-API: errorCode "TI-API-0401"

zhihong geng

Prodigy 11 points

Part Number: TI-API

We have the Consumer Key and Consumer Secret, and Authorized by Server .

Then, I GET/store/products/{tiPartNumber} , Try it out , input the tiPartNumber , click Excute.

We have respones :

Responses

Curl

curl -X 'GET' \
  'transact.ti.com/.../SN74HC595PWR \
  -H 'accept: application/json' \
  -H 'Authorization: Bearer PReOADzlPQmIAMBvwZUUD8bQdUxQ'

Request URL

transact.ti.com/.../SN74HC595PWR

But, the Request URL have a 401 error:

errors
0
errorCode	"TI-API-0401"
type	"Security"
reason	"Invalid Credentials"
message	"Invalid bearer token. Please contact your local IT support to verify authentication information. Once resolved, please resubmit request."

over 3 years ago

+1 Paul King over 3 years ago

TI__Genius 10401 points

I suspect that you got caught in the middle of the transition from v1 to v2, and your API request for v2 may have been rejected. If you're trying to use credentials for a v1 API, they will not work the the v2 APIs.

To get access to the v2 APIs with the proper credentials, you must first create a myTI company account. Within your newly created company account, you can make a new request for v2 API access. Create a myTI company account at https://www.ti.com/ordering-resources/myti-company-account.html

Or for more information about getting started with the v2 APIs, take a look at the Get Started section of the API overview page at https://www.ti.com/ordering-resources/api-buying.html#get-started

After your API key request has been approved, check out the API portal https://api-portal.ti.com/

Let us know if you continue to have trouble.

0 zhihong geng over 3 years ago in reply to Paul King

Prodigy 11 points

Thank you, Paul!

As you said, the wrong reason is that we didn't use the company's account.

When we use the company account authorized, we get the correct response:

**Attention** This is a public forum

API solutions

API solutions Forum

TI-API: errorCode "TI-API-0401"

Responses

Curl

Request URL