---
title: "Trigger Sync From ID or Slug"
method: POST
path: "/syncs/trigger"
---

# Trigger Sync From ID or Slug

`POST /syncs/trigger`

Trigger a new run globally based on sync id or sync slug

If a run is already in progress, this queues a sync run that will get
executed immediately after the current run completes.

## Request body

- TriggerRunCustomInput — The input of a trigger action to run syncs based on sync ID, slug or other filters
  - `syncSlug` string — Trigger run based on sync slug
  - `syncId` string — Trigger run based on sync id
  - `clearAndFill` boolean — Whether to clear the audience and then sync the full query to the destination
  - `resetCDC` boolean — Whether to sync all the rows in the query without executing changes on the destination.
  - `fullResync` boolean — Whether to resync all the rows in the query (i.e. ignoring previously synced rows).

## Response `200`

Ok

- union
  - TriggerRunOutput — The output of a trigger action to run syncs
    - `id` string, required — The id of the triggered sync run. This can be passed to `/sync/runs` to get the run's status.
  - ValidateErrorJSON
    - `message` 'Validation failed', required
    - `details` object, required

## Other responses

- `400` — Bad request
- `401` — Unauthorized
- `422` — Validation Failed

---

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