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

# 60372: Relying party id invalid or not provided

Log Type: APPLICATION

Log Level: ERROR

## Description

This error appears when your Verify Passkeys request does not include a valid `Passkeys.RelyingParty.Id`. The Relying Party ID identifies your application during passkey registration and authentication, and Twilio expects it to be the application domain, expressed without a scheme or port.

### Possible causes

* Your request did not include `Passkeys.RelyingParty.Id`.
* You sent the Relying Party ID in an invalid format, such as including `https://` or a port instead of only the origin domain.
* The value in `Passkeys.RelyingParty.Id` is not the domain of your application.
* Your Passkeys configuration does not include the correct accepted origins for your application in `Passkeys.RelyingParty.Origins`.

### Possible solutions

* Include `Passkeys.RelyingParty.Id` when you create or update your Verify Passkeys service configuration.
* Set `Passkeys.RelyingParty.Id` to your application domain only, for example `example.com`. Do not include a scheme, path, or port.
* Review `Passkeys.RelyingParty.Origins` and make sure it lists the HTTPS origins or app IDs that your service should accept.
* When you test passkey registration or authentication in the browser, use the domain expected by `publicKey.rpid`.

#### Additional resources

* [Verify Passkeys quickstart](/docs/verify/quickstarts/passkeys)
* [Verify Passkeys technical overview](/docs/verify/passkeys/technical-overview)
* [Verify Services API reference](/docs/verify/api/service)