The Kernvel Developer Platform
The eight apps listed below expose documented merchant APIs for selected data they own. Each reference sets out its own scopes, limits, test behavior, and safety rules.
Learn It Once, Use It Everywhere
Pick up any Kernvel API and the basics feel familiar: scoped keys, predictable errors, signed webhooks, and plain examples. The details that matter — test behavior, write safety, plan gates, and PII access — live in each app's own reference.
Scoped API Keys
Create keys from your app's admin and grant each one only the access it needs — read-only or read-write, narrowed to the resources it should touch. Rotate or revoke any key instantly, so a key for one integration can never do more than that integration's job.
Safer Writes
Write endpoints document the safety rail they expect: idempotency keys where supported, validation errors where a retry needs a fix, and plan gates where an action is not available. Check the endpoint notes before building retry logic.
Signed Webhooks
Subscribe to the events that matter and Kernvel pushes them to your endpoint the moment they happen — every payload signed so you can verify it really came from us. React in real time instead of polling for changes.
Test Behavior Called Out
Use each app's reference to see what its test keys do before you point an integration at production. Some APIs provide non-destructive sandbox flows; availability and onboarding requirements are called out in the app-specific reference.
Examples First
Each reference is written around the job a merchant or partner is trying to do, with scopes, request and response shapes, notable errors, and copy-paste curl and JavaScript examples.
Predictable Errors & Limits
Clear, consistent error codes tell you exactly what went wrong and how to fix it. Rate limits are documented and returned in the response headers, so your client can back off gracefully instead of guessing.
Pick an App, Read the Reference
These eight apps offer documented merchant REST APIs. Choose the app that owns the data you need, then check its reference for endpoints, scopes, examples, errors, and webhooks.
AuctionAI API
Create and manage auctions, read bids and products, inspect account usage, and react to auction and bid events from your own systems.
ListIQ API
Read wishlists and wishlist items, pull demand signals and conversion analytics, and trigger or track email campaigns programmatically.
GateIQ API
Manage locks, members, memberships, approval requests, analytics, account usage, and membership/access events from your own systems.
StockIQ API
Pull demand forecasts and inventory alerts, read and create purchase orders, query supplier scores, and sync inventory signals into your own tooling.
ReturnsIQ API
Read and manage returns, return items, refunds, return reasons, policies, fraud signals, account usage, and return webhooks.
Image SearchIQ API
Run visual searches by image, manage your indexed catalog, read auto-extracted product attributes, and pull the demand signals from what shoppers search for.
VendorIQ API
Read vendors, vendor products, order splits, payouts, commission rules, and invoices; update selected vendor and product fields; schedule or complete payout records; and subscribe to supported events. Local delivery, menus, the money ledger, returns, and disputes are separate app workflows.
SupportIQ API
Read and post conversation messages, manage escalations and knowledge articles, pull voice-of-customer insights, and subscribe to conversation webhooks.
DeliveryIQ and Kernvel Mobile App Builder do not currently offer a supported merchant API-key REST API. Their Shopify, shopper, driver, and private app-connection routes have separate access rules. See the DeliveryIQ integrations guide or AppBuilder local-shopping help for supported paths.
Apps That Talk to Each Other
Beyond the public API, Kernvel apps share signals with each other privately — a no-code layer called Connections. It's how the suite gets sharper the more of it you run.
Store-Scoped Connections
Compatible apps can connect for the same Shopify store. Some signals have a switch in Connections; others need setup in a companion app. Each app's integrations guide explains the available controls.
Purpose-Limited Data
Inventory and return signals use counts and rates. Shopper features can use a verified customer's own order or delivery details when that is necessary for the feature. Private app connections are authenticated and tied to the merchant store; they are not the merchant public API.
Got an Integration in Mind?
Browse any app's API reference to get started, or tell us what you're building and we'll point you at the right endpoints. We build APIs the way we build everything — to actually be used.