Native authentication API reference

Microsoft Entra's Native authentication enables you to host the user interface of your app in the client application instead of delegating authentication to browsers, resulting in a natively integrated authentication experience. As a developer, you have full control over the look and feel of the sign-in interface.

This API reference article describes details required only when you manually make raw HTTP requests to execute the flow. However, we don't recommend this approach. So, when possible, use a Microsoft-built and supported authentication SDK. For more information on how to use the SDK, see Tutorial: Prepare your Android mobile app for native authentication and Tutorial: Prepare your iOS mobile app for native authentication.

When a call to the API endpoints is successful, you receive both an ID token for user identification and an access token to call protected APIs. All responses from the API are in a JSON format.

Currently, our identity platform's Native authentication API supports sign-up and sign-in for two authentication methods:

• Email with password, which supports sign-up and sign-in with an email and password, and self-service password reset (SSPR).

• Email one-time password or passcode, which supports sign-up and sign-in with email one-time passcode.

Note

Currently, the native authentication API endpoints don't support Cross-Origin Resource Sharing (CORS).

Next steps

• Native authentication API reference with email one-time passcode.

• Native authentication API reference with Email and password.

• Native authentication API reference with Email and password - Self-service password reset option.