Flat, predictable REST
Endpoints with clear HTTP verbs, JSON both ways, ISO dates and consistent error codes. What your backend expects from a serious API.
New · Open API
Your store talks to everything else.
A real REST API connects your wholesale portal with your ERP, your CRM, your BI tool or that custom app you had built. Orders, stock, customers and SKUs travel both ways with a Bearer token — and a console lets you test every endpoint without opening Postman.
For the business that already has systems
Your portal is not an island
You already have an ERP that invoices, a CRM that tracks your reps and maybe a BI dashboard where you watch everything. The wholesale store has to talk to them, not live apart. The Open API gives your technical team a standard REST door to read and write what matters — no manual exports, no spreadsheets stepping on each other.
The API console
Test every endpoint without opening Postman
Inside the panel, under Settings → ERP, there's a console that runs real calls against the integration endpoints. Your team pastes the token, fills in the parameters, hits Send and sees the response with the color-coded HTTP status and formatted JSON. No cURL, no external tools.
- Real calls, not mocked: the console hits your actual endpoints. Test with a sandbox business before plugging in the production ERP.
- Quick-start overview: base URL, authentication flow, date format and error codes, with the suggested steps to get going.
- HTTP status in sight: green for 2xx, red for 4xx/5xx, and the formatted, copyable JSON body.
- Ready-to-copy cURL: every endpoint brings its cURL example — the fastest way to move the integration into a script or a scheduled job.
Two-way sync
The ERP reads orders and writes stock. No spreadsheets.
The classic pattern: your system pulls the new orders, invoices them and marks them synced; then it pushes stock and prices back to the store. Each piece is a clear endpoint, and the loop keeps itself while your job runs.
- Pull by cutoff date: ask only for the new orders since the last run. No re-pulling everything each time.
- Close the loop: marking an order as synced drops it from pending — the list doesn't grow forever.
- High-frequency stock: the stock endpoint handles frequent runs, with per-batch size limits so nothing gets throttled.
- Prices and account balance: update the assigned price list and the account balance of each wholesale customer from your ERP.
Authentication
One Bearer token, and you're in
Every call travels with a Bearer token that identifies your business. You generate it from settings, send it in the Authorization header, and the console stores it in the browser so you don't have to paste it on every test. Simple to start, safe for production.
- One header, nothing more:
Authorization: Bearer …on every request. No three-legged OAuth, no complicated signatures. - Rotate it anytime: if you suspect a token leaked, generate a new one and the old one stops working.
- Per-token limit: each token has its own rate limit, so one integration doesn't step on the others.
- Admins only: the console and the tokens live in the admin panel, not in the public store.
The endpoints
Everything your integration needs to touch
POST
register
Registers a wholesale buyer or a seller from an external system — replicate the onboarding you already do in your ERP.
GET
pending-orders
Lists the orders pending sync from a cutoff date, so the ERP pulls and processes them locally.
POST
order-synced
Marks an order as already synced in the ERP, with an optional external identifier and invoice type.
POST
stock-update
Sends stock updates from the ERP: a batch of SKUs with their available quantity. The most frequently used one.
POST
customers
Updates buyer data: account balance, assigned price list and special terms.
GET
skus
Downloads the platform's SKU codes to reconcile them with your ERP's.
POST
update-skus
Sends a batch of SKUs with their prices and related data from the ERP into the store.
POST
orders
Creates an order on behalf of an existing customer — with their prices, discounts and taxes computed by the store's own engine.
Built for your technical team
An API that doesn't fight you
Bearer token
One token per business, in each call's header. Rotate it whenever you want and each one carries its own rate limit.
JSON batches
Stock, SKUs and customers go in batches: a JSON array with the expected structure and each endpoint's example as a template.
cURL on every endpoint
At the bottom of each endpoint there's a ready-to-copy cURL — the fastest way to move the integration into a script or a cron.
Sandbox before production
Test with real data in a sandbox business and validate the batch structure before plugging in the production ERP.
Orders with the real engine
Creating an order from the API runs through the store's same pricing, discounts and tax engine. No made-up per-request prices.
The loop doesn't jam
Mark each order synced and it drops off pending. The list stays short, with no duplicates piling up.
Documented from within
The console itself is the living reference: overview, parameters and response of each endpoint, always in sync with what the API actually does.
Connect what you already have
Plug your wholesale portal into the rest of your operation
Give your technical team the API and the console to connect your ERP, your CRM or your custom app — and stop moving data by hand.