This thread has been locked.

Does it make sense to create API?

Hello,

After spending some time learning about this API framework, I can say that everything is now in place.
In addition, I've created a database to track how many of the parts I wish to purchase are readily available.

But after a few months, I see that there will be regular replenishment, always below a particular level.
As a result, the inventory that would alert me to new manufacturing will never be initiated.


I need to purchase roughly 10,000 pieces, but it seems that the API idea is out of my expectations and merely gives me the illusion that I would succeed sometime.
Am I mistaken or is there a problem?
Or is there really little manufacturing throughout the year?

Any response to this query would be helpful to my understanding of the current procedure. I therefore appreciate any advice in advance.

Thanks again.

  • Hi Far,

    Inventory availability fluctuates based on customer demand and the need to reserve some product for samples.   We are always replenishing our products, to try and meet the demands of our customers, but, there are no guarantees, since other customers are always ordering.  Some tips we offer:

    • Make sure the product you want to order is available;  Go to TI.com and if the part states "not available" (see below), this means you will not be able to purchase this product and we have no timeframe of when the product will be available again.

    • Set up an Inventory Subscription to real-time monitor the status of products. The inventory subscription (https://api-portal.ti.com/store-inventory-subscription-push-api ) is a notification that can be configured to notify you when parts have been stocked up with the quantity that you need.  When a part has stocked up, this API will generate a notification that is sent to your configured API via an HTTP POST request.  Here's an FAQ that shows the details of the API.  One suggestion when setting up your subscription  - set your quantity to a reasonable amount, so, that you have a greater chance of being notified sooner. 

    • Last suggestion, if you decide to take advantage of the inventory subscription API, you might want to program some automation between the inventory subscription and the Order API, so that once the subscription notifies you, the order API will order the product automatically.

    Regards,

    Faye

  • I appreciate your response.
    Indeed, I followed all of the instructions you provided. Every day, I check my email to see if I have any notifications from API Inventory.
    But it appears that my expectations were too high, as if this were a routine mass manufacturing.
    Thank you, it is now clearer.

    Routine

    Substantiv: Routine, Übung, Trott, Ordnung, Schablone, Figur
    Adjektiv: routinemäßig, laufend

  • Hi Far,

    To follow-up, I looked at our logs and noticed that the API call you are currently making is /v2/store/products/ - which is not the inventory subscription API call. The last time you tried to execute the inventory subscription API  (v2/store/subscriptions/inventory) was on 04Nov.  At that time we were experiencing some issues with PUSH API calls late last year, and I believe your PUSH API calls were failing as a result of that.   I executed a test (a ping between servers) using your credentials and it successfully executed.  I would suggest that you re-try  the subscription API again.     If you encounter further problems, you can you review our FAQ on PUSH API Best Practices .

    Also, it's suggested to know if there are any limits on products before setting up your subscription API.  This way you can at least eliminate the easy failures.  From looking at the logs, a couple of products you were trying to order do have limits on them, so, you cannot order more that those limits.

    Regards,

    Faye

  • Hello Faye,

    Thank you for evaluating my case.
    In fact, I created two systems to check the product availability.
    The first is based on the explanations at "">api-portal.ti.com/store-api-getstarted," which uses "v2/store/products/." In regular intervals throughout the day, this receives the available quantity of the products. 
    The other, which uses (v2/store/subscriptions/inventory), is based on "">api-portal.ti.com/store-inventory-subscription-push-api" back-in-stock notifications. When you send a notification that a part has stocked up, this will be used. 


    When a product is finally available, at both cases, it place an order by using this "URL: /store/orders".
    Both systems have so far performed satisfactorily.

    However, after using "/store/products/tiPartNumber" and evaluating the findings over the course of several months, I found that there had been no change in the production of the parts I was hoping to be able to buy in considerable quantity.

    Of course, in both circumstances, the limit is taken into account.

    In general, I was informed by your colleagues that production doesn't happen on a regular basis or frequently in a year.

    Best regards,

    Far

  • Far,

    First, I am glad that you are able to successfully execute the other queries and receive product information.   With regards to executing the /store/products/tiPartNumber query, I would like to get more information from you and have sent you a friend request so that we can communicate privately. 

    As it pertains to product replenishment, there is no set schedule that is followed for products, which is why the v2/store/subscriptions/inventory API is recommended (which you are already using).

    Look forward to you accepting my friend request.

    Faye

**Attention** This is a public forum