🧩 One API model · Six apps

The Kernvel Developer Platform

Every Kernvel app is a real product with a real API behind it. Read and write your data programmatically, wire Kernvel into your own systems, and automate the work you'd otherwise click through by hand — all on one consistent, plain-English API model that's the same across every app.

Learn It Once, Use It Everywhere

Pick up any Kernvel API and it works the way you'd expect — the same auth, the same safety rails, the same shapes. No per-app surprises.

🔑

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.

♻️

Idempotent Writes

Send an idempotency key with any create request and a retry after a dropped connection won't double-charge, double-refund, or duplicate a record. Safe retries are built into the contract, not bolted on — so your integration can recover from a timeout without fear.

🪝

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.

🧪

Sandbox / Test Mode

Build and test against a safe test mode before you touch live data. Exercise the full request/response flow — including webhooks — without issuing a real refund or emailing a real customer, then flip to production with the same code.

📘

OpenAPI & Examples

Every endpoint is documented with its request shape, response shape, scopes, and copy-paste curl and JavaScript examples — backed by an OpenAPI description so you can generate a client in your language of choice.

📊

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

Each app exposes its own REST API for the data it owns. Jump straight to the full reference — endpoints, scopes, examples, errors, and webhooks — or read the user guide and integrations alongside it.

🔨

AuctionAI API

Create and manage auctions, read bids and bidders, pull AI pricing suggestions, and react to bid and auction-end events from your own systems.

API Reference →

User Guide  ·  Integrations

💖

ListIQ API

Read wishlists and wishlist items, pull demand signals and conversion analytics, and trigger or track email campaigns programmatically.

API Reference →

User Guide  ·  Integrations

🔐

GateIQ API

Manage locks and conditions, check access decisions, read and update members and memberships, and listen for access-granted and membership events.

API Reference →

User Guide  ·  Integrations

📦

StockIQ API

Pull demand forecasts and inventory alerts, read and create purchase orders, query supplier scores, and sync inventory signals into your own tooling.

API Reference →

User Guide  ·  Integrations

📮

ReturnsIQ API

Read returns and their fraud scores, create and resolve return requests, issue refunds or store credit, and react to return events in real time.

API Reference →

User Guide  ·  Integrations

🔍

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.

API Reference →

User Guide  ·  Integrations

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.

🔗

One Toggle, No Code

When you have two Kernvel apps on the same store, the relevant connection appears in each app's Connections screen. Flip a single switch to turn it on — there's nothing to build, export, or import. Turn it off any time; nothing is shared until you say so.

🛡️

Signals, Never Customer Data

Connected apps exchange only the minimum needed — counts, rates, and product or vendor identifiers. They never pass raw shopper data, email lists, or personal information between each other, and each side verifies the other privately before anything moves.

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.