{
"id": "evt_01GV12VR4DJP70GD1ZBK0SDWFH",
"type": "sync.completed",
"timestamp": "2021-01-06T03:24:53.000Z",
"detail": {
"connection": {
"id": "conn_01GV12VR4DJP70GD1ZBK0SDWFH",
"provider": {
"code": "geotab",
"name": "Geotab"
},
"externalId": "123456789",
"tags": [
"<string>"
]
},
"sync": {
"id": "sync_01GV12VR4DJP70GD1ZBK0SDWFH",
"status": "completed",
"requestedAt": "2021-01-06T03:24:53.000Z",
"failureReason": "Reason for failure if sync status is 'failed'",
"issues": [
"isu_01D8ZQFGHVJ858NBF2Q7DV9MNC"
],
"startFrom": "2021-01-06T03:24:53.000Z",
"completedAt": "2021-01-06T03:24:53.000Z",
"attempts": 1
}
}
}Emitted when a connection sync completes successfully.
"evt_01GV12VR4DJP70GD1ZBK0SDWFH"
sync.completed Show child attributes
Basic connection details to be able to reference connections from webhook events
Show child attributes
"conn_01GV12VR4DJP70GD1ZBK0SDWFH"
Show child attributes
Every provider has a unique code to identify it across Terminal's system. You can find each provider's code under provider details.
"geotab"
"Geotab"
"123456789"
Show child attributes
"sync_01GV12VR4DJP70GD1ZBK0SDWFH"
The status of the sync
requested, in_progress, completed, failed "completed"
If the sync failed, this will contain the reason
"Reason for failure if sync status is 'failed'"
Issues are problems encountered with a connection that did not result in a failed sync but may require manual intervention. You can see the issues for a given sync by providing issues to the expand parameter.
Entities in Terminal are expandable. Using the expand query parameter you can choose to ingest just an ID or the full entity details.
"isu_01D8ZQFGHVJ858NBF2Q7DV9MNC"
The earliest records to sync for those based on time (ex: historical locations and stats)
"2021-01-06T03:24:53.000Z"
1