Skip to main content

Web setup

Capture IQ ships as a single script and a custom element (<glamar-captureiq>). A typical web integration loads the bundle from the CDN (or your own host), adds the element to the page, registers event listeners, then calls init() and start() in order.

The Capture IQ Setup guide covers the same flow in depth; this page highlights patterns that match the official static demo.

icon

Web demo project

Demo source: captureiq-web-demo.

Prerequisites​

Node.js 18 and above is recommended for npm and local tooling if you use the demo dev server.

  • A Capture IQ api-key (live_apitoken). See Getting started if you have not created one yet.
  • A browser with getUserMedia support and permission to use the camera.
  • Secure context for camera access: HTTPS or http://localhost (see MDN: Secure contexts). Do not open the HTML file as a file:// URL if you need the camera—the demo uses a dev server for this reason.

Load the bundle​

Point a <script> tag at your Capture IQ bundle URL. The reference demo uses the Z0 staging script:

https://cdn.glamarz0.de/sdk/captureiq

For production, use the URL and environment your team standardizes on.

Reliable session start​

Do not rely on the ready event alone to call start(). The demo and product guidance use this order:

  1. Attach event listeners to the element (ready, captureSuccess, error, etc.).
  2. await el.init() (or handle its promise).
  3. await el.start() after init completes.

That avoids racing registration, license checks, and the first session. See Host script timing in the demo repo’s docs/capture-iq/captureiq.md for more detail.