---
title: "Trigger a Procountor sync"
method: POST
path: "/procountor-connections/{connection_id}/sync"
tags: ["Connections"]
---

# Trigger a Procountor sync

`POST /procountor-connections/{connection_id}/sync`

Pulls data from the Procountor connection, optionally constrained to a date window or a full backfill. Requires a write-scoped key.

## Path parameters

- `connection_id` string, required

## Request body

- ConnectionSyncInput — Options for a provider sync.
  - `customer_id` string — Target company. Optional for API keys.
  - `date_from` string — Start of the sync window, `YYYY-MM-DD`.
  - `date_to` string — End of the sync window, `YYYY-MM-DD`.
  - `backfill` boolean — Pull the full available history.

## Response `200`

Sync result.

- ConnectionSyncResult — Result of a provider sync run.
  - `customer_id` string
  - `result` object

## Other responses

- `401` — Missing or invalid bearer token.
- `403` — Insufficient scope or role — e.g. a read-scoped key on a mutating method, or an API key on an admin/approver-only endpoint.

---

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