A real REST API connects your wholesale portal with your ERP, your CRM, your custom app — and now with AI agents like Claude or Codex too. Orders, stock, customers and SKUs travel both ways with a Bearer token.
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 — or your AI agent — a standard REST door to read and write what matters, with no manual exports and no spreadsheets stepping on each other.
Flat REST, JSON and a Bearer token: the language your systems already understand — and the native language of AI agents.
The ERP pulls the new orders, invoices them and sends updated stock and prices back. You load the merchandise once in your system and the store mirrors it on its own — no exported spreadsheets, no retyping.
See ready-made ERP integrationsBuyer onboarding, account balances and the assigned price list travel between the CRM and the store. Your reps see in their usual tool what each customer bought, owes and can buy.
How sales reps workAn agent like Claude Code or Codex reads this API like a blueprint: ask it for the ERP integration and it writes it, tests it against the console and leaves it running — what used to be a job for a consulting firm. It can also run the store for you: check pending orders every morning, push the warehouse stock or build the report you always do by hand.
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.
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.
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.
Authorization: Bearer … on every request. No three-legged OAuth, no complicated signatures.Registers a wholesale buyer or a seller from an external system — replicate the onboarding you already do in your ERP.
Lists the orders pending sync from a cutoff date, so the ERP pulls and processes them locally.
Marks an order as already synced in the ERP, with an optional external identifier and invoice type.
Sends stock updates from the ERP: a batch of SKUs with their available quantity. The most frequently used one.
Updates buyer data: account balance, assigned price list and special terms.
Downloads the platform's SKU codes to reconcile them with your ERP's.
Sends a batch of SKUs with their prices and related data from the ERP into the store.
Creates an order on behalf of an existing customer — with their prices, discounts and taxes computed by the store's own engine.
Endpoints with clear HTTP verbs, JSON both ways, ISO dates and consistent error codes. What your backend expects from a serious API.
One token per business, in each call's header. Rotate it whenever you want and each one carries its own rate limit.
Stock, SKUs and customers go in batches: a JSON array with the expected structure and each endpoint's example as a template.
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.
Test with real data in a sandbox business and validate the batch structure before plugging in the production ERP.
Creating an order from the API runs through the store's same pricing, discounts and tax engine. No made-up per-request prices.
Give your technical team — or your AI agent — the API and the console to connect your ERP, your CRM or your custom app. And stop moving data by hand.