60368: Challenge details invalid or not provided

Twilio returns this error when a Verify Challenge request does not include valid details, or when the details payload does not match the expected structure for the Challenge being created. For push challenges, details.message is required and details.fields must follow the documented format and limits.

• The request creates a push Challenge without details.message, which is required when factor_type is push.
• The details.fields payload is not sent as a list of objects with label and value pairs.
• One or more details.fields entries exceed the supported limits. Each label can be up to 36 characters, each value can be up to 128 characters, and you can send up to 20 fields.
• The details.message value exceeds the supported maximum of 256 characters.
• The request sends context in hiddenDetails but omits the user-facing details values needed for the Challenge. hiddenDetails is separate from the Challenge details shown to the end user.

• If you are creating a push Challenge, include details.message in the request body. Use it for the message shown when the push notification arrives.
• If you send details.fields, structure each item as a field object with label and value. Match the Create a Challenge request format shown in the API reference.
• Keep all Challenge detail values within the documented limits. Limit details.message to 256 characters, each field label to 36 characters, each field value to 128 characters, and the total number of fields to 20.
• Send hiddenDetails only for context that should not be shown to the user. Put user-facing challenge content in details.
• Compare your request against the Verify Challenge creation examples and update your request body so the parameter names and payload shape match the documented API.

• Challenge Resource
• Verify Push & Silent Device Approval Overview
• Verify Push Client Library Technical Overview