Your storefront.
Our digital inventory.

From bot to first request

1. Create your API key

   Open @DigikeyhubBOT in a private chat. Choose API → Create API key. Opening the API menu alone does not create a key. Save the secret when it appears; it cannot be displayed again.

2. Fund your wallet

   Use the bot's Wallet menu. Your integration spends this same balance. API prices match bot checkout prices; any reseller discount is assigned by the shop.

3. Check your account

   Set KPS_API_KEY as a secret environment variable on your server, then send the request below.

curl 'https://digikeyhub.com/api/customer/me' \
  -H "Authorization: Bearer $KPS_API_KEY"

{
  "user": {
    "id": "YOUR_ACCOUNT_ID",
    "walletBalance": "50"
  }
}

Authentication

Include your key in the Authorization header on every API request. All examples use HTTPS and JSON. The documentation and OpenAPI file are public; account and purchase endpoints require authentication.

Authorization: Bearer kps_YOUR_SECRET_KEY
Content-Type: application/json

Access requires an active account, an active key, account API permission, and the shop's API service to be enabled. Key creation in the bot enables API access for your own account without granting administrative permissions.

Pricing & balance

All amounts are USDT decimal strings with up to six decimal places. Use decimal arithmetic in your integration. The API and bot share your wallet and purchase-pricing rules.

• GET /products returns your unit price for quantity one.
• Quantity promotions and an optional coupon are applied when an order is purchased. The order's totalAmount is the final amount charged.
• The server calculates prices. Do not send a price, discount, wallet balance, or another account ID in an order request.
• Only prepaid wallet payment is supported. Zero or negative purchase totals are rejected.

A product listing is not a stock reservation. Availability and product limits are checked again during checkout.

Retries without duplicate purchases

An idempotency key identifies one intended purchase. It must contain 16–128 ASCII letters, digits, underscores, or hyphens. A UUID is suitable.

• On a timeout, lost connection, or server error, retry the same body with the same key.
• A successful replay returns the original order with 201, without another charge or allocation.
• Changing the body while reusing a key returns 409 IDEMPOTENCY_CONFLICT.
• Keys are scoped to your account and remain associated with their orders, including across API-key replacement.
• A new idempotency key represents a new purchase. Do not generate one just because a response was lost.

After an uncertain response, check the existing order if you have its ID. Otherwise, resubmit the original request and key. An upstream delay does not mean the purchase failed.

Order lifecycle

Start polling after a few seconds and increase the interval if the order remains pending. Webhooks and reseller cancellation/refund endpoints are not currently available. A supplier timeout requires reconciliation by the shop, not an automatic replacement purchase.

Server-side code examples

These examples require KPS_API_KEY and a persisted PURCHASE_REQUEST_ID in the server environment. Set PRODUCT_ID to a real catalog ID. Running the purchase code spends wallet funds.

// Node.js 18+. Reuse the SAME request ID and body after a timeout.
const key = process.env.KPS_API_KEY;
const requestId = process.env.PURCHASE_REQUEST_ID;
const productId = process.env.PRODUCT_ID;
if (!key || !requestId || !productId) throw new Error('Missing configuration');

const response = await fetch('https://digikeyhub.com/api/customer/orders', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${key}`,
    'Content-Type': 'application/json',
    'Idempotency-Key': requestId
  },
  body: JSON.stringify({ productId, quantity: 1, paymentProvider: 'WALLET' }),
  signal: AbortSignal.timeout(20000)
});
const result = await response.json();
if (!response.ok) throw new Error(result.code || result.error || 'Request failed');
// Store result.order.id and result.order.status in your database.
// Do not log deliveryPayload or API keys.

# Python 3. Standard library only. Persist the request ID before calling.
import json
import os
from urllib.request import Request, urlopen
from urllib.error import HTTPError

request = Request(
    'https://digikeyhub.com/api/customer/orders',
    data=json.dumps({
        'productId': os.environ['PRODUCT_ID'],
        'quantity': 1,
        'paymentProvider': 'WALLET'
    }).encode(),
    headers={
        'Authorization': 'Bearer ' + os.environ['KPS_API_KEY'],
        'Content-Type': 'application/json',
        'Idempotency-Key': os.environ['PURCHASE_REQUEST_ID']
    },
    method='POST'
)
try:
    with urlopen(request, timeout=20) as response:
        result = json.load(response)
        # Store result['order']['id']; protect delivery data.
except HTTPError as error:
    result = json.loads(error.read())
    raise RuntimeError(result.get('code') or result.get('error')) from None
# For connection/timeout errors, retry the original body and request ID.

Errors & rate limits

Error responses contain error, and may also contain a machine-readable code or field-validation details. Check the HTTP status first; do not assume every error has a code.

{
  "error": "INSUFFICIENT_WALLET_BALANCE",
  "code": "INSUFFICIENT_WALLET_BALANCE"
}

The application limit is 120 requests per minute per account and connection IP, per backend instance. Shared proxies may share the connection limit. Poll conservatively and respect any additional edge limits. Rate-limit responses include Retry-After.

Keep your integration secure

• Use HTTPS with certificate verification enabled.
• Keep API keys in a server-side secret store. Never send a key to an unofficial URL.
• Protect delivered keys and account credentials in your own storage and logs.
• Revoke or replace exposed keys in the bot. Replacement invalidates all existing keys for your account.
• Persist purchase IDs and idempotency keys, and retain an auditable mapping to your customer orders.
• Do not resell an item twice or automatically return already-exposed credentials to your stock after a refund.

Authenticated responses are marked Cache-Control: no-store. The API never provides another account's orders or raw supplier responses.

Frequently asked questions