Skip to main content
BETA — APIs in this section may change. They power partner integrations (lenders, 3PLs, agentic buyers, KYB providers) and are in active iteration. Pin versions in production code and watch the changelog.
The Developers section documents the partner-facing surfaces of the Droplinked platform — the read-and-write API contracts that lenders, 3PLs, agentic buyers, KYB providers, and large merchants integrate against. These complement the public commerce API in the API Reference; pick this section if you’re building an integration that consumes inventory data, submits a lending application, or routes around the merchant onboarding cohorts.

​
What you can do here

InventoryOS API

Eight inventory data streams (catalog, inventory level, sell-through, return rate, pricing, attribution, settlement, provenance) read via REST + delivered via webhook subscriptions.

Lending Application API

Submit, update, and review merchant lending applications. State machine + per-cohort doc checklist + CredibleX referral model.

KYB Cohorts

The cohort taxonomy that routes a merchant’s KYB sources, MoR entity, and lending tier.

​
Authentication

There are two distinct auth schemes in this section — match the scheme to the surface:

​
InventoryOS API keys

InventoryOS keys are bound to a single merchant’s shop. Send the key in the x-droplinked-api-key header. (x-gravitee-api-key and the ?api_key= query parameter are also accepted for gateway compatibility.)
Every row returned is filtered server-side to the merchant the key is bound to — a key physically cannot read another merchant’s data, regardless of the scope grant.

​
Scopes (InventoryOS API)

Scopes are additive and bound to the key at creation time. A key with * is granted all scopes. Issue separate keys for separate integration responsibilities — don’t mint one omni-scope key.

​
Rate limits

InventoryOS rate limits are per-stream, applied at the handler level plus an in-process per-(key, stream) counter so one integration polling catalog can’t starve another hitting settlement on the same key. Exact per-stream limits are published live on the unauthenticated manifest endpoint.

​
Pagination

InventoryOS list endpoints use opaque forward-only cursor pagination. Pass ?limit= (1–200, default 50) and follow nextCursor until it’s null.
Response envelope:
The cursor is the base64url-encoded id of the last row on the page — it’s opaque, don’t parse it, and don’t reuse cursors across keys or streams.

​
Environments

Data is isolated per environment. Build and test against development; promote to production with production-environment keys.

​
Issuing keys

InventoryOS API keys are minted through the API-key management surface:
This is the same ApiKeyV2 surface that powers other partner integrations; bind the inventory-os:* scopes you need at creation time. For Tier-1 CredibleX referral access and Tier-3 vault decisioning, contact partners@droplinked.com.

Next: InventoryOS overview

The eight streams, the consumer surfaces, and the data-layer thesis.