---
title: Using /start with the API integration method
description: "When you use the API method to integrate DaVinci flow policies into your application, the /start request uses the endpoint from the orchestrate-api.pingone.com resource server: POST {{orchestratePath}}/v1/company/{{companyID}}/policy/{{davinciFlowPolicyID}}/start."
component: pingone-api
page_id: pingone-api:auth:pingone-davinci/davinci-runtime-apis/dvflows/initiating-flow-policies/using-start-with-the-api-integration-method
canonical_url: https://developer.pingidentity.com/pingone-api/auth/pingone-davinci/davinci-runtime-apis/dvflows/initiating-flow-policies/using-start-with-the-api-integration-method.html
---

# Using /start with the API integration method

When you use the API method to integrate DaVinci flow policies into your application, the `/start` request uses the endpoint from the `orchestrate-api.pingone.com` resource server: `POST {{orchestratePath}}/v1/company/{{companyID}}/policy/{{davinciFlowPolicyID}}/start`.

For API integration use cases, this method is used for headless flow execution in which no end user is involved. This workflow can pass in the application's API Key directly because it should be protected from public exposure.

For more information about the API application integration method, refer to [Launching a flow with an API call](https://docs.pingidentity.com/davinci/integrating_flows_into_applications/davinci_launching_a_flow_with_an_api_call.html) in the PingOne admin documentation.

For sample requests and responses that use the `POST {{orchestratePath}}/v1/company/{{companyID}}/policy/{{davinciFlowPolicyID}}/start` endpoint, refer to [Create Start Company Flow Policy](../create-start-company-flow-policy.html).

|   |                                                                                            |
| - | ------------------------------------------------------------------------------------------ |
|   | This endpoint is used for backend operations that do not require additional CORS settings. |