---
title: DaVinci Direct Flow Executions
description: DaVinci flows use the /start endpoint to initiate a non-PingOne flow that will return HTML in the response. You can integrate a non-PingOne flow in the following ways:
component: pingone-api
page_id: pingone-api:auth:davinci-flow-executions/davinci-direct-flow-executions
canonical_url: https://developer.pingidentity.com/pingone-api/auth/davinci-flow-executions/davinci-direct-flow-executions.html
llms_txt: https://developer.pingidentity.com/pingone-api/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
page_aliases: ["auth:pingone-davinci/davinci-runtime-apis/dvflows.adoc"]
---

# DaVinci Direct Flow Executions

DaVinci flows use the `/start` endpoint to initiate a non-PingOne flow that will return HTML in the response. You can integrate a non-PingOne flow in the following ways:

* A redirect through PingOne. This method uses a call to a PingOne application to launch a flow with a redirect.

* A redirect through PingOne using DaVinci as an external identity provider (IdP). This method uses a call to a PingOne application to launch a flow with a redirect using an external IdP configuration.

* The widget. This method launches a flow inside of a widget on the current page.

* An API call. This method launches a flow using an API call.

For more information, refer to [Integrating Flows into Applications](https://docs.pingidentity.com/davinci/integrating_flows_into_applications/davinci_how_to_implement_a_flow.html) in the *PingOne DaVinci* guide.