68002: Mapper Error

This error occurs when Verify cannot map the entity data in your request. In Verify, an Entity represents the user or other identity being verified, and each Entity can contain one or more Factors.

• The request includes entity data in an unexpected format. For Verify Entity resources, identity must be immutable, 8 to 64 characters long, and contain only dash-separated alphanumeric characters.
• The request uses an Entity and Factor that do not belong to the same Verify resource path. Verify Factor and Challenge endpoints are scoped under /Services/{ServiceSid}/Entities/{Identity}/... and expect the correct identity for the factor you are using.
• You are trying to continue with a factor that should be recreated. Verify deletes unverified factors after 1 to 24 hours, which can leave the existing enrollment unusable for later steps.

• Create a new factor for the user and continue with the new Factor SID. If the Entity does not already exist, creating the factor creates the Entity automatically.
• Check the identity value in your request path and use the same stable user identifier across your Entity, Factor, and Challenge requests. Make sure the value matches Verify's formatting requirements.
• If you are creating a Push factor, send a complete and valid factor payload, including the required binding and device configuration values.
• If you are using TOTP and the existing enrollment is no longer valid, register the user again by creating a new TOTP factor and completing verification with the new factor.

• Verify overview
• Entity Resource API
• Factor Resource API