Dear Sir/Madam,
Good day.
My name is Shashank, and I am working as a Component Engineer at Kaynes Technology. I support both the engineering and procurement teams in managing component data.
As part of this effort, I have developed an application using the Digi-Key API to streamline our workflow. However, I am currently facing an issue where the system processes only around 500 MPN (Manufacturer Part Number) records, instead of the required 30,000. This limitation is impacting our operations significantly.
I kindly request your assistance in resolving this issue. Please let me know if you require any additional details, including the API key or technical information.
Your support in this matter would be greatly appreciated.
Thank you for your time and consideration.
For any DigiKey API questions or requests you will need to use the DigiKey API Portal.
If you have technical questions about our parts that we carry we can answer them on the TechForum.
2 Likes
Hi Shashank,
Two things to check before asking DigiKey for a limit bump:
-
Endpoint. The keyword-search endpoint paginates in small batches.
For bulk MPN lookups use the product-details endpoints with pagination
(skip/take) — iterate through chunks and merge results.
-
Rate limit, not daily quota. Production tier throttles around
240 req/min. Hitting the per-minute cap silently truncates at a few
hundred MPN if the client doesn’t catch 429s. Add exponential
backoff on 429/5xx, a limiter at ~4 req/sec, and cap concurrency
at 5–10.
If after that you still hit the daily quota at 30k records, you need
the Marketplace/commercial tier — apply via the developer portal and
mention your EMS volume, upgrades usually go through fast.
One note: DigiKey alone won’t give you lifecycle/EOL and alternative-
parts matching. At 30k MPN that’s where the real exposure sits, not on
cost.
Happy to go deeper on the batching pattern if useful.
