Platform Auth API Reference

To implement OTP verification for user signup, you need to call the specific platform-auth endpoints under `/api/v1/auth` using fetch integration. This requires providing the correct authentication headers, request body schemas, and mapping documented error codes to handling logic for deterministic failure responses.

Platform-auth API endpoints require specific authentication modes depending on the operation: none, user JWT, or a bearer service role key. You must include the correct authentication headers matching the expected mode to successfully execute your fetch calls.

Custom access token enrichment allows you to append additional claims to the user session token during the profile bootstrap phase. You achieve this by calling the dedicated enrichment endpoint with a valid user JWT and the required request payload schema.

The best way to handle platform authentication error codes is to map the structured error-code table to specific handling logic in your consumer application. This approach ensures deterministic failure responses when operations like login, signup, or password reset fail.

Yes, you can reset a user password and resend OTP without an existing user session by calling the respective endpoints with no authentication mode required. You must provide the correct request body schema to trigger the password reset or OTP resend successfully.

Your fetch integration fails when calling the profile bootstrap endpoint if you provide incorrect endpoint paths, invalid authentication headers, or mismatched request body schemas. You must ensure valid user JWT credentials and verify the service health check passes before retrying.