domain: digikey.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm your company has an active DigiKey Credit account — the Ordering API requires ordering on account, not just an API subscription.
Register an application, subscribe to the Ordering API product, and complete the OAuth 2.0 3-legged (authorization code) flow; Ordering only supports 3-legged OAuth.
Exchange the authorization code for an access token at https://api.digikey.com/v1/oauth2/token.
POST https://api.digikey.com/Ordering/v3/Orders with Authorization: Bearer <token> and X-DIGIKEY-Client-Id headers, and an OrderRequest JSON body containing PurchaseOrderNumber, Currency, ShippingContact, BuyerContact, and one or more LineItems (DigiKeyPartNumber or ManufacturerPartNumber, RequestedQuantity, UnitPrice).
Read the OrderResponse for SalesOrderId (0 = Marketplace-only order; -1 = order received but a SalesOrderId hasn't been generated yet — don't resubmit).
Poll order status afterward with the separate Order Status API using the returned SalesOrderId or a date range.
Known gotchas
Ordering is 3-legged-OAuth-only — client-credentials (2-legged) tokens are not accepted.
UnitPrice on each LineItem is your expected price and is checked against DigiKey's actual price, so refresh pricing right before ordering.
SalesOrderId = -1 means the order was received and is processing; resubmitting creates and charges a duplicate order.
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?