60372: Relying party id invalid or not provided

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.

• 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.

• 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.

• Verify Passkeys quickstart
• Verify Passkeys technical overview
• Verify Services API reference