To launch a template, we recommend using projects.locations.templates.launch with a regional endpoint. Using projects.templates.launch is not recommended, because jobs launched from the template will always start in us-central1.
HTTP request
POST https://dataflow.googleapis.com/v1b3/projects/{projectId}/locations/{location}/templates:launch
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-04-30 UTC."],[[["\u003cp\u003eThis webpage details how to launch a template using the \u003ccode\u003eprojects.locations.templates.launch\u003c/code\u003e method, recommending the use of regional endpoints for job execution.\u003c/p\u003e\n"],["\u003cp\u003eThe HTTP request uses a \u003ccode\u003ePOST\u003c/code\u003e method directed to a specific URL with path parameters for \u003ccode\u003eprojectId\u003c/code\u003e and \u003ccode\u003elocation\u003c/code\u003e, adhering to gRPC Transcoding syntax.\u003c/p\u003e\n"],["\u003cp\u003eQuery parameters include \u003ccode\u003evalidateOnly\u003c/code\u003e to validate without executing and a union parameter \u003ccode\u003etemplate\u003c/code\u003e that accepts either a \u003ccode\u003egcsPath\u003c/code\u003e or \u003ccode\u003edynamicTemplate\u003c/code\u003e for template specification.\u003c/p\u003e\n"],["\u003cp\u003eThe request body must contain a \u003ccode\u003eLaunchTemplateParameters\u003c/code\u003e instance, and a successful response will include a \u003ccode\u003eLaunchTemplateResponse\u003c/code\u003e instance.\u003c/p\u003e\n"],["\u003cp\u003eAuthorization for this action requires one of the specified OAuth scopes, either \u003ccode\u003ehttps://www.googleapis.com/auth/compute\u003c/code\u003e or \u003ccode\u003ehttps://www.googleapis.com/auth/cloud-platform\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,["# Method: projects.locations.templates.launch\n\n- [HTTP request](#body.HTTP_TEMPLATE)\n- [Path parameters](#body.PATH_PARAMETERS)\n- [Query parameters](#body.QUERY_PARAMETERS)\n- [Request body](#body.request_body)\n- [Response body](#body.response_body)\n- [Authorization scopes](#body.aspect)\n- [Try it!](#try-it)\n\nLaunches a template.\n\nTo launch a template, we recommend using `projects.locations.templates.launch` with a [regional endpoint](https://cloud.google.com/dataflow/docs/concepts/regional-endpoints). Using `projects.templates.launch` is not recommended, because jobs launched from the template will always start in `us-central1`.\n\n### HTTP request\n\n`POST https://dataflow.googleapis.com/v1b3/projects/{projectId}/locations/{location}/templates:launch`\n\nThe URL uses [gRPC Transcoding](https://google.aip.dev/127) syntax.\n\n### Path parameters\n\n### Query parameters\n\n### Request body\n\nThe request body contains an instance of [LaunchTemplateParameters](/dataflow/docs/reference/rest/v1b3/LaunchTemplateParameters).\n\n### Response body\n\nIf successful, the response body contains an instance of [LaunchTemplateResponse](/dataflow/docs/reference/rest/v1b3/LaunchTemplateResponse).\n\n### Authorization scopes\n\nRequires one of the following OAuth scopes:\n\n- `https://www.googleapis.com/auth/compute`\n- `\n https://www.googleapis.com/auth/cloud-platform`\n\nFor more information, see the [Authentication Overview](/docs/authentication#authorization-gcp)."]]
