--- title: Authentication API Support description: You can use the PingFederate authentication application programming interface (API) to integrate the Magic Link IdP Adapter into your application. component: pingone page_id: pingone:magic_link_integration_kit:pf_magic_link_ik_authentication_api_support canonical_url: https://docs.pingidentity.com/integrations/pingone/magic_link_integration_kit/pf_magic_link_ik_authentication_api_support.html revdate: June 10, 2024 --- # Authentication API Support You can use the PingFederate authentication application programming interface (API) *(tooltip: \
\

A specification of interactions available for building software to access an application or service.\

\
)* to integrate the Magic Link IdP Adapter into your application. The PingFederate Authentication API provides access to the current state of the authentication flow as a user steps through the PingFederate authentication policy. Learn more in [PingFederate authentication API](https://docs.pingidentity.com/pingfederate/latest/developers_reference_guide/pf_authentication_api.html) in the PingFederate documentation. To integrate the Magic Link IdP Adapter into your authentication flow, configure your application based on the information in this section. | | | | - | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | For this adapter, only the different device SSO flow supports the PingFederate Authentication API. For more information on the different device SSO flow, see [Overview of the SSO flow](pf_magic_link_ik_overview_of_the_sso_flow.html).The application using the authentication API polls for status and continues with the same flow ID and cookie once the link is approved. This is because the link verification endpoint requires a redirect back to the resume URL, and the application should control this behavior. | | | | | - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | You can also explore the process using the PingFederate Authentication API Explorer. Learn more in [Exploring the Authentication API](https://docs.pingidentity.com/pingfederate/latest/developers_reference_guide/pf_exploring_authentication_api.html) in the PingFederate documentation. |