Skip to main content

QR Codes

A QR code here is a dynamic short link: the printed code encodes an Autessa URL, not your destination, so you can repoint it later without reprinting anything. Every command in the namespace is runnable — this is one of the few surfaces with no web-app-only step at all.

Key concepts​

Dynamic, so the destination is editable​

The code's public slug is assigned automatically — you never set it — and stays fixed for the life of the code. update changes where it points. A poster printed in January can send scanners somewhere new in June.

Private by default​

A new code is visible only to its creator. Sharing is two independent things: a baseline visibility level, and per-member grants.

How to create one​

autessa qr-codes create \
  --name "Conference booth poster" \
  --destinationUrl "https://example.com/signup" \
  --active true

name is for your own reference in the list, not shown to scanners. The response carries the assigned slug and the public scan URL.

Two optional objects shape the rest:

autessa qr-codes create \
  --name "Spring campaign" \
  --destinationUrl "https://example.com/spring" \
  --design '{...}' \
  --utm '{...}'
  • design — colors, logo and style for the rendered code.
  • utm — campaign parameters appended to the destination URL on redirect, so scans show up attributed in your analytics.

Run autessa qr-codes create help for the exact QrDesignDto and QrUtmDto fields.

How to manage one​

autessa qr-codes list
autessa qr-codes get --json '{...}'
autessa qr-codes update --json '{...}'
autessa qr-codes delete --json '{...}'

get returns the destination, design, UTM tags, slug and public scan URL. update changes the name, destination, active state, design or UTM tags.

Setting active to false stops the code redirecting — scanners hit a dead end rather than your old destination. That is the safe way to retire a printed code, and it is reversible. delete is not.

How to share​

Two independent controls:

# baseline visibility
autessa qr-codes set-share-level --json '{...}'   # PRIVATE or COMPANY

# per-member grants
autessa qr-codes share --json '{...}'
autessa qr-codes shares --json '{...}'
autessa qr-codes unshare --json '{...}'

PRIVATE means the owner plus explicitly shared members; COMPANY means everyone in the company can see it. shares lists who currently has a grant and at what access level.

How to read scan analytics​

autessa qr-codes stats --json '{...}'

Returns totals plus breakdowns of who scanned, when, and from where. Pair this with distinct codes per placement — one per poster location, say — and the comparison tells you which placement is actually working.

Full command reference​

10 commands10 runnable
CommandWhat it does
autessa qr-codes createBuild a new QR code pointing at a destination URL.
autessa qr-codes deletePermanently delete a QR code.
autessa qr-codes getFetch one QR code by id, including its destination, design, UTM tags, slug, and public scan URL.
autessa qr-codes listList every QR code you can access in the current company — those you own plus those shared with you.
autessa qr-codes set-share-levelSet a QR code's baseline visibility — PRIVATE (only the owner and explicitly shared members) or COMPANY (everyone in the company can see it).
autessa qr-codes shareShare a QR code with a specific company member at a given access level.
autessa qr-codes sharesList the members a QR code is shared with and their access levels.
autessa qr-codes statsGet scan analytics for a QR code — totals and breakdowns of who scanned it, when, and from where.
autessa qr-codes unshareRevoke a specific member's access to a QR code.
autessa qr-codes updateUpdate a QR code's name, destination, active state, design, or UTM tags.