Reveal and copy a stored credential

Stored keys render masked with a per-field eye to reveal and a one-click copy, and the page says out loud who can see them.

What it is

A shared secret row used by every credential card: label, masked value, reveal toggle and copy button. The tab states plainly that credentials are returned so you can verify and copy them, and that anyone with admin access can see them.

Also called: show my api key · copy the token · what key did I save

See it
Reveal and copy a stored credential
Area
Integrations
Group
Connected services
System
Integrations
Solves
2 named problems
01The status endpoint returns both the full value and a masked version; the row shows masked by default.
02Reveal is per field, not per card.
03Copy writes to the clipboard and flashes a confirmation.
A SecretRow with the masked value, eye icon and copy tick confirmation. Sample data — no customer information appears here.
How it works
  1. 1The status endpoint returns both the full value and a masked version; the row shows masked by default.
  2. 2Reveal is per field, not per card.
  3. 3Copy writes to the clipboard and flashes a confirmation.
Why we built it

Write-only credential fields sound safer but force a builder to re-mint a token every time they need to check what they saved. Returning the value with an explicit statement of who can see it is the honest trade, and it is exactly the trade that motivated the optional PIN lock on the same tab.

The problem
  • Verifying a stored credential meant re-issuing it.
  • The exposure of stored keys was implicit.
Sound familiar?
What you get
A credential can be checked or reused without touching the third-party dashboard.
The exposure is stated, which is what the PIN lock then addresses.

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →