• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 2 subscribers
  • Views 292 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Product API failing standard request

Nicholas Freeman
Prodigy 20 points

Hello,

From your developer portal I am not getting this error for what looks like a valid request. What am I doing wrong?

api-portal.ti.com/product-information-api

curl -X 'GET' \
'transact.ti.com/.../GRM32ER61E226KE15L' \
-H 'accept: application/json' \
-H 'Authorization: Bearer <TOKEN>'

{
"Errors": [
{
"Code": "TI-API-00221",
"Message": "No API Endpoint Found"
}
]
}

EDIT: after trying to submit this issue I can see that the part number is not recognized??? 

This form is not recognizing the following part number: GRM32ER61E226KE15L

  • 0
    TI__Genius 9365 points

    HI Nicholas - i need to do some investigation and I will be out of office tomorrow, returning on Monday.

    But see if this will help you in the meantime- on our portal this link --  Keys and company information 

    talks about access keys, you must enter in your key access and id and click the authorized icon (even to use our tryout features)

    then run the try out feature

    Please make sure you are using your credentials, even in our portal json as show in the above snipit, you have to enter your key access and id in the porta,  click on the authorize  lock icon then tryout feature -- I am not finding this product in our system, if it happens to be not the material but a referenced material -  Do you have another material you can try to see if your access is working like this material AFE7799IABJ  it should be found.  

    Will be glad to revisit with you on Monday.

  • 0 in reply to Tammy Rawdon
    Prodigy 20 points

    Thanks for that tip– yes I was sure to authorize the request before doing so. Additionally, I would expect if the issue were authorization, that I would not get "No API Endpoint Found" as an error.

    To me the error leads me to believe that somehow adding the MPN to the path leads the API to believe I am accessing an endpoint that doesnt exist. 

  • +1 in reply to Nicholas Freeman
    TI__Genius 9365 points

    I ran with your credentials in my app and I did get the expected error of part number not found. when I execute on the portal with creds - I see a network failure that should not be happening for the url.. a mix of errors.. it seems we have an issue, thank you for sharing to us...

    I did run with this json  below  from the portal and got part number not found (note it has a v1 in the url vs a v2 in the url.

    I will have our developers look at the system error to see why it is not giving the valid error code of part number not found.

    If you will run the product api with the following url - it should work for you   we need to look at the code on our portal

    https://transact.ti.com/v1/products/GRM32ER61E226KE15L

  • 0 in reply to Tammy Rawdon
    Prodigy 20 points

    Thanks Tammy, that makes sense. Is V1 still active and reliable? Wondering if I should migrate our systems to use that endpoint in the meantime

  • 0 in reply to Nicholas Freeman
    TI__Genius 9365 points

    Yes, we had mistakenly added as v2 in the portal access for our product API- no it is not migrated to a v2 - we have/are correcting this on our portal, please update to v1 on your end, that is the valid, active, and reliable url to use.

**Attention** This is a public forum