search digikey products by keyword using oauth2 client credentials
domain: digikey.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register an application at developer.digikey.com and subscribe it to the Product Information V4 API to get a client ID and client secret.
Get a 2-legged OAuth2 access token: POST https://api.digikey.com/v1/oauth2/token (sandbox: https://sandbox-api.digikey.com/v1/oauth2/token) as x-www-form-urlencoded body with client_id, client_secret, grant_type=client_credentials.
Call POST https://api.digikey.com/products/v4/search/keyword with headers Authorization: Bearer <access_token>, X-DIGIKEY-Client-Id: <your client ID>, X-DIGIKEY-Locale-Site, X-DIGIKEY-Locale-Language, X-DIGIKEY-Locale-Currency.
Send a JSON body with a Keywords string (up to 250 chars) plus optional RecordCount, Offset, FilterOptionsRequest, and SortOptions.
Parse the KeywordResponse for matched Products — note MyPricing is never returned here, only StandardPricing.
Known gotchas
2-legged access tokens expire in 10 minutes per the 2-Legged Flow doc (a separate FAQ page cites 30 minutes generally) — either way, refresh often.
KeywordSearch pricing/quantity data is cached and can be up to 24 hours stale; use ProductDetails or ProductPricing for real-time numbers.
Exceeding limits returns 429 with X-RateLimit-*/X-BurstLimit-* headers and a Retry-After value; sandbox mode always returns the same example product regardless of query.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?