<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z0000AKAeFrCQLOkta Identity EngineAdministrationAnswered2026-01-18T09:00:48.000Z2025-03-12T10:23:58.000Z2025-03-12T15:37:55.000Z

yc954 (yc954) asked a question.

Clarification on OKTA Login APIs

We are integrating OKTA authentication into our platform and need clarification on the following points

Primary Authentication:

Our platform will call the /api/v1/authn API for primary authentication in OKTA, and the API returns a session token in the response.

Authorization and Token Flow:

 Our platform plans to call the /v1/authorize API to fetch an authorization token by passing a session token.

After obtaining an authentication token, our platform will call the /v1/token endpoint to fetch an access token.

Are these steps aligned with OKTA’s best practices? Any insights or recommended optimizations would be greatly appreciated.


This question is closed.
Loading
Clarification on OKTA Login APIs