The MSP ProDesk Vendor API Console is a single-file HTML dashboard that centralizes MSP procurement workflows across Ingram Micro and TD SYNNEX. It gives procurement teams a unified interface for product search, real-time pricing, BOM optimization, order submission, shipment tracking, spend analytics, and market intelligence — without switching between vendor portals.

The console runs in full demo mode out of the box — all data is generated from the static products[] array and hardcoded mock objects. When PROXY_BASE is set, each action calls the proxy which routes to the real vendor APIs and returns normalized JSON. The UI, render functions, and interaction model are production-ready and require no changes to go live.

Every data-fetching action, button, and displayed endpoint path was audited against live vendor documentation before any code was changed. The following table is the complete finding set.

The console is a self-contained single HTML file. No framework, no CDN dependencies except Google Fonts. All rendering is pure DOM manipulation using template literals.

The default landing pane. Shows a search bar, category/stock filter chips, and a responsive product grid. Filtering is instant as-you-type — no button press needed after initial load. The search button fires runSearch() and also shows the response terminal panel below the grid.

Two-column layout: left has order configuration (vendor, PO number, shipping, line items); right shows the cart summary, order total, estimated lead time, and an API endpoint preview panel.

BOM-driven procurement optimization. Three hardcoded demo items (Fortinet FG-70F, Ubiquiti USW-48-POE, Ubiquiti U6 Pro). Compares Ingram vs SYNNEX pricing and stock for each line, then routes each item to the cheapest available distributor.

Enter any order ID in the input and click TRACK. Three demo orders are wired: IM-2024-091422 (Ingram, in transit), TD-2024-003291 (SYNNEX, processing), IM-2024-091380 (Ingram, delivered). Unknown IDs fall back to the first demo order.

Opens via the Analytics nav pill. Triggers animateAnalytics() which animates sparkline bars and vendor split bars. All values are hardcoded — no live data connection in any field of this pane.

Five intelligence cards. All static demo data. No vendor API natively supports stock predictions, hardware substitution rankings, or client hardware profiles — these features require a proxy-side analytics layer built on top of vendor API data.

These are genuine vendor API gaps — features the console displays that no vendor API can fulfill directly. Each is documented in the dashboard source code with a comment. Your proxy must implement workarounds where noted.

• 1
  Get OAuth tokenYour proxy must call POST https://api.ingrammicro.com:443/oauth/oauth20/token with grant_type=client_credentials and your client credentials from Key Vault. Cache the token (expires in ~3600s). Add it as Authorization: Bearer {token} to every downstream call.
• 2
  Product search endpointWire GET /api/ingram/catalog?keyword={q}&pageSize=50 → proxy calls GET /resellers/v6/catalog/productsearch?keyword={q}&pageSize=50&pageNumber=1. Map the response catalog[] array to the console's products[] shape (vendor, sku, name, desc, price, stock, lead, cat).
• 3
  Price and availabilityWire POST /api/ingram/pricing (body: {skus:[]}) → proxy calls POST /resellers/v6/catalog/priceandavailability with body {products:[{ingramPartNumber,quantity}]}. Returns pricing, stock by warehouse, discounts. Note: this is a POST, not GET — the console was logging it incorrectly before the audit fix.
• 4
  Order creationWire POST /api/ingram/orders → proxy calls POST /resellers/v6/orders. Required body fields: customerOrderNumber, shipToInfo, lines[]. The proxy must also include IM-CustomerNumber, IM-CountryCode, and IM-CorrelationID headers on every call.
• 5
  Order trackingWire GET /api/ingram/orders/{id} → proxy calls GET /resellers/v6.1/orders/{orderNumber}. Map the response's shipmentDetails and orderStatus into the step-timeline format the tracking pane expects.

• 1
  SOAP client in proxyAdd a SOAP client library to your Function App (e.g. node-soap for Node.js). Load the WSDL from https://ws.synnex.com/webservice/pnaserviceV05?wsdl. Authenticate with your EC Express customer number and password (stored in Key Vault).
• 2
  P&A (Price and Availability)Wire POST /api/synnex/pricing → proxy calls pnaserviceV05.getPriceAndAvailability({skus:[]}). Parse the XML response — each item has <price>, <qty>, <status>. Return normalized JSON matching the Ingram P&A shape so the BOM optimizer can compare them directly.
• 3
  Order submissionWire POST /api/synnex/orders → proxy calls poserviceV02.submitPO({...}). SOAP PO body includes: customer number, PO number, ship-to info, line items with vendor part numbers, quantities. Returns an order confirmation number.
• 4
  Order statusWire GET /api/synnex/orders/{id} → proxy calls posserviceV02.getPOStatus({poNumber}). Returns shipment status, carrier, tracking number. Map to the same step-timeline format used by the Ingram tracking response.
• 5
  Cloud licenses (StreamOne Ion)Wire POST /api/synnex/licenses → proxy calls POST https://ion.tdsynnex.com/api/v3/accounts/{id}/subscriptions with Bearer token from StreamOne Ion. This path is only for SaaS products (Microsoft 365, Acronis, etc.) — not physical hardware.

• ✓
  PROXY_BASE set. Updated in the dashboard's script block to your Function App URL (or left empty if same-origin).
• ✓
  DEMO_MODE = false during testing. Set to false so fetch errors appear in browser console. Return to true for production if you want silent fallback.
• ✓
  Ingram credentials in Key Vault. Application Settings show @Microsoft.KeyVault(...) reference strings for ingram-client-id, ingram-client-secret, and ingram-customer-number.
• ✓
  SYNNEX EC Express credentials in Key Vault. synnex-customer-number, synnex-ec-username, synnex-ec-password — used for SOAP calls.
• ✓
  StreamOne Ion credentials in Key Vault (if wiring cloud products). ion-client-id, ion-client-secret or ion-refresh-token.
• ✓
  Product search returns results. Open the Search pane, type "cisco", check DevTools → Network tab. Confirm the proxy call to /api/ingram/catalog returns 200 with a JSON array. Products should appear in the grid.
• ✓
  Price check returns live data. Click "Check Pricing" on any product. Confirm POST /api/ingram/pricing returns 200 with price data. Toast should show the actual reseller price from Ingram.
• ✓
  Order submission sandbox tested. Set proxy to point at Ingram sandbox (/sandbox/resellers/v6/orders). Submit a test order. Confirm 201 response with a valid order number. Test account: 20-222222 (Ingram sandbox).
• ✓
  Tracking returns step data. Enter a known order number and click TRACK. Confirm the timeline updates with real steps from GET /resellers/v6.1/orders/{id}.
• ✓
  API call log shows real paths. Open Analytics pane. Confirm all entries in the API Call History log show the corrected /resellers/v6/ paths — not the old /v1/ paths.