Data Connector V1 Changelog
Release Date: 2026-05-01
Version 1.2.0
Added
You can now:
- Use delta extraction (Change Data Capture) service groups to extract only records
that have changed within a specified time window, instead of full datasets on each
run. Delta extraction requires
startDateandendDateto define the extraction window. See the Field Guide for details. - Use the new
CUSTOMvalue for thedateRangeattribute to define a custom date range usingstartDateandendDate.
See POST requests for more details about these updates.
Release Date: 2025-01-21
Version 1.1.1
Added
You can now:
- Extract data for a list of selected projects (
projectIdList) - Extract data for only active projects in the hub (
projectStatus) - Specify a timeframe for data extraction using the new
dateRangeattribute, with options such asTODAY,YESTERDAY,PAST_7_DAYS,MONTH_TO_DATE, andLAST_MONTH. Note that the dateRange attribute currently applies only to the Activities service. See the Field Guide for details about Request Scheduling and Data Timeframes.
See POST requests for more details about these updates.
Release Date: 2023-05-17
Version 1.1.0
Added
You can now:
- Extract Activities service data (
serviceGroups) - Specify date ranges (
startDate,endDate) for schemas that support date range extraction
See POST requests and PATCH requests/:requestId for more details.
You can now:
- Sort parameters in the response (
sortFields) - Filter your request according to specified values or dates (
filter[])
See GET requests and GET jobs for more details.
You can now check who last downoaded each returned extraction job, and the date and time it was extracted.
See GET requests/:requestId/jobs, GET jobs, and GET jobs/:jobId endpoints now return lastDownloadedBy and lastDownloadedAt for more details.
Release Date: 2022-06-06
Version 1.0.1
Added
Added a new endpoint, GET jobs, which returns all of the data extraction jobs for all of the requests in a specified account or project. Use this endpoint’s projectId parameter to specify the project.
Other Data Connector endpoints now include a projectId field in their request or response payload to support project-level data extraction:
- POST requests uses
projectIdin its request payload to create a project-level data extraction request. - POST requests, GET requests, PATCH requests/:requestId, and GET requests/:requestId/jobs include
projectIdin their response payloads to identify the project of each returned request or job.