Build your customer portalintegration

Yes. Qoblex has a REST API covering close to everything the app does: products, variants and stock, sale orders, shipments, invoices and payments, quotes and customers, purchase orders, goods receipts, bills and suppliers, manufacturing orders and kits, batches, adjustments and transfers, reporting and custom fields. You authenticate with a key you generate in your own account, send and receive JSON, and every endpoint sits under /v1. The API reference lists all of them with working examples.

Yes, or somebody who writes code for you. There is nothing exotic in it, REST URLs, JSON in and JSON out, standard HTTP verbs and status codes, and filtering, sorting and pagination that work the same way on every list, but it is programming. There is no partner programme, no certification and no separate developer account to apply for: an API key and the reference are the whole of it.

In your own account, and without asking us. Open Integrations, find the API tile, install it and create a key, then send it as the qoblex-x-api-key header on every request. Revoke it from the same screen if it ever leaks. There is no application to fill in and no separate developer account.

No. We do not take on integration work, because it would make us responsible for code we do not run and cannot support properly. We do help the people who build it: your developers can ask us how something behaves and get a real answer, which is usually what decides how long the work takes.

Webhooks. Your endpoint is called when a record changes, so your integration can react to a new order, a dispatch or a stock movement as it happens rather than on the next poll. Polling still works where it suits you better: list endpoints take filters and sorting, so asking for what changed since your last run is one request rather than a download of everything.

Yes. One API key may make 30 requests every 60 seconds. The limit applies per key, so one integration can never use up another’s capacity and nothing you build slows down your team in the app. Every response reports the limit and what is left of it, and a 429 tells you how many seconds to wait. List endpoints return up to 50 records a page. Filtering, sorting and expandable responses are there so that a job which sounds like thousands of calls is usually a handful.

Yes. Permissions are expressed as scopes, each pairing a resource (sale orders, products, purchase orders, reporting, manufacturing) with an action (view, create, edit, delete, authorize, approve), and a key inherits the permissions of the integration it belongs to. Grant each key only the scopes its job needs. Enforcement is being switched on area by area as each part of the product moves onto our new experience, so scopes you set now are respected automatically as each endpoint comes online.

It should not. Everything lives under /v1 and the API evolves additively: new endpoints, new fields and new values can appear at any time, so build your integration to ignore what it does not recognise and not to depend on the order of fields. Anything genuinely breaking gets a new version in the path, and this one keeps running while you move.

Not yet, and it is on the list. In the meantime a no-code platform can call the API directly with its generic HTTP step, and webhooks give it something to trigger on.

It is a paid add-on on Starter and Business, and included on Scale. It is also fully active during the free trial, so an integration can be built and tested before anyone commits to it. See pricing for current terms.