# 60371: Relying party invalid or not provided

Log Type: APPLICATION

Log Level: ERROR

## Description

Twilio returns this error when your Verify Passkeys request does not include a valid relying party configuration. The relying party identifies the application requesting passkey registration or authentication, and the request must send that configuration in the expected format.

### Possible causes

* The request omits the relying party configuration.
* The `relying_party` object is malformed or does not follow the expected structure for `id`, `name`, and `origins`.
* The Passkeys relying party ID is not sent as your application domain without a scheme or port.
* The relying party origins are missing, incorrectly formatted, or do not match the server origins or App IDs your service accepts.

### Possible solutions

* Send the relying party configuration in the correct field for the endpoint you are calling. For a Passkeys factor request, provide it in `config.relying_party`. For a Verify Service request, provide the Passkeys relying party fields on the Service configuration.
* Set `id` to your application domain, such as `example.com`, and do not include a scheme or port.
* Set `name` to the app or website name you want authenticators to display during registration and authentication.
* Set `origins` to the exact HTTPS origins or App IDs that your Passkeys flow should accept, and make sure they match the domains where passkeys are created and verified.

#### Additional resources

* [Verify Passkeys quickstart](/docs/verify/quickstarts/passkeys)
* [Verify Service API reference](/docs/verify/api/service)
* [Passkeys Factor API reference](/docs/verify/api/passkeys-factor)