QRbolt API Terms of Use

Last updated: November 7, 2026

1. These terms

These API Terms of Use (the "API Terms") cover your use of the QRbolt application programming interface at api.qrbolt.com, its keys, webhooks, documentation and machine-readable specification (together, the "API"). The API is part of the QRbolt service provided by Incudo Labs Inc., a company registered in British Columbia, Canada ("QRbolt", "we", "us").

The API Terms add to our Terms of Service and Privacy Policy, which continue to apply. Where the API Terms and the Terms of Service disagree about your use of the API, the API Terms apply. The industry-specific sections of the Terms of Service (cannabis, alcohol, tobacco and controlled substances) apply to codes created through the API exactly as they do to codes created in the dashboard.

By creating an API key or calling the API, you agree to the API Terms on behalf of the organization that owns the QRbolt account ("you"), and you confirm you are authorized to do so.

2. Access to the API

  • API access is available on the plans that include it, as shown on the pricing page, or where we grant it to an account in writing. We may change which plans include API access; if a change removes access from your current plan, we will give you at least 30 days notice.
  • An account administrator creates and revokes keys in Settings. Each key belongs to one organization, and to one department when it is a department key, and can only reach that organization's data.
  • The API acts within your plan: the same limits on codes, Digital Links, items and features apply whether you use the dashboard or the API.
  • You may build applications and integrations for your own organization, or for your clients where you manage their QRbolt accounts with their authorization. Each organization must use its own keys.

3. API keys

  • Keys are secrets. Keep them on servers you control. Do not put them in browser or mobile app code, public repositories, URLs, logs or support messages. We show a key once, when it is created, and store only a one-way hash.
  • Give each key only the scopes and department it needs, and use separate keys for separate systems so you can revoke one without stopping the others.
  • You are responsible for all requests made with your keys. If a key may have been exposed, revoke it in Settings at once and create a new one.
  • We may revoke or suspend a key we believe is compromised, is being misused, or puts the service or other customers at risk. Where we can, we will tell an account administrator first.

4. Acceptable use

You must not, and must not let anyone else:

  • try to get around rate limits, plan limits, scopes or department boundaries, for example by spreading traffic over several keys or accounts to exceed a limit;
  • access, or try to access, data of another organization, or probe the API for other customers' identifiers;
  • run load, stress, penetration or vulnerability tests against the API without our written permission (if you find a security problem, report it to us as described under Contact below);
  • send malware, or create codes or links that point to phishing, malicious, deceptive or unlawful content. Destinations are checked against threat intelligence, and we may block, disable or remove codes that are not safe for the people who scan them;
  • use GTINs, GS1 Company Prefixes or brand identifiers you are not authorized to use. You confirm that you hold the right to every GTIN and prefix you register, assign or encode through the API;
  • resell or sublicense the API itself, or offer it as a standalone API to third parties, without a separate written agreement;
  • copy, scrape or reverse engineer the service beyond what the documented API provides, or use it to build a competing service;
  • use the API in breach of applicable law, including privacy, consumer protection, advertising and product labelling law.

5. Rate limits and fair use

  • Requests are rate limited per key and per account, at levels set by your plan. Responses to requests made with a valid key carry the current limit in RateLimit headers; when a limit is reached the API answers 429 with a Retry-After header. Build your client to read these headers and slow down, rather than relying on fixed numbers: we may adjust limits to keep the service fair and available.
  • Request sizes and batch sizes are limited as described in the developer guide (for example, the request body size and the number of items per call or per job). Large batches belong in jobs.
  • If your usage harms the service for others, we may throttle it and will contact you to agree a fix, such as moving work to jobs or to a plan with higher limits.

6. Your content and data

  • You keep ownership of the content and data you send through the API, such as destinations, product data, GTINs, SKUs, serial numbers and metadata. You grant us the rights needed to store, process and serve it to provide the service, as in the Terms of Service.
  • You are responsible for that content: that you may use it, that it is accurate, and that the pages your codes lead to are lawful.
  • Do not send personal information through the API unless you need to for your use of the service, and you have a lawful basis to do so. Serial numbers, metadata and similar fields are not meant to hold personal information about consumers.
  • Results of background jobs (files and result lists) are available for 7 days after the job finishes (24 hours for barcode export files); after that they can no longer be downloaded. The job record stays. Download what you need within that time.
  • You may access and export your data through the API and the dashboard at any time while your account is active.

7. Request logs and the audit trail

  • We log every API request, including refused ones: time, request id, method, request path and matched route, status, response time, IP address, user agent, whether the key was accepted, the key's public prefix and id (never the secret), and the account. We use these logs to secure and operate the service, investigate abuse and support your requests.
  • Request log files are kept on the API servers for 90 days. Their copies in our backups are deleted after one year.
  • Changes made through the API are recorded in your account's audit trail as made by the key, with the request id, and are visible to your account administrators. IP addresses in the audit trail are removed after one year.
  • Personal information in these records is handled under our Privacy Policy.

8. Webhooks

  • You choose where webhooks are sent and are responsible for the endpoints you register, including keeping them secure and verifying the signature on every delivery as described in the developer guide.
  • Webhook endpoints must be on the public internet and use HTTPS. Deliveries are retried for a limited time; an endpoint that keeps failing may be disabled, and you can turn it back on in Settings.
  • Webhook payloads contain your account's data. Do not forward them to systems that should not see it.

9. Versions and changes to the API

  • The API is versioned in its URL (v1). Within a version we only add to the API: new endpoints, new optional fields, new enum values and new response fields. Your client must ignore fields and values it does not know.
  • Removing or changing existing behaviour needs a new version. When we deprecate an endpoint, we announce it in the changelog, mark its responses with Deprecation and Sunset headers, and keep it available for at least 6 months after the announcement.
  • We may change behaviour without notice where needed to fix a security problem, to comply with law, or to stop abuse. We will document the change in the changelog as soon as we can.

10. Availability and support

  • We work to keep the API available and fast, but unless you have a separate written agreement with a service level, the API is provided without a guaranteed uptime or response time.
  • We may carry out maintenance, which can briefly affect the API. We try to schedule planned work outside business hours in North America.
  • Support for the API is provided through the same channels as for your plan. Include the request id (X-Request-Id) of the calls you ask about.

11. Fees

API use is included in plans that include API access and is billed as part of your subscription through our reseller Paddle.com, under the payment terms in the Terms of Service. We do not charge per request. Codes, items and other resources you create through the API count toward your plan's limits like those created in the dashboard.

12. Suspension and termination

  • We may suspend or revoke keys, or suspend API access for an account, if you breach the API Terms or the Terms of Service, if a payment is overdue, or if your use puts the service, other customers or the people scanning codes at risk. Where we can, we will tell you first and give you a chance to fix the problem.
  • You can stop using the API at any time by revoking your keys.
  • If your plan no longer includes API access, or your account is closed, your keys stop working. Your data is then handled as described in the Terms of Service. Published codes keep resolving as long as your account and plan keep them active.

13. Disclaimers and liability

The API is provided "as is" and "as available", to the extent permitted by law. The disclaimers, limitation of liability and governing law (British Columbia, Canada) in the Terms of Service apply to the API. You will indemnify Incudo Labs Inc. against claims arising from your use of the API in breach of the API Terms or the law, including claims about content, destinations and identifiers you send through it.

14. Changes to these terms

We may update the API Terms. For material changes we will give account administrators at least 30 days notice by email or in the service, unless a change is required sooner by law or to address a security risk. The date at the top of this page shows when the API Terms last changed. Continuing to use the API after a change takes effect means you accept the updated API Terms.

15. Contact

Questions about the API Terms: Incudo Labs Inc., legal@qrbolt.com. To report a security problem with the API, write to the same address with "Security" in the subject, and do not test it further until we reply.