---
title: "Whether a connected user can be asked for a passkey touch"
method: GET
path: "/v1/platform/connections/{connectionId}/passkeys"
tags: ["Platform"]
---

# Whether a connected user can be asked for a passkey touch

`GET /v1/platform/connections/{connectionId}/passkeys`

## Request

- Base URL: `https://api.1claw.co`
- URL: `https://api.1claw.co/v1/platform/connections/{connectionId}/passkeys`
- Auth: HTTP bearer

Answers one question: can this app offer the passkey confirm
step to this user? No credential material is returned — not
credential ids, not public keys, not enrolment times.

`count` is what matters. Passkeys are bound to the domain they
were registered on, so an account can hold credentials that this
domain cannot offer; `count` reports only those usable on
`rp_id`, while `registered_count` is the raw total. Branch on
`has_passkey`.

## Path parameters

- `connectionId` string, uuid, required

## Response `200`

Passkey availability for this connection

- object
  - `has_passkey` boolean, required: True when count > 0.
  - `count` integer, required: Passkeys usable on rp_id.
  - `registered_count` integer, required: All passkeys on the account, including any bound to a different domain.
  - `rp_id` string, required: The domain these counts are measured against.

## Other responses

- `403`: Insufficient permissions
- `404`: Resource not found

---

[API](https://skmtc.dev/1claw/apis/1claw-api.md) · [All operations](https://skmtc.dev/1claw/apis/1claw-api/llms.txt) · [OpenAPI document](https://skmtc.dev/1claw/apis/1claw-api/revisions/5fa0918f3b41?raw)