Introduced v4 Authentication Mechanism
- Generates an access token and refresh token using a user’s username and password for authentication.
- Tokens are intended for use with other v4 endpoints via the Authorization: Bearer <access_token> header.

Behavior

Authentication is now handled through the v4-specific login endpoint, consistent with other v4 resources.
Error responses for invalid credentials and related issues follow the standard v4 error format and HTTP status codes.

Notes for integrators

Existing integrations using v3 authentication flows can use the same access token, nothing would get affected.
Existing integrations using v1 and v2 APIs have to mandatorily use v4 Authentication Mechanism for obtaining tokens.
New integrations targeting v4 can use this endpoint as the primary mechanism for obtaining tokens.