Drive QRSansar from your own code

When the API is the right answer

Not for ten codes. For codes that follow your own data: one per SKU, per table, per asset, per shipment. Anything where a human copying values between two systems would eventually paste the wrong one.

Getting started

1. Open API tokens in your dashboard and create a token. It is shown once.
2. Send it as a bearer token on each request.
3. Start with a read call to confirm authentication before you write anything.

Rate limits and where they bite

Requests are limited per token, per minute, and the ceiling is higher on Enterprise than on Premium. Both are admin-configurable, so read the current numbers rather than hardcoding an assumption. If you are creating codes in bulk, add a small delay between requests rather than retrying hard on a rejection: a backoff that doubles is kinder to your own job than a tight loop.

Keep the token out of your repository and out of the browser. A token in client-side code is a token anyone can read.