TI-API: 429 Too Many Requests Error on Pricing And Inventory API

Joshua Stein

Part Number: TI-API

On both Postman and Mulesoft (our API and integration platform) I am getting this error and a 429 status code when making a request to transact.ti.com/.../catalog

{

"errors": [

{

"errorCode": "TI-API-0429",

"type": "Security",

"reason": "Too many requests",

"message": "Rate Limit Quota exceeded. Please reduce the rate of requests. If issue persists, please contact support (https://api-portal.ti.com/support)."

}

]

}

All the information I can find suggests that this (pricing and inventory) API is not meant to have a rate limit, such as this post: e2e.ti.com/.../ti-api-how-to-solve-error-ti-api-0429
or this post
e2e.ti.com/.../api-rate-limiting-information-is-needed-for-three-api-s-for-our-account

Last week I was able to call this API and get a response, I haven't made any calls to it since then until today. Today all my requests have failed with the 429 error. I made 4 or 5 requests with maybe 5 minutes between each (I don't normally plan on making that many requests to this endpoint per day, I was just making sure the 429 error wasn't a fluke).

With Mulesoft I don't get return headers but with Postman I do. The Set-Cookie error looked like the only one that might help diagnose this but I won't put it in this ticket unless you specifically want it; in case it contains confidential data. There were no rate limit related return headers.

over 1 year ago

0 Paul King over 1 year ago

TI__Genius 10096 points

Hi Joshua,

I'll check this out and get back to you later today.

Best regards,
Paul

+1 Paul King over 1 year ago in reply to Paul King

TI__Genius 10096 points

Hi Joshua,

Calling the inventory and pricing API for the entire catalog as you did is limited to 1 call every 4 hours. Calling that API for a specific product is essentially unlimited, which is what the other threads you referenced were communicating. This difference is detailed at https://e2e.ti.com/support/enterprise-automation-integration-group/enterprise-automation-integration/f/enterprise-automation-integration-forum/1126205/faq-ti-api-how-many-times-can-i-make-a-catalog-generic-part-number-gpn-or-orderable-part-number-opn-part-number-query-in-one-day/4188367#4188367, and we'll try to be more careful about explaining that difference in future posts.

On Jan 16, I can see that had a successful call on Jan 16 at 8:56:18am then received a 429 error a few seconds later at 8:56:24am. That wouldn't have been enough time to retrieve the very large response to the first call for the full catalog. We recommend limiting your calls to the inventory and pricing API for the specific products you are interested in, or to allow sufficient time to process and retrieve the catalog data and for the 4-hour limit to pass.

I hope that helps.

Best regards,
Paul

0 Joshua Stein over 1 year ago in reply to Paul King

Prodigy 20 points

Thanks very much Paul! I appreciate the investigation into what calls were made. I don't remember making two calls in such quick succession but I must have. I'll keep the 1 per 4 hours rate in mind.

0 Joshua Stein over 1 year ago in reply to Joshua Stein

Prodigy 20 points

I'd like to add for anyone looking at this in the future: The reason I made those two requests in quick succession was because I was getting a remotely closed error on the first request and Mulesoft was automatically retrying the request. The reason Mule was getting a remotely closed error was because of the size of the response. I had to check the "Stream response" box in the request configuration in Mule for it to work.

**Attention** This is a public forum

API solutions

API solutions Forum

TI-API: 429 Too Many Requests Error on Pricing And Inventory API