---
title: "List Bulk Sync Executions"
method: GET
path: "/api/bulk/syncs/{id}/executions"
tags: ["Bulk Sync"]
---

# List Bulk Sync Executions

`GET /api/bulk/syncs/{id}/executions`

Lists executions for a bulk sync.

Results are ordered by start time descending by default. When more results are
available, the response includes an opaque `pagination.next_page_token`; pass it
back as the `page_token` query parameter to retrieve the next page. The `limit`
parameter is optional, and the maximum page size is 100 executions.

Use `only_terminal=true` to return only finished executions. In that mode,
executions are ordered by `updated_at` so recently completed runs appear first.

Use `ascending=true` to walk forward from the oldest execution instead of
starting with the newest execution.

For the full details of a single run — including per-schema execution status —
use [`GET /api/bulk/syncs/{id}/executions/{exec_id}`](../../../../../api-reference/bulk-sync/executions/get).

## Path parameters

- `id` string, uuid, required — Unique identifier of the bulk sync.

## Query parameters

- `page_token` string — Pagination cursor returned in the previous response. Omit on the first request.
- `only_terminal` boolean — When true, only return executions that have finished. Terminal executions are ordered by updated_at.
- `ascending` boolean — When true, return executions from oldest to newest. Default is newest first.
- `limit` integer — Maximum number of executions to return. Capped at 100.

## Headers

- `X-Polytomic-Version` string

## Response `200`

OK

- ListBulkSyncExecutionsEnvelope
  - `data` BulkSyncExecution[], nullable
    - `completed_at` string, date-time, nullable
    - `created_at` string, date-time
    - `error_count` integer
    - `fetch_mode` 'none' | 'incremental' | 'full' — How the data is fetched. 'none' is normal operation for Polytomic. 'incremental' and 'full' apply to syncs from Salesforce. 'incremental' indicates the data is synced incrementally using record modification time. 'full' is necessary to catch up to the latest values for formula fields and rollup fields whose updates don't show up in incremental runs due to limitations in Salesforce.
    - `id` string, uuid
    - `is_partial` boolean
    - `is_resync` boolean
    - `is_test` boolean
    - `output_disposition` 'retain' | 'truncate' | 'rebuild'
    - `record_count` integer
    - `schemas` BulkSyncSchemaExecution[], nullable
      - `completed_at` string, date-time, nullable
      - `created_at` string, date-time
      - `error_count` integer
      - `output_name` string
      - `record_count` integer
      - `schema` string
      - `started_at` string, date-time, nullable
      - `status` 'created' | 'scheduled' | 'running' | 'exporting' | 'canceled' | 'completed' | 'failed' | 'interrupted' | 'processing'
      - `status_message` string
      - `updated_at` string, date-time
      - `warning_count` integer
    - `started_at` string, date-time, nullable
    - `status` 'created' | 'scheduled' | 'running' | 'exporting' | 'canceling' | 'canceled' | 'completed' | 'failed' | 'processing' | 'errors' | 'interrupted'
    - `status_message` string
    - `type` string
    - `updated_at` string, date-time
    - `warning_count` integer
  - `pagination` PaginationDetails
    - `next_page_token` string

## Other responses

- `404` — Not Found

---

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