---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/60434#article
headline: "60434: Unsupported passkeys verification content type"
url: https://www.twilio.com/docs/api/errors/60434
inLanguage: en
dateModified: 2026-06-08T12:04:59.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 60434: Unsupported passkeys verification content type

Log Type: APPLICATION

Log Level: ERROR

## Description

This error occurs when you send a Verify Passkeys verification request with a credential `type` that Verify does not support. Verify Passkeys uses WebAuthn passkey registration and authentication flows, and the passkeys verification payload accepts `public-key` for the credential `type`.

### Possible causes

* The credential object sent to `VerifyFactor` used a `type` other than `public-key`.
* The verification request did not include the WebAuthn credential payload generated during passkey registration.
* The request payload came from a different Verify flow or a non-Passkeys implementation, so the verification content type was not valid for Passkeys.

### Possible solutions

* Send the credential returned by your browser passkey registration flow to `VerifyFactor` as a JSON object.
* Make sure the credential `type` is `public-key`.
* Include the required WebAuthn registration fields in `response`, including `clientDataJSON` and `attestationObject`.
* If you include `transports`, use only supported values.
* Follow the Verify Passkeys quickstart to create the factor, generate the browser credential, and verify the factor with the expected payload structure.

#### Additional resources

* [Verify Passkeys overview](/docs/verify/passkeys)
* [Verify Passkeys quickstart](/docs/verify/quickstarts/passkeys)
* [Passkeys Factor resource](/docs/verify/api/passkeys-factor)