• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 2 subscribers
  • Views 405 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TI-API: Reliability of response code 404

Stefan Fröhlich
Prodigy 140 points
Part Number: TI-API

In our application we have a hot-list of items which we query in regular intervals in order to show our customers current stock and price data. If any item receives response code 404 ("tiPartNumber does not exist") we consider this a permanent failure (either an input error or a product becoming obsolete) and no longer query this item.

I found out that this is not reliable. As an example, SN74AHC1G14DCKR received response code 404 on March 6th:

2023-03-06 15:25:43.050936: TI API call (GET): https://transact.ti.com/v2/store/products/SN74AHC1G14DCKR?currency=EUR

TI API result (404):

[...]

[errorCode] => ERR-TICOM-INV-API-1002

[type] => ResourceNotFound

[reason] => Resource could not be found

[message] => tiPartNumber ('SN74AHC1G14DCKR') does not exist. Please correct the format (see e2e.ti.com/search
m&group=452&date=&customdaterange=0&startdate=&faq=true&sort=date%20desc&faq=true#) or verify that the part number is valid on TI.com and resubmit your request

[...]

After I manually removed the flag today the item (and a couple of others) have been queried successfully again.

Could you please have a look at this and either:

.) correct this if the behaviour is not what was intended or

.) otherwise tell me, so that we can treat 404s as temporary errors on our side and keep retrying

  • +1
    TI__Genius 10401 points

    Hi Stefan,

    You should not expect a part to fluctuate between found and not found.

    The logs indicate that the inventory API returned a 404 response for SN74AHC1G14DCKR for a handful of requests on March 6, and never before or after since the API was released last year.

    In general, you're interpretation of a 404 should be correct.

    I have logged an issue to see if we can determine the cause of the response code and return something other than 404 if an error occurs.

    Best regards,
    Paul

**Attention** This is a public forum