---
title: "Send a custom event for a specific flow"
method: POST
path: "/syncs/{syncid}/flows/{flowid}/event"
tags: ["Syncs"]
---

# Send a custom event for a specific flow

`POST /syncs/{syncid}/flows/{flowid}/event`

Route that can be used to send a specific event for a flow

## Path parameters

- `syncid` string, required
- `flowid` string, required

## Request body

- PostSyncFlowEvent
  - `consumers` union[]
    - union
      - string, uuid
      - string
  - `data` PostSyncFlowEventData
    - `is_preview` boolean — Whether to preview the sync
    - `force_restart` boolean — Whether to force restart the sync from the specified dates
    - `start_date` string, date, nullable — Start date for sync range
    - `end_date` string, date, nullable — End date for sync range
    - `force_from_date` string, date, nullable — Force sync from this specific date, overriding flow configuration
    - `import_mode` 'IMPORT_ONLY_MISSING_DAYS' | 'REIMPORT_ENTIRE_PERIOD' — Enumeration of import modes for flow execution.

## Response `200`

Successful Response

- TriggerResponse
  - `status` string, required
  - `message` string, required
  - `data` object, nullable

## Other responses

- `400` — Bad Request
- `404` — Not Found
- `422` — Unprocessable Entity

---

[API](https://skmtc.net/chift/apis/chift-api.md) · [All operations](https://skmtc.net/chift/apis/chift-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/chift/chift-api/revisions/b5f1214a482a/schema)