SMTP
Auth
Authenticate SMTP credentials (used by SMTP relay server)
POST
cURL
Authenticate SMTP credentials. This endpoint is called by the SMTP relay server to validate client credentials during authentication.
401 Unauthorized:
Usage
The SMTP relay server calls this endpoint during theAUTH phase to verify that the provided username and API key are valid. The username can be a custom team-specific SMTP username or the global default (bytesend).
Authentication
This endpoint does not require Bearer token authentication. Instead, it accepts the credentials directly in the request body.Request Body
-
username(string, required): The SMTP username. Can be:- A custom team SMTP username (configured in team settings)
- The global default:
bytesend - Or any username if using an API key for a team with remote auth enabled
-
password(string, required): The API key to verify. This is used as the password in SMTPAUTH PLAINorAUTH LOGINflows.
Response
200 Success:Examples
Notes
- This endpoint is fire-and-forget from the perspective of the SMTP relay. Failures are logged but do not block the SMTP handshake.
- The endpoint does not perform rate limiting separate from the standard API rate limits.
- For custom team SMTP usernames, ensure the API key belongs to that team.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
application/json
Response
Credentials are valid
Available options:
true