Ingest tokens for automated readings

An ingest token is a credential a device — or a small script running on a gateway — sends with each reading to prove it's allowed to push data into your workspace. Use ingest tokens when you're wiring up your own device or a homebrew gateway, rather than pasting a per-device cloud URL (that flow is on the sensor's own page — see Connect a sensor and log readings).

Prerequisite: managing ingest tokens needs the manage sensors permission. If you don't have it, the screen explains that and no tokens are shown — ask a workspace admin.

Open the ingest tokens screen

1. In the navigation, choose Sensors.
2. On the Sensors list, choose Ingest device tokens (top right).

The screen lists your device tokens and lets you mint new ones. Every ingest token's id begins with sit_.

Mint a token

1. On the Ingest device tokens screen, optionally enter a Label to recognise the token later — for example Fermentation room gateway.
2. Choose Mint token.
3. The full token appears in a highlighted card headed Copy this token now — you won't see it again. Choose Copy token to copy it, then store it somewhere safe.
4. When you've saved it, choose Dismiss.

The full token is shown only once, at creation. Brewstiller keeps only a one-way hash of it, so it can never be shown again. If you lose it, revoke that token and mint a new one.

Once you have the token, configure your device or gateway to send it as its bearer credential with each reading.

Revoke a token

Revoke a token when a device is retired or a token may have leaked.

1. On the Ingest device tokens screen, find the token in Your tokens — each row shows its sit_… prefix, its label, and when it was created and last used.
2. Choose Revoke on that row.
3. In the dialog, choose Revoke token to confirm.

The token stops working immediately and can't be restored. Any device still sending it will be rejected, so mint a new token and update the device. Revoked tokens stay listed with a Revoked badge so you can see a token's full history.