WebAuthn Signal API
Lets a site tell the passkey manager a credential is gone or its name changed.
In one line
Can tell your passkey manager that a passkey is gone or renamed
Lets a site tell the passkey manager a credential is gone or its name changed.
Keeps the passkey list clean. Shows no data back to the site.
What it can and can't do
What the user does: Nothing extra. It happens after you delete an account or change your username
It can
- Send a note that a passkey no longer works so the manager can hide it
- Send a new username or display name so your passkey list stays tidy
It cannot
- See what passkeys your manager holds; it sends nothing back
- Delete a passkey on its own; the manager decides
- Work in Firefox, or in Safari before version 26
How it differs between platforms: Chrome and Edge support it from version 132 and Safari from version 26; Firefox does not yet.
Browser support
| Browser | Status | First version | Note |
|---|---|---|---|
| Chrome | Supported | 132 | None |
| Edge | Supported | 132 | None |
| Firefox | Not supported | Not available | not shipped |
| Safari | Supported | 26 | None |
| Safari on iPhone | Supported | 26 | None |
| Chrome on Android | Supported | 132 | verify on Android |
| Samsung Internet | Not supported | Not available | not confirmed |
How a site asks for it
| API | PublicKeyCredential.signalUnknownCredential(), signalAllAcceptedCredentials(), signalCurrentUserDetails() |
| Browser compat keys | api.PublicKeyCredential.signalUnknownCredential |
| How access is granted | none |
| What the user sees | None |
| Needs a secure context (HTTPS) | Yes |
| Needs a user gesture | No |
| How long it lasts | Per origin |
| How to take it back | Site settings |
| Inside an iframe | Same as top level; cross-origin iframes need a permissions policy where listed |
Typical flow
- Call the API
- Browser applies its access rules
- Page receives the result
Data you get
What comes back: Lets a site tell the passkey manager a credential is gone or its name changed.
Shape: object
How often: on demand
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
rpId, credentialId | string | None | base64url | Not listed |
name, displayName | string | None | user visible | Not listed |
Technical limits
- Provider may ignore
- No Firefox
The story
What it is
Lets a site tell your passkey manager that a passkey was removed or renamed.
For you
You never see a prompt. When you delete a passkey on a site, your phone or password manager quietly removes it from its list too. The list stays tidy.
For makers
Makers keep users from seeing stale or broken passkeys that cause failed sign ins. Fewer failures mean fewer help requests and cleaner security records.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A game account page removes a deleted passkey from the player's list, so they are not offered a broken one at login. | Roblox |
| banking | A bank cleans up passkeys after a customer closes an account or changes their username. | None named |
| shopping | A shop updates the name of a passkey when a person changes their email, so the list still makes sense. | None named |
| productivity | A work app tells the manager to remove passkeys for a former employee's departed device. | None named |
| security | A security team uses it to remove old keys after a suspected break in. | None named |
Risks
- Little, mostly housekeeping
What the platform says
- Google Chrome: Passkeys Signal API. Chrome describes it as a way to keep passkey lists up to date when an account or name changes.
Good uses and abuse
Legitimate uses
- Remove deleted accounts' passkeys
Known abuse
- None
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2024-11, Chrome 132: Signal API ships
- 2025-09, Safari 26: Safari support
Sources
How well checked: Checked against real behavior.