Driffle publishes seller API documentation, including a legacy reference covering products, offers, inventory and transactions. Confirm the currently supported version and account permissions before implementing against it.

Legacy documentation needs a version decision

An accessible reference is evidence that documentation exists; it is not a promise that every endpoint remains appropriate for a new integration. Ask which version your account should use and whether migration guidance applies. Record the documentation version used in your implementation.

Avoid mixing response formats from separate versions. Keep a typed integration boundary so a changed field is detected during reconciliation rather than silently interpreted as zero stock or an empty transaction list.

Product and offer mapping

Maintain separate local records for product identity, offer identity and individual stock units. Match region and redemption platform along with the title. A mapping correction should pause the affected offer until the inventory is verified.

For multi-channel stock, use a central reservation process. Marketplace quantities should reflect genuinely available units after reservations elsewhere. A scheduled synchronization that runs every few minutes may still allow a race between two orders; account for that risk in stock limits and fulfillment controls.

Reconciliation before expansion

  • Compare a small set of live offers with local mappings and quantities.
  • Validate transaction identifiers and state changes against dashboard records.
  • Confirm documented pagination before treating an import as complete.
  • Track uncertain writes and reconcile them before retrying.
  • Alert operators on stale stock or missing transaction updates.

Do not equate a successful HTTP response with a fulfilled order unless the documented response establishes that state. Conversely, a timeout can leave a successful remote operation with no local confirmation. Design an exception queue for these cases.

Access and recovery

Keep seller credentials on the server and restrict access to production secrets. Document how to pause writes, rotate access and reconcile inventory after a credential change. Never put keys or tokens in a browser bundle, support screenshot or ordinary log.

Before acquiring an account, confirm whether API access is included, transferable through the permitted process or subject to a new request. Review Driffle requirements and the Driffle product specifications.

Technical reference

Driffle legacy API reference lists the documented resource areas. Verify current support with the platform before deploying a production integration.

Sources and scope

Driffle official reference.

Public sources reviewed on 3 October 2026. Operational checklists and hypothetical examples are KeyMerchantHub planning guidance. Confirm account-specific requirements and current commercial terms with the marketplace.