422 Errors on Signup with Supabase Authentication

[Mergim1992]

Describe the problem
Signup requests consistently return 422 errors due to missing or invalid fields. The documentation does not clearly specify which fields are required for successful signup (e.g., email, password). This is confusing for new users, as it's unclear what data the signup endpoint expects.

Describe the improvement
Add clearer documentation on the required fields for signup, ideally with example payloads showing the correct format (e.g., email, password). This would help users avoid 422 errors during setup.

Additional context
Adding this information would improve the onboarding experience by preventing errors related to missing or incorrect signup data.

Error-Codes:

• Web-Inspector: Failed to load resource: the server responded with a status of 422 ()
• No-Errors in Console