Guides
TurnKit Auth with Brevo
Use Brevo SMTP with TURNKIT_AUTH to let players sign in with email OTP. This is the fastest setup if you want TurnKit to handle auth for you.
Create Brevo Account
- Open Brevo registration and create your account.
Copy SMTP Credentials
- Open Brevo real-time SMTP.
- Copy the login and password shown there.
Configure TurnKit Auth
In your game dashboard, open Player Authentication Mode and switch it to TURNKIT_AUTH.
Client flow
- Fill the SMTP fields below and press SAVE.
- Client calls
/v1/client/auth/otp/requestand/v1/client/auth/otp/verify. - Use the returned player JWT in
Authorization: Bearer <player-jwt>for normal client calls.
| Field | Value |
|---|---|
| SMTP HOST | smtp-relay.brevo.com |
| PORT | 465 |
| USERNAME | Login from Brevo real-time SMTP page |
| PASSWORD | Password from Brevo real-time SMTP page |
| FROM | The email address you used to sign up with Brevo |
| NAME | Your game name |
TurnKit sends the OTP email through these SMTP credentials. After verification succeeds, the client uses the returned player JWT for authenticated client API calls.
Current API behavior: send OTP requests as JSON with
Content-Type: application/json. Default limits are 5 requests per 10 minutes for /v1/client/auth/otp/request and 10 requests per 10 minutes for /v1/client/auth/otp/verify.Sender Note
Note: If the email you used in Brevo is not verified for your website domain, the sender will still use your email name, but Brevo may send from an address ending in @random_number.brevosend.com.