Workbench developer docs中文

TrustedParts

Base URL

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

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

It's TrustedParts's own API

Everything after the base URL is TrustedParts' API (its documentation comes with your TrustedParts API account), exactly as TrustedParts 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 TrustedParts key on the server. You never see that key.

Notes

Examples

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

wb

wb call trustedparts v2/search --data '{"Queries": [{"SearchToken": "MMBT3904"}]}'

curl

curl "https://desktop-api.wbench.io/v1/proxy/trustedparts/v2/search" \
  -H "Authorization: Bearer $(wb token)" \
  -H "Content-Type: application/json" \
  -d '{"Queries": [{"SearchToken": "MMBT3904"}]}'

Python

TrustedParts 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/trustedparts/v2/search",
    headers=headers,
    json={"Queries": [{"SearchToken": "MMBT3904"}]},
    timeout=60,
)
r.raise_for_status()
print(r.json())

TypeScript

const r = await fetch("https://desktop-api.wbench.io/v1/proxy/trustedparts/v2/search", {
  method: "POST",
  headers: { Authorization: `Bearer ${process.env.WB_TOKEN}`, "Content-Type": "application/json" },
  body: JSON.stringify({"Queries": [{"SearchToken": "MMBT3904"}]}),
});
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.