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

# 60375: Invalid id

Log Type: APPLICATION

Log Level: ERROR

## Description

This error occurs when you send an invalid `id` value in a Verify Passkeys request. For Passkeys registration and authentication, Verify expects `id` in the JSON payload for `VerifyFactor` and `ApproveChallenge`. That value must be the `base64url`-encoded representation of the credential `rawId` from the browser-generated `PublicKeyCredential`.

### Possible causes

* The `id` value is not encoded as the required `base64url` representation of the credential `rawId`.
* You modified the browser-generated `credential` object before sending it. In the Passkeys flow, create or fetch the credential in the browser, copy it, and pass that JSON object to the Verify endpoint for the current step.
* The request payload does not match the expected Passkeys credential shape, including `id`, `rawId`, `type`, and the required `response` fields for the registration or authentication step.

### Possible solutions

* Pass the `id` value from the browser-generated `credential` object exactly as returned. Do not reformat or regenerate it before sending the request.
* If you are registering a Passkey, send the copied browser `credential` object to `VerifyFactor` and include the required fields for that step, including `id`, `rawId`, `authenticatorAttachment`, `type`, `response.clientDataJSON`, and `response.attestationObject`.
* If you are approving a Passkey authentication challenge, send the copied browser `credential` object to `ApproveChallenge` and confirm that `id` and `rawId` come from the `PublicKeyCredential` returned by `navigator.credentials.get()`.
* Follow the Verify Passkeys quickstart flow so the credential is created in the browser, copied, and then posted to the correct Verify endpoint.

#### Additional resources

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