---
title: "Start a new schedule from an existing workflow"
method: POST
path: "/api/my/schedules/start"
---

# Start a new schedule from an existing workflow

`POST /api/my/schedules/start`

Start a new schedule from an existing workflow

## Headers

- `Authorization` string — Bearer token for authentication.
- `Credimi-Api-Key` string — User API key or internal admin API key, depending on the endpoint.

## Request body

- HandlersStartScheduleRequest
  - `global_runner_id` string
  - `pipeline_id` string
  - `schedule_mode` WorkflowengineScheduleMode
    - `day` integer, nullable
    - `mode` string

## Response `200`

Successful response

- HandlersStartScheduleResponse
  - `message` string
  - `schedule_id` string
  - `schedule_mode` WorkflowengineScheduleMode
    - `day` integer, nullable
    - `mode` string

## Other responses

- `default` — An unexpected error occurred.

## Changes

> 34 revisions in range; 2 could not be searched.

- **2026-05-15** `3480fda55a73` — 2 info
  - added the new optional `header` request parameter `Credimi-Api-Key`
  - the `header` request parameter `Authorization` became optional
- **2026-02-17** `39b2cda1a16e` — 1 info
  - endpoint added
- **2024-10-17** `53644f0719aa` — 1 breaking
  - api path removed without deprecation

[Change history](https://skmtc.dev/forkbombeu/apis/credimi-api/changes/api/my/schedules/start/post.md)

---

[API](https://skmtc.dev/forkbombeu/apis/credimi-api.md) · [All operations](https://skmtc.dev/forkbombeu/apis/credimi-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/forkbombeu/credimi-api/revisions/eaad04e53622/schema)