PROGRAMMATICSTOCK-KEEPINGFOR CLIENTS
A REST API and event bus that keeps your warehouse in stock parity with 888 Wholesale.Read live stock, post atomic transactions, register signed webhooks, and let refill thresholds raise replenishment automatically. Built for ERPs, 3PLs, and in-house operations.
ONE LEDGER. EVERY WAREHOUSE.
Work splits across four independent paths: stock reads, transaction writes, alert evaluation, and webhook dispatch. Reads never block writes, and writes never block delivery, so a busy event bus never slows a stock lookup.
Read latency (99th percentile)
< 40ms
Idempotency window
24h
Event signing
HMAC-256
Uptime target
99.9%
A SMALL SURFACE. DEEP CONTROL.
Keep every warehouse in lockstep with 888: no overselling, no blind stockouts. A handful of resources cover the full lifecycle. Read stock, post transactions, watch alerts, and subscribe to events. Bearer-token auth, JSON in, JSON out.
/v1/stockRead live stock levels and status (OK, LOW, CRITICAL) for one or more SKUs in your warehouse.
curl -H "Authorization: Bearer $WMS_KEY" \ https://www.888wholesale.co/api/wms/v1/stock?sku=TEE-BLK-L
/v1/stock/updateApply a batch of signed deltas (sale, return, damage, adjustment) atomically. Idempotency-Key safe.
curl -X POST -H "Authorization: Bearer $WMS_KEY" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{"transactions":[{"sku":"TEE-BLK-L","delta":-12,"type":"SALE"}]}' \
https://www.888wholesale.co/api/wms/v1/stock/update/v1/alertsList open replenishment alerts raised when a SKU reaches or drops below its refill threshold.
curl -H "Authorization: Bearer $WMS_KEY" \ https://www.888wholesale.co/api/wms/v1/alerts
/v1/webhooksRegister a signed HTTPS callback for alert.triggered, order.shipped, and order.delivered events.
curl -X POST -H "Authorization: Bearer $WMS_KEY" \
-d '{"url":"https://erp.example.com/hooks","events":["alert.triggered"]}' \
https://www.888wholesale.co/api/wms/v1/webhooksENGINEERED FOR CLIENT WAREHOUSES
Real-time stock
Levels and status are written on commit and read back live. No cache sits between your client and the truth.
Threshold alerts
Per-SKU refill thresholds and par levels raise CRITICAL and LOW signals automatically for replenishment.
Signed webhooks
HMAC-signed events for alerts and shipments that you verify on receipt, then reconcile against the API.
Scoped tokens
Per-warehouse tokens with supervisor or worker access. Least privilege by default, revocable in one click.
Append-only ledger
Every sale, return, adjustment, and receipt is recorded with type, quantity-after, source, and timestamp.
Idempotent writes
Client-supplied keys deduplicate retried writes over a 24-hour window so your systems can replay safely.
QUESTIONS & ANSWERS
Common questions about our services, ordering process, and partnership requirements.
Every endpoint uses Bearer token authentication. A token is scoped to a single warehouse and carries either supervisor access (read plus write) or worker access (read-only stock and its own issuance history). Tokens are issued from portal credentials and can be revoked or re-issued at any time from the portal under Warehouse, API Keys.
Stock changes are written synchronously on commit and are immediately visible on the next GET /v1/stock call. Treat the REST endpoints as the source of truth: poll them on your own cadence, and use webhooks as a fast notification layer on top.
Yes. Each warehouse is a separate entity with its own SKU registry, stock levels, and token set. A single account can operate multiple warehouses from the portal, and each warehouse can carry several scoped tokens, for example one per integration plus one per worker device.
Thresholds and par levels are configured by 888 Wholesale. When an order ships to your warehouse for the first time, the matching SKUs are initialised automatically with a sensible par level and threshold, then reviewed. If you want a level changed, raise it with your 888 contact. Partners do not self-register SKUs.
Yes. Every delivery carries an X-WMS-Signature header in the form sha256=<hex>, an HMAC-SHA256 of the exact request body keyed with the secret you receive when you register the webhook. Recompute it on your server and compare with a timing-safe check before trusting any payload.
Webhooks are best-effort notifications. Each event is delivered once with a short timeout, so build your receiver to be idempotent and reconcile against the GET endpoints (stock, alerts, shipments) as the authoritative state. A missed webhook never means missed data: the data is always available over the API.
Point your client at the production base URL and confirm reachability with the unauthenticated GET /v1/health probe. Mint a token, then exercise the flow against a dedicated test SKU and warehouse so you can read, write, and reconcile without touching live programs. Idempotency keys make every write safe to replay during testing.
Pass an Idempotency-Key header (any unique string, typically a UUID) on POST /v1/stock/update or POST /v1/transactions. If the same key arrives again within 24 hours the server replays the original response without re-applying the change, so a retry after a dropped connection can never double-count.
Still have questions?
Contact our team at info@888wholesale.co or call us during business hours.
Get an API key
CONNECT YOUR WAREHOUSE. START SHIPPING TODAY.
Approved clients can register warehouses, mint scoped tokens, and start syncing stock from the portal. Need a custom integration? Schedule a consultation.