Products
Read and write products, variants, categories, images and stock levels.
Developers
Build on top of a merchant's commerce data
A REST API and signed webhooks, so the systems a business already runs can read and write the same records the dashboard does.
What the API covers
Every endpoint runs through the same service layer as the dashboard. There is no second, lagging copy of the business logic behind the API.
Orders
List, create and update orders, including status transitions and fulfilment.
Inventory
Adjust stock, read movements and query availability across locations.
Customers
Customer records, addresses and order history.
Payments
Read payment status against orders. Payments themselves are initiated through the provider.
Webhooks
Subscribe to order, payment and fulfilment events, delivered as signed POSTs with retries.
Webhooks, and why they matter more than polling
An API lets your system ask what changed. A webhook tells it. Subscribe to events like order created, payment successful and order shipped, and SellTrove sends a signed POST to your endpoint — with retries and backoff on failure, and a delivery log per attempt so you can see exactly what was sent and what came back.
That is what makes integrations with accounting tools, logistics partners and custom messaging bots practical without hammering the API on a timer.
Developer questions
Premium. Webhooks for your own store are available on Basic and above.
A scoped API key per business. Each key carries only the permissions you grant it — read products without write access, for example.
Yes, per key. Limits and current usage are returned in response headers so an integration can back off rather than guess.
Any request that creates money-moving state accepts an Idempotency-Key header. A retry with the same key replays the original response instead of creating a second order.
Breaking changes ship as a new version in the URL path. Existing versions keep working, and deprecation is announced with a migration window.