> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.propexo.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.propexo.com/_mcp/server.

# Sync Complete Webhook

The **SYNC\_COMPLETE** webhook is sent when a full data sync for an integration has finished. This event does **not** include the first sync, which is reported separately by the **FIRST\_SYNC\_COMPLETE** webhook.

## When It Triggers

A SYNC\_COMPLETE webhook is triggered after a periodic or on-demand full sync job finishes running for an integration. It is sent once all associated jobs for that sync cycle have either succeeded or failed.

## Common Use Cases

* **Triggering post-sync processes** such as report generation, downstream updates, or data exports.
* **Generating sync completion logs** for monitoring integration performance and reliability.

## Example Payload

```json
{
 "event": "SYNC_COMPLETE",
 "failed_job_count": 0,
 "integration_id": "INTEGRATION_ID_003",
 "is_sync_finished": true,
 "job_schedule_id": "JOB_SCHEDULE_ID_001",
 "successful_job_count": 49,
 "vendor": "YARDI"
}
```

## Field Reference

* **failed\_job\_count** – Number of jobs that failed during the sync.
* **integration\_id** – Unique ID for the integration.
* **is\_sync\_finished** – Indicates whether the sync is fully complete.
* **job\_schedule\_id** – The ID of the scheduled job that ran the sync.
* **successful\_job\_count** – Number of jobs that completed successfully during the sync.
* **vendor** – The PMS vendor for the integration.