Fork Workflow — POST /api/v1/projects/{project_id}/workflows/{workflow_id}/fork
Fork Workflow
Endpoint: POST /api/v1/projects/{project_id}/workflows/{workflow_id}/fork
Authentication: Send a signed-in user’s access token in Authorization: Bearer <access token>, or an API key in X-API-Key: <API key>.
- Your role in the project must be QA lead or higher. If you are not a member of the project, your account role counts instead.
- You must be a member of the project. Admins always have access.
Parameters
Section titled “Parameters”| Name | In | Required | Type | Default | Description |
|---|---|---|---|---|---|
project_id | path | yes | string (uuid) | ||
workflow_id | path | yes | string | ||
version | query | no | integer or null | ||
X-API-Key | header | no | string or null | API key, as an alternative to the access token (see Authentication). |
Request body
Section titled “Request body”| Content type | Body | Required |
|---|---|---|
application/json | WorkflowForkV1 | yes |
Responses
Section titled “Responses”| Status | Meaning | Body |
|---|---|---|
201 | Successful Response | object (application/json) |
422 | Validation Error | HTTPValidationError (application/json) |
It can also return 401 if your credential is missing or expired, 403 if your credential does not allow this request, and 404 if the item does not exist or you cannot see it. Your role, your project membership and the key’s scope decide what a credential allows. See Errors and retries.
More details
Section titled “More details”- Group: Workflows
- Operation ID:
fork_workflow_api_v1_projects__project_id__workflows__workflow_id__fork_post - Source code:
backend/app/routers/workflows.py, line 423 - Specification: OpenAPI JSON