> 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.

# First Sync Complete Webhook

The FIRST\_SYNC\_COMPLETE webhook is sent when the initial data sync for an integration has finished. This event ensures your system has received an initial dataset from each group of models that are scheduled to be synced. Note that this may represent a subset of available data based on the configured sync schedule rather than a complete baseline of all possible data.

## When It Triggers

You’ll receive one FIRST\_SYNC\_COMPLETE webhook for each sync schedule in your integration.

Default Configuration:\
Most customers use a single sync schedule, which syncs all enabled data models on a set timing interval. In this case, you’ll receive a single webhook when the initial sync completes.

Multiple Sync Schedules:\
In less-common cases, you could have multiple sync schedules configured. In that case, you’ll receive a separate webhook as each schedule completes its initial sync.

For example, with custom schedules like:

* `Applicants` syncing every 15 minutes
* `Units` and `Listings` syncing weekly

You’ll receive two webhooks - one when each schedule finishes its first sync.

## Common Use Cases

* Kicking off first-time data processing flows, such as analytics, migrations, or initial reporting.

## Example Payload

```json
{
  "event": "FIRST_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"
}
```