Workbench developer docs中文

DigiKey

Base URL

https://desktop-api.wbench.io/v1/proxy/digikey/

Use https://desktop-api.wbench.io/v1/proxy/digikey/ where DigiKey's documentation uses https://api.digikey.com/.

It's DigiKey's own API

Everything after the base URL is DigiKey's Product Information API v4, exactly as DigiKey documents it: the same paths, methods, query parameters and JSON bodies. Only the address and the credential change: you send your Workbench token, and Workbench adds your company's DigiKey key on the server. You never see that key.

Notes

Examples

Set WB_TOKEN first: export WB_TOKEN=$(wb token).

wb

wb call digikey products/v4/search/keyword --data '{"Keywords": "MMBT3904", "Limit": 10, "Offset": 0}'

curl

curl "https://desktop-api.wbench.io/v1/proxy/digikey/products/v4/search/keyword" \
  -H "Authorization: Bearer $(wb token)" \
  -H "Content-Type: application/json" \
  -d '{"Keywords": "MMBT3904", "Limit": 10, "Offset": 0}'

Python

DigiKey has no official SDK for Python or TypeScript, so these examples use plain HTTP.

import os
import requests

headers = {"Authorization": f"Bearer {os.environ['WB_TOKEN']}"}
r = requests.post(
    "https://desktop-api.wbench.io/v1/proxy/digikey/products/v4/search/keyword",
    headers=headers,
    json={"Keywords": "MMBT3904", "Limit": 10, "Offset": 0},
    timeout=60,
)
r.raise_for_status()
print(r.json())

TypeScript

const r = await fetch("https://desktop-api.wbench.io/v1/proxy/digikey/products/v4/search/keyword", {
  method: "POST",
  headers: { Authorization: `Bearer ${process.env.WB_TOKEN}`, "Content-Type": "application/json" },
  body: JSON.stringify({"Keywords": "MMBT3904", "Limit": 10, "Offset": 0}),
});
if (!r.ok) throw new Error(`${r.status}: ${(await r.json()).message}`);
console.log(await r.json());

See Limits and errors for what a refusal looks like.