18 November, 2026

Secrets stay inside flespi

Token keys and credentials in item configurations become write-only: what changes, when, and what to check in your integration.

We designed flespi and its API for people and for the automated systems they build. Giving back everything you stored, credentials included, was simply convenient: open a stream and you see the password it uses, list your tokens, and you can copy any key.

In 2026, the readers of these responses changed. More and more of our users work with flespi through AI coding agents and assistants, and every REST API response such an agent fetches lands in the model context, in the chat history, and in the logs of a third-party tool. A token key or a stream password returned there is a copy nobody controls anymore. We treat it as a security hole and choose safety over convenience: credentials you give flespi stay inside flespi.

What changes

Credentials become write-only. You enter them once, flespi stores them deep inside the platform and uses them, but never gives them back to anybody, you included:

  • flespi token keys. The full key comes only once, in the response to the request that creates the token, and in the panel dialog right after creation. Copy and store it then.
  • Credentials in item configurations. Passwords, API keys, access tokens, private keys, and header values in channels, streams, plugins, modems, and AI agent connectors.

REST API responses, MQTT state and log topics, logs, webhooks and the flespi.io panel show such a secret in its redacted form: the first few characters followed by (redacted).

GET /platform/tokens/all?fields=id,key
{"result":[{"id":12345,"key":"AbCd(redacted)"}]}

GET /gw/streams/678?fields=configuration
{"result":[{"configuration":{"uri":"broker.example.com:8883","username":"flespi","password":"(redacted)"}}]}

PUT /gw/streams/678
{"configuration":{"uri":"broker.example.com:8883","username":"flespi","password":"(redacted)"}}
(the stored password stays unchanged)

Everything else works as before. An item read, changed, and written back as a whole keeps its credentials: the redacted value tells flespi to keep the stored secret. To change a secret, send its new value. The Login button on a token card in the panel keeps working too.

Our flespi AI agents already work this way: they never see secrets and manage your items with the stored credentials in place.

Timeline

Our SLA promises at least one month of notice for REST API changes. We give two months.

  • November 18, 2026: flespi AI agents and the flespi AI assistant see secrets only in their redacted form.
  • November 24, 2026: the flespi.io panel shows secrets redacted.
  • December 8, 2026: secrets are hidden by default in REST API responses, MQTT topics, logs and webhooks. From this date, logs store only the redacted values.
  • January 19, 2027: secrets are always hidden.

What to check on your side

Most integrations never read credentials back and need no changes. Yours needs attention if it:

  • reads token keys with GET /platform/tokens, e.g. to build TrackIt, Toolbox or flespi panel login links, instead of storing them at creation.
  • copies items with their configurations, e.g. clones a stream into a subaccount. A redacted value cannot create a new item, the request fails with "redacted secret does not match the stored one", so take the real credentials from your own storage.
  • selects items by a stored credential: selectors on secret fields match the redacted value.
  • shows or compares item configurations and expects real credentials in them.

Manage the transition at your pace

Until January 19, 2027 your integration can choose for itself, whatever the platform default is:

  • show keeps the full values. Add it now, and the December 8 switch passes your integration by.
  • hide gives the redacted values. Use it to test your integration now, and switch to it once your changes are ready.

REST API. Add the x-flespi-secrets header to your requests:

curl -H 'Authorization: FlespiToken XXX' -H 'x-flespi-secrets: hide' 'https://flespi.io/gw/streams/all?fields=id,configuration'

MQTT. Add the x-flespi-secrets user property to the CONNECT packet of your MQTT 5.0 session. It applies to the flespi/state and flespi/log topics the session receives. MQTT 3.x clients cannot send user properties and follow the platform default.

From January 19, 2027 secrets are always hidden, and the header and the property no longer change anything.

Important! Keys of existing tokens can still be read through the REST API until January 19, with the x-flespi-secrets: show header after December 8. Save the ones you need: after January 19 a lost key means a new token.

The details live in the Secret fields section of the flespi API basics article. If something in your integration is unclear, ask us in HelpBox with the SUPPORT button in the top-right corner of the flespi.io panel.