# Release Notes --- ## November 2026 The `connector_sdk_package_id` field is no longer returned by the [Retrieve Connection Details](/docs/developer-resources/rest-api/api-reference/connections/connection-details.md) endpoint. Use `config.package_id` instead. It contains the same package ID, and it is also the field you use to set the package when you create or update a Connector SDK connection. We added a new REST API endpoint, [Retrieve Connection Errors](/docs/developer-resources/rest-api/api-reference/connections/connection-errors.md) (`GET /v1/connections/{connectionId}/errors`), that returns all active errors for a connection. Each error corresponds to a task type currently active for the connection and includes a machine-readable `type`, a human-readable `title`, a short `reason` summary, a plain-text `message` with remediation guidance, and the `created_at` timestamp of the most recent occurrence. The response is paginated with the `cursor` and `limit` query parameters. If no errors are currently active, the endpoint returns an empty `items` array. We have added a new field, **TikTok API rate limit tier**, to the connection setup form. The field lets you match the connector's request rate to the rate limit tier TikTok has approved for your developer app (Basic, Advanced, Premium, or Ultimate), so that your syncs can run faster if your app has a higher tier. The field defaults to **Basic**, so existing connections continue to sync at the same rate. Select a higher tier only if TikTok has approved your app for it. If you select a tier that your app has not been granted, your syncs may fail with rate-limit errors. We have also added a new parameter, `api_rate_limit_tier`, to the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=tiktok_organic_app). We added two REST API endpoints that describe the log service types you can create and the configuration each one accepts: - [Retrieve Log Service Types](/docs/developer-resources/rest-api/api-reference/log-service-metadata/metadata-log-services.md) (`GET /v1/metadata/log-service-types`) returns a paginated list of the log service types you can create, with their name, description, icons, documentation link, and availability status. - [Retrieve Log Service Type Metadata](/docs/developer-resources/rest-api/api-reference/log-service-metadata/metadata-log-service-config.md) (`GET /v1/metadata/log-service-types/{service}`) returns the details of one log service type, including a `config` object that describes its configuration fields. For each field, the object shows its data type, its allowed values, and whether the field is read-only, immutable, or nullable. Fields that hold secrets, such as API keys, are marked with `"format": "password"`. Use these endpoints to find out which fields a log service type accepts before you [add a group log service](/docs/developer-resources/rest-api/api-reference/log-service-management/add-log-service.md) or [add an account log service](/docs/developer-resources/rest-api/api-reference/log-service-management/add-account-log-service.md). You can also use them to build or validate log service configuration in your tooling instead of hard-coding the fields for each service. You don't need to change anything in your existing integrations. The [Update a Connection](/docs/developer-resources/rest-api/api-reference/connections/modify-connection.md) endpoint now accepts the `destination_schema_names` parameter. Previously, the endpoint ignored this parameter, so you could change the setting only in the dashboard. You can set `destination_schema_names` to `FIVETRAN_NAMING` or `SOURCE_NAMING` only before the connection's initial sync. After the initial sync starts, you can only send the value that's already set. Attempting to change it returns an error. --- ## October 2026 The [Retrieve Connection Details](/docs/developer-resources/rest-api/api-reference/connections/connection-details.md) endpoint now returns a `connector_sdk_package_id` field for Connector SDK connections. The field contains the ID of the package currently used for the connection. Use the package ID with the [Retrieve Connector SDK Package Details](/docs/developer-resources/rest-api/api-reference/connector-sdk/get-connector-sdk-package.md) and [Download Connector SDK Package](/docs/developer-resources/rest-api/api-reference/connector-sdk/download-connector-sdk-package.md) endpoints to inspect or download the connection's source code, for example to investigate a sync failure. You no longer need to list all packages in your account and match them to the connection. The field is omitted for connections that are not Connector SDK connections and for Connector SDK connections that have no package deployed. After you deploy a connection to a different package, the field returns the new package ID. The [Create connection](/docs/rest-api/api-reference/connections/create-connection.md) and [Modify connection](/docs/rest-api/api-reference/connections/modify-connection.md) endpoints now support a time zone for cron sync schedules, matching the behavior already available in the dashboard. See the full list of changes below: - The `schedule` object now accepts a `time_zone` field. It takes an IANA time zone name, such as `Europe/Prague`, and is only supported when `schedule_type` is `CRON`. Sending it with any other schedule type returns a `400 Bad Request`. - Giving a connection a time zone it was not already syncing in returns a `400 Bad Request` when a transformation is scheduled on that connection, because such a transformation shares one schedule with every connection it is scheduled on. This covers setting `schedule.time_zone` and switching `schedule_type` back to `auto`, which restores the time zone the connection had before it was set to `manual`. Repeating the time zone the connection already syncs in is accepted, so a Terraform config that sets `time_zone` keeps applying cleanly. - The `cron` expression is evaluated in the given time zone, so daylight saving transitions are applied automatically. Previously, cron schedules set through the API always ran against the destination group's configured UTC offset. - The [Retrieve connection details](/docs/rest-api/api-reference/connections/connection-details.md) and [List connections](/docs/rest-api/api-reference/connections/list-connections.md) responses now include `time_zone` in the `schedule` object when a time zone is set. - Omitting `time_zone` in a modify request preserves the connection's existing time zone, so updating only the `cron` expression no longer clears a time zone that was set in the dashboard. When a connection has never had a time zone set, the destination group's configured UTC offset continues to be used. We've added Adobe Developer Console as a new authentication method for the Adobe Workfront connector. Adobe is retiring custom Workfront OAuth2 applications: you can no longer create new applications starting November 1, 2026, and existing applications stop working on February 1, 2027. We recommend that you switch your existing connections to the Adobe Developer Console authentication method before February 1, 2027. For more information, see the [Adobe migration guide](https://experienceleague.adobe.com/en/docs/workfront/using/administration-and-setup/configure-integrations/migrate-oauth2-to-developer-console). To support this enhancement, we have made the following changes: - Added a new drop-down menu, **Authentication type**, to the connection setup form. The drop-down menu lets you select either **Adobe Developer Console** or the legacy **Workfront OAuth2 application** authentication method. - Added the `auth_type` parameter to the Fivetran REST API. For more information, see the [create a connection API reference](/docs/rest-api/api-reference/connections/create-connection.md?service=adobe_workfront). For more information, see our [setup instructions](/docs/connectors/applications/adobe-workfront/setup-guide.md). --- ## September 2026 The [Sync Connection Data endpoint](/docs/developer-resources/rest-api/api-reference/connections/sync-connection.md) now returns a `data` object with the `result` field. The field contains the outcome of a sync trigger operation and shows whether a new sync was triggered or not, and the reason for not triggering the sync. The `message` field was updated to match the outcome returned in the `data.result` field. You can now enable or disable automated data validation (data checks) for a connection using the `data_checks` field in the REST API. When data checks are enabled, Fivetran compares source and destination data once per day to detect discrepancies such as missing rows or value mismatches. When disabled, validation is skipped. The `data_checks` field is supported for the following endpoints: - [Create a Connection](/docs/developer-resources/rest-api/api-reference/connections/create-connection.md) — set `data_checks` to `true` or `false` when creating a connection. - [Update a Connection](/docs/developer-resources/rest-api/api-reference/connections/modify-connection.md) — update the `data_checks` setting independently of other configuration changes. - [Retrieve Connection Details](/docs/developer-resources/rest-api/api-reference/connections/connection-details.md) — the current `data_checks` state is returned in the response. The field is only present for connector and destination combinations that support data validation. Sending `data_checks` for an unsupported combination returns a `400 Bad Request` error. **Click to see the list of supported connectors** - [Amazon Aurora MySQL](/docs/connectors/databases/mysql/aurora-setup-guide.md) - [Amazon Aurora PostgreSQL](/docs/connectors/databases/postgresql/aurora-setup-guide.md) - [Amazon RDS for Oracle](/docs/connectors/databases/oracle/oracle-connector/rds-setup-guide.md) - [Amazon RDS for PostgreSQL](/docs/connectors/databases/postgresql/rds-setup-guide.md) - [Amazon RDS for SQL Server](/docs/connectors/databases/sql-server/rds-setup-guide.md) - [Azure Database for MariaDB](/docs/connectors/databases/mariadb/azure-setup-guide.md) - [Azure Database for MySQL](/docs/connectors/databases/mysql/azure-setup-guide.md) - [Azure Database for PostgreSQL](/docs/connectors/databases/postgresql/azure-setup-guide.md) - [Azure SQL Database](/docs/connectors/databases/sql-server/azure-setup-guide.md) - [Azure SQL Managed Instance](/docs/connectors/databases/sql-server/azure-managed-setup-guide.md) - [Epic Clarity](/docs/connectors/databases/epic_clarity.md) - [Google Cloud SQL for MySQL](/docs/connectors/databases/mysql/google-cloud-mysql-setup-guide.md) - [Google Cloud SQL for PostgreSQL](/docs/connectors/databases/postgresql/gcs-setup-guide.md) - [Google Cloud SQL for SQL Server](/docs/connectors/databases/sql-server/gcs-setup-guide.md) - [Heroku Postgres](/docs/connectors/databases/postgresql/heroku-setup-guide.md) - [MariaDB](/docs/connectors/databases/mariadb/setup-guide.md) - [MariaDB on Amazon RDS](/docs/connectors/databases/mariadb/rds-setup-guide.md) - [MySQL](/docs/connectors/databases/mysql/setup-guide.md) - [MySQL on Amazon RDS](/docs/connectors/databases/mysql/rds-setup-guide.md) - [Oracle](/docs/connectors/databases/oracle/oracle-connector/setup-guide.md) - [Oracle E-Business Suite](/docs/connectors/applications/oracle-ebs/setup-guide.md) - [Oracle RAC](/docs/connectors/databases/oracle/oracle-connector/rac-setup-guide.md) - [PostgreSQL](/docs/connectors/databases/postgresql/setup-guide.md) - [SAP HANA](/docs/connectors/databases/sap/sap-hana.md) - [Snowflake](/docs/connectors/databases/snowflake.md) - [SQL Server](/docs/connectors/databases/sql-server/setup-guide.md) **Click to see the list of supported destinations** - [Snowflake](/docs/destinations/snowflake.md) - [BigQuery](/docs/destinations/bigquery.md) - [Redshift](/docs/destinations/redshift.md) - [Databricks](/docs/destinations/databricks.md) - [PostgreSQL](/docs/destinations/postgresql.md) - [Managed Data Lake Service](/docs/managed-data-lake-service.md) You can now retrieve and dismiss warnings for a connection using the REST API: - The [Retrieve Connection Warnings](/docs/developer-resources/rest-api/api-reference/connections/connection-warnings.md) endpoint returns all active warnings for a connection, grouped by destination table. Each warning includes the warning code, message, error details, and creation timestamp. - The [Dismiss Connection Warnings](/docs/developer-resources/rest-api/api-reference/connections/dismiss-connection-warnings-by-type.md) endpoint allows you to dismiss all active instances of a specific warning type for a connection, mirroring the dismissal functionality in the dashboard. This enables programmatic warning management for customers with large numbers of tables. > NOTE: This feature is currently in private preview. Please submit a support ticket if you would like to try out this feature. --- ## August 2026 Our [Create a Destination endpoint](/docs/developer-resources/rest-api/api-reference/destinations/create-destination.md) now returns `402 Payment Required` response when the selected destination region or [private networking](/docs/core-concepts/features.md#privatenetworking) is not available for your account plan. You can now check the status of asynchronous connection move operations using the [Retrieve Move Connection Job Status (Beta)](/docs/developer-resources/rest-api/api-reference/connections/connection-moved-job-status.md) REST API endpoint. This endpoint allows you to monitor the progress of move jobs initiated with the `CONTINUE_WITH_DATA` sync behavior. The [Connection Schema](/docs/rest-api/api-reference/connection-schema.md) response now includes a new read-only `parent_table` field for tables that are grouped under a parent (core) table. The field contains the name of the parent table and only appears in the response for child tables. This allows API consumers, such as Terraform, to accurately reconcile schema configuration state. Our Marketo connector now supports an additional sync of activity data from the previous three days during each incremental sync, to help capture late-arriving activity records. To support this enhancement, we have made the following changes: - Added a new toggle, **Sync Late Arriving Activities**, to the connection setup form - Added a new parameter, `trailingSyncEnabled`, to the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=marketo) For more information, see our [Marketo documentation](/docs/connectors/applications/marketo.md#lookbackwindowforlatearrivingactivities). The [Modify connection schema config](/docs/rest-api/api-reference/connection-schema/modify-connection-schema-config.md) endpoint now supports [row filtering](/docs/core-concepts/features/row-filter.md#rowfiltering) for individual tables. See the full list of changes below: - Each table in a schema update request now accepts a `row_filter` field of type `RowFilterUpdateRequest`. Setting this field creates or replaces the row filter for that table; sending `null` deletes the existing row filter; omitting the field leaves the existing row filter unchanged. - A row filter consists of a `name` (required), a `description` (required), and between 1 and 10 `column_clauses`. Each clause specifies a `column` (max 500 characters), a `column_type`, an `operator`, and a list of `values` (each value max 1,000 characters). All clauses are combined with a logical AND, so only rows satisfying every clause are synced to your destination. - The [Retrieve connection schema config](/docs/developer-resources/rest-api/api-reference/connection-schema/connection-schema-config.md) response now includes a `row_filtering_supported` boolean at the top level. The field is `true` when the connector type supports row filtering. The field is `false` when the connector does not support row filtering. The field is omitted when row filtering information is not available. - The `row_filter` for each table is included in both GET and PATCH responses when `row_filtering_supported` is `true`. The field is omitted from a table's response when no filter is configured. - Creating or removing a row filter triggers a historical resync for the affected table. Supported operators depend on the column type: | Operator | Compatible types | Values required | | --- | --- | --- | | `EQUALS`, `NOT_EQUALS` | LONG, FLOAT, DOUBLE, BIGDECIMAL, DATE, DATETIME, STRING, BOOLEAN | Exactly 1 | | `LESS`, `LESS_OR_EQUALS`, `GREATER`, `GREATER_OR_EQUALS` | LONG, FLOAT, DOUBLE, BIGDECIMAL, DATE, DATETIME, STRING | Exactly 1 | | `STARTS_WITH`, `CONTAINS` | STRING | Exactly 1 | | `IN` | LONG, FLOAT, DOUBLE, BIGDECIMAL, STRING | At least 1 | | `IS_NULL`, `IS_NOT_NULL` | All types | 0 | Value format requirements by column type: | Column type | Required format | | --- | --- | | `DATETIME` | UTC timestamp ending in `Z`, e.g. `2024-01-01T00:00:00Z` | | `DATE` | `yyyy-MM-dd`, e.g. `2024-01-01` | | `BOOLEAN` | Lowercase `"true"` or `"false"` exactly | | `BIGDECIMAL` | Each value must be at most 50 characters | | `STRING` + `IN` | Combined length of all values in the clause must not exceed 10,000 characters | --- ## July 2026 We now support external cloud storage for the Email connector. You can choose whether Fivetran stores email attachments in Fivetran-managed storage or in your Amazon S3, Azure Blob Storage, or Google Cloud Storage bucket. For more information, see our [setup instructions](/docs/connectors/files/email/setup-guide.md) and [REST API documentation](/docs/rest-api/api-reference/connections/create-connection.md?service=email). You can now move connections from one destination group to another using the [Move a Connection (Beta)](/docs/developer-resources/rest-api/api-reference/connections/connection-moved.md) REST API endpoint. We have added a new feature, **Dynamically extract tables**. You can now define a single regex pattern with a named capture group, `(?<table>...)`, to automatically extract table names from file paths. This feature automatically creates and maps destination tables based on your file naming patterns, eliminating the need for manual intervention. To support this feature, we have made the following changes to the connection setup form: - Added a new option, **File mapping**, that allows you to choose between **Define per table** and **Dynamically extract tables**. - Added a new field, **Table extraction pattern**, to specify your own regex pattern. - Added a new button, **Preview**, to validate the specified regex pattern. Key benefits include: - Simplified configuration: Avoids repetitive setup for multiple entities. - Automatic table creation: Captures new entities as they appear in your source, without additional configuration. For more information, see our [Dynamic Table Mapping tutorial](/docs/connectors/files/tutorials/dynamic-table-mapping.md) and [setup instructions](/docs/connectors/files/share-point/setup-guide.md). We are gradually rolling out this change to all existing connections. We now support specifying custom primary keys for tables created through dynamic table mapping. We have added a new feature, **Dynamically extract tables**. You can now define a single regex pattern with a named capture group, `(?<table>...)`, to automatically extract table names from file paths. This feature automatically creates and maps destination tables based on your file naming patterns, eliminating the need for manual intervention. To support this feature, we have made the following changes to the connection setup form: - Added a new option, **File mapping**, that allows you to choose between **Define per table** and **Dynamically extract tables**. - Added a new field, **Table extraction pattern**, to specify your own regex pattern. - Added a new button, **Preview**, to validate the specified regex pattern. Key benefits include: - Simplified configuration: Avoids repetitive setup for multiple entities. - Automatic table creation: Captures new entities as they appear in your source, without additional configuration. For more information, see our [Dynamic Table Mapping tutorial](/docs/connectors/files/tutorials/dynamic-table-mapping.md) and [setup instructions](/docs/connectors/files/ftp/setup-guide.md). We are gradually rolling out this change to all existing connections. We now support specifying custom primary keys for tables created through dynamic table mapping. --- ## June 2026 Effective July 4, 2026, you can specify the delimiter used in your Klarna settlement reports to improve sync reliability for reports that use a delimiter other than the default value. To support this enhancement, we have made the following changes: - Added a new field, **CSV delimiter**, to the connection setup form - Added a new API parameter, `csv_delimiter`, to the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=klarna) We will automatically migrate the current delimiter values for all existing connections. The following endpoints now require the `Account Read` permission instead of `Account Destination Create`: - [List Proxy Agents](/docs/developer-resources/rest-api/api-reference/proxy-agent/get-proxy-agent.md) - [Retrieve Proxy Agent Details](/docs/developer-resources/rest-api/api-reference/proxy-agent/get-proxy-agent-details.md) - [List Proxy Agent Connections](/docs/developer-resources/rest-api/api-reference/proxy-agent/get-proxy-agent-connections.md) - [List Private Links](/docs/developer-resources/rest-api/api-reference/private-links/get-private-links.md) - [Retrieve Private Link Details](/docs/developer-resources/rest-api/api-reference/private-links/get-private-link-details.md) We have added a new field, **Allowed Senders**, to the connection setup form. You can now use this field to restrict file ingestion to approved email addresses or domains. If specified, the connector processes only emails from matching senders. For more information, see [our documentation](/docs/connectors/files/email/setup-guide-senders-allowed-list.md#setupinstructions) We have changed the connector type of our OpenAI connector from Lite to Standard. The OpenAI connector can now sync [Codex Enterprise Analytics API](https://developers.openai.com/codex/enterprise/governance#analytics-api) data from a specific ChatGPT workspace. To support this enhancement, we have made the following changes: - Added two new fields, **Codex Enterprise Analytics API key** and **Workspace ID**, to the connection setup form - Added two new parameters, `api_key_3` and `workspace_id`, to the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=openai) The [Connect Card configuration](/docs/developer-resources/rest-api/api-reference/connections/create-connection.md) now supports the `all_fields` parameter. When set to `true`, Connect Card displays all available setup fields for a connection, including fields that are hidden by default for certain connectors. Fivetran REST API endpoints now correctly reject floating-point values for integer fields. Previously, sending a floating-point number for an integer field would silently truncate it to the nearest integer and succeed. The request now returns a `400 Bad Request` error, consistent with the integer type declared for those fields. The `group_region` field in the [Create a Proxy Agent](/docs/developer-resources/rest-api/api-reference/proxy-agent/create-proxy-agent.md) endpoint is now optional. Previously, omitting `group_region` returned a `400 Bad Request` error. You can now create a proxy agent without specifying a region. A regionless proxy agent is not tied to any specific region and can serve connections in any region. --- ## May 2026 We now support the [ShipStation V2 API](https://docs.shipstation.com/apis/openapi) to connect the ShipStation connector with Fivetran. To support this enhancement, we have added the following changes: - Added a new field, **V2 API key**, to the setup form. Enter your v2 API key to fetch data using the latest ShipStation v2. - Added a new parameter, `v2_api_key`, to the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=shipstation). For more information, see our [setup instructions](/docs/connectors/applications/shipstation/setup-guide.md) and [REST API documentation](/docs/rest-api/api-reference/connections/create-connection.md?service=shipstation). We are gradually rolling out these enhancements to all existing connections. We have discontinued the `archive_pattern` and `pattern` parameters in the Fivetran REST API for the following connectors: - Amazon S3 - Azure Blob Storage - Box - Dropbox - Email - FTP - Google Cloud Storage - Google Drive - SharePoint - SFTP - S3-Compatible Storage We will continue supporting these parameters for both new and existing connections until August 31, 2026. After August 31, 2026, we will stop supporting these parameters for all connections and replace them with the `files.archive_pattern` and `files.pattern` parameters respectively. We now support a new authentication method, **OAuth 2.0**, for the Veeva Vault connector. To support this enhancement, we have added the following changes: - Added new fields to the connection setup form: - **Client ID** - **Client Secret** - **OIDC Profile ID** - **OAuth Token Service URL** - **Vault DNS** - **Scope** - Added the following parameters to the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=veeva_vault): - `authentication_method` - `client_id` - `client_secret` - `o_auth_service_token_url` - `oidc_profile_id` - `scope` - `vault_dns` For more information, see our [setup instructions](/docs/connectors/applications/veeva-vault/setup-guide.md) and [REST API documentation](/docs/rest-api/api-reference/connections/create-connection.md?service=veeva_vault). We have upgraded the Veeva Vault API version from **v25.2** to **v26.1** to support newer API features and improvements. This upgrade is being rolled out gradually and is transparent to users. --- ## April 2026 We have added two new options, `FORM` and `SEGMENT` to select the custom report type in the connection setup form. You can now select the `FORM` and `SEGMENT` custom reports from the **Type** drop-down menu while configuring your connection in **Pack Mode**. For more information, see the [setup instructions](/docs/connectors/applications/klaviyo/setup-guide.md) and the [REST API Configuration](/docs/connectors/applications/klaviyo/api-configuration.md). Our Workday Adaptive Planning connector now supports sync modes for **Account** and **Level**. You can choose to sync specific accounts and levels or sync all accounts and levels. To support this enhancement, we have made the following changes in the setup form: - Added two new options, **Sync all accounts** and **Select specific accounts** to the **Account sync mode** field. - Added two new options, **Sync all levels** and **Select specific levels** to the **Level sync mode** field. - Added a new section, **Accounts selected**, to select the specific accounts you want to include in your report. - Added a new section, **Levels selected**, to select the specific levels you want to include in your report. For more information, see our [setup instructions](/docs/connectors/applications/workday-adaptive-planning/setup-guide-new-ui.md) and [REST API documentation](/docs/rest-api/api-reference/connections/create-connection.md?service=workday_adaptive). We are gradually rolling out these enhancements to all existing connections. We now support the [Harvest v3 (OAuth 2.0)](https://harvestdocs.greenhouse.io/docs/overview-and-philosophy) to connect the Greenhouse connector with Fivetran. To support this enhancement, we have made the following changes: - Added a new toggle button, **Use Harvest API v3**, to the setup form. The toggle button allows you to fetch data using the latest Harvest v3. - Added two new fields, **Client ID** and **Client secret**, to the setup form. - Added two new parameters, `client_id` and `client_secret`, to the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=greenhouse). For more information, see our [setup instructions](/docs/connectors/applications/greenhouse/setup-guide.md#setupinstructions) and [REST API documentation](/docs/rest-api/api-reference/connections/create-connection.md?service=greenhouse). We are gradually rolling these changes to all existing destinations. We have removed the following deprecated fields from the Fivetran REST API for Workday RaaS connections to align with the multi-report flow configuration: - Removed the `primary_keys` parameter - Removed the `report_format_type` parameter - Removed the `report_url` parameter - Removed the `support_nested_columns` parameter - Removed the `generate_fivetran_pk` parameter These fields are now only used within the `reports.fields` configuration for individual reports in the multi-report flow. If you are using the Fivetran REST API or Terraform provider to manage Workday RaaS connections, please update your configurations to use the multi-report flow instead. We have added OAuth 2.0 as a new authentication method for the Samsara connector. To support this enhancement, we have made the following changes: - Added a new drop-down menu, **Authentication type**, to the connection setup form. The drop-down menu allows you to select the authentication method. - Added two new fields, **App ID** and **App secret**, to the connection setup form. These fields appear only when you select **OAuth 2.0** authentication and allow you to provide your OAuth 2.0 app credentials. - Renamed the **Access Token** field to **API token**. - Added the following parameters to the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=samsara): - `auth_type` - `app_id` - `app_secret` For more information, see our [setup instructions](/docs/connectors/applications/samsara/setup-guide.md). You can now configure custom variables for [Quickstart Transformations](/docs/transformations/data-models/quickstart-management.md) by using the [Transformation API resource](/docs/developer-resources/rest-api/api-reference/transformation-management.md). This lets you create more flexible and reusable transformation configurations. Supported variables are package-specific and are included in the package’s metadata. --- ## March 2026 We have implemented pagination for the `SESSION` table. Our Gainsight Customer Success connector now supports OAuth 2.O authentication. To support this enhancement, we have made the following changes: - Added a new field, **Authentication**, to the connection setup form, allowing you to choose between OAuth 2.0 and API key authentication methods - Added a new parameter, `authentication_method`, to the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=gainsight_customer_success) For more information, see our [setup instructions](/docs/connectors/applications/gainsight-customer-success/setup-guide.md). --- ## February 2026 We’ve extended the table response model for the [Connection Schema](/docs/developer-resources/rest-api/api-reference/connection-schema.md) resource endpoints by adding a new field, `supports_history_mode`. This boolean field indicates whether a table supports history mode. We have added a new drop-down menu, **Region**, to the connection setup form. You can now specify the Appcues region from which you want to sync the data. We have also added a new config parameter, `region`, to the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=appcues). --- ## January 2026 We now use a centralized OAuth application maintained by Fivetran to authenticate all TikTok Organic connections. We have made this change to align with the new TikTok OAuth framework. To support this update, we have made the following changes: - Removed the **App ID** and **Secret** fields from the connection setup form. - Added a new field, **Business category**, to the connection setup form. The new field allows you to select the TikTok business categories whose data you want to sync. - Removed the `app_id` and `secret` parameters from the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=tiktok_organic_app). - Added a new parameter, `business_category`, to the Fivetran REST API. We are gradually rolling out this change to all existing connections. If your TikTok Organic connection was set up _before_ January 28, 2026, you must set up a new connection to continue syncing data without interruption. For more information, see our setup instructions. DSV is deprecating Basic Authentication and transitioning to OAuth 2.0 for improved security and efficiency. To support this, we have made the following changes: - Added new fields, **Tracking Subscription key**, **DSV Username**, **DSV Password**, and **API Development Environment**, to the connection setup form. These fields allow you to specify your Tracking Subscription key, DSV Username, DSV Password, and your API development environment. - Added three new parameters, `tracking_subscription_key`, `dsv_username`, `dsv_password`, and `environment`, to the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=dsv). For more information, see our [setup instructions](/docs/connectors/applications/dsv/setup-guide.md). We have added a new authentication method, **Client certificate**, for our SharePoint connector. You can now use this method to authenticate your SharePoint account and connect with Fivetran. To support these features, we have made the following changes to the connection setup form: - Added **Client ID**, **Client Certificate** and **Private Key** fields, allowing you to provide your own app credentials. - Added **Run connection test** button to validate your credentials. For more information, see our [setup instructions](/docs/connectors/files/share-point/setup-guide.md) and [REST API configuration](/docs/rest-api/api-reference/connections/create-connection.md?service=share_point). We are gradually rolling out these enhancements to all existing connections. All new StackAdapt connections created _on or after_ January 15, 2026 now use the StackAdapt GraphQL API to retrieve data. We have made this change because StackAdapt is sunsetting its REST API. To support this update, we have made the following changes to the StackAdapt connector: - Added a new drop-down menu, **Environment**, to the connection setup form. The drop-down menu allows you to select your StackAdapt environment. - Added a new parameter, `environment`, to the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=stackadapt_graphql). If your StackAdapt connection was created _before_ January 15, 2026, you must set up a new connection to continue syncing data without interruption. For more information, see our [setup instructions](/docs/connectors/applications/stackadapt-graphql/setup-guide.md). The Upland Software connector now supports API key authentication. To support this enhancement, we have made the following changes: - Added a new drop-down menu, **Authentication type**, to the connection setup form. The drop-down menu allows you to select the authentication method of your choice. - Added a new field, **API key**, to the connection setup form. The field allows you to specify your API key. - Added two new parameters, `auth_type` and `api_key`, to the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=upland). For more information, see our [setup instructions](/docs/connectors/applications/upland/setup-guide.md). Our [REST API](/docs/developer-resources/rest-api.md) now supports setting transformations as parents for dependent schedules. When creating or updating transformations with the integrated schedule (`schedule_type: INTEGRATED`) or custom schedules (`schedule_type: TIME_OF_DAY` or `schedule_type: INTERVAL`) with smart syncing enabled (`smart_syncing: true`), you can now specify `transformation_ids` in addition to or instead of `connection_ids`. This lets you run transformations only after upstream ones finish, making orchestration workflows more flexible. --- ## December 2025 You can no longer change your [account role](/docs/getting-started/fivetran-dashboard/account-settings/role-based-access-control.md#standardrolesinourrbacmodel) either through the [Update a User](/docs/developer-resources/rest-api/api-reference/users/modify-user.md) endpoint or in the dashboard. We have added a new feature, **Dynamically extract tables**. You can now define a single regex pattern with a named capture group `(?<table>...)` to automatically extract table names from file paths. This feature automatically creates and maps destination tables based on your file naming patterns, eliminating the need for manual intervention. To support this feature, we have made the following changes to the connection setup form: - Added a new option, **File mapping**, that allows you to choose between **Define per table** and **Dynamically extract tables**. - Added a new field, **Table extraction pattern**, to specify your own regex pattern. - Added a new button, **Preview**, to validate the specified regex pattern. Key benefits include: - Simplified configuration: Avoids repetitive setup for multiple entities. - Automatic table creation: Captures new entities as they appear in your source, without additional configuration. For more information, see our [Dynamic Table Mapping tutorial](/docs/connectors/files/tutorials/dynamic-table-mapping.md) and [setup instructions](/docs/connectors/files/azure-blob-storage/setup-guide.md). We are gradually rolling out this change to all existing connections. We have added a new feature, **Dynamically extract tables**. You can now define a single regex pattern with a named capture group, `(?<table>...)`, to automatically extract table names from file paths. This feature automatically creates and maps destination tables based on your file naming patterns, eliminating the need for manual intervention. To support this feature, we have made the following changes to the connection setup form: - Added a new option, **File mapping**, that allows you to choose between **Define per table** and **Dynamically extract tables**. - Added a new field, **Table extraction pattern**, to specify your own regex pattern. - Added a new button, **Preview**, to validate the specified regex pattern. Key benefits include: - Simplified configuration: Avoids repetitive setup for multiple entities. - Automatic table creation: Captures new entities as they appear in your source, without additional configuration. For more information, see our [Dynamic Table Mapping tutorial](/docs/connectors/files/tutorials/dynamic-table-mapping.md) and [setup instructions](/docs/connectors/files/sftp/setup-guide.md). We are gradually rolling out this change to all existing connections. We have made the following changes to the Appcues connector: - Removed the **Email** field from the connection setup form - Discontinued the `email` parameter from the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=appcues) You can now specify the country whose data you want to sync. To support this enhancement, we have made the following changes: - Added a new drop-down menu, **Country**, to the connection setup form - Added a new parameter, `country`, to the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=sistrix) --- ## November 2025 We have added a new feature, **Dynamically extract tables**. You can now define a single regex pattern with a named capture group `(?<table>...)` to automatically extract table names from file paths. This feature automatically creates and maps destination tables based on your file naming patterns, eliminating the need for manual intervention. To support this feature, we have made the following changes to the connection setup form: - Added a new option, **File mapping**, that allows you to choose between **Define per table** and **Dynamically extract tables**. - Added a new field, **Table extraction pattern**, to specify your own regex pattern. - Added a new button, **Preview**, to validate the specified regex pattern. Key benefits include: - Simplified configuration: Avoids repetitive setup for multiple entities. - Automatic table creation: Captures new entities as they appear in your source, without additional configuration. For more information, see our [Dynamic Table Mapping tutorial](/docs/connectors/files/tutorials/dynamic-table-mapping.md) and [setup instructions](/docs/connectors/files/amazon-s3/setup-guide.md). We are gradually rolling out this change to all existing connections. --- ## October 2025 We have added a new authentication method for our Azure Blob Storage connector. You can now use a Microsoft Entra authentication method to connect your Azure Blob Storage with Fivetran. To support these features, we have made the following changes to the connection setup form: - Added **Authentication method** field, that allows you to select between **Microsoft Entra ID - client credentials grant using client secret** and **Connection String** authentication methods. - Added **Storage account**, **Tenant ID**, **Client ID**, and **Client secret** fields, allowing you to provide your own app credentials. For more information, see our [setup instructions](/docs/connectors/files/azure-blob-storage/setup-guide.md) and [REST API configuration](/docs/rest-api/api-reference/connections/create-connection.md?service=azure_blob_storage). We are gradually rolling out these changes to all existing connections. We have added a new authentication method for our Microsoft List connector. You can now use a custom authentication method to connect your Microsoft list account with Fivetran. To support these features, we have made the following changes to the connection setup form: - Added **Authentication method** field, that allows you to select between a **Quick Setup (Default)** and an **Advanced Setup**. - Added **Client ID**, **Client secret**, **Tenant Id** and **Site Id** fields, allowing you to provide your own app credentials. - Added a **Run connection test** button to validate the connection credentials. For more information, see our [setup instructions](/docs/connectors/applications/microsoft-lists/setup-guide.md) and [REST API configuration](/docs/rest-api/api-reference/connections/create-connection.md?service=microsoft_lists). We are gradually rolling out these changes to all existing connections. --- ## September 2025 We now display [replacement role name](/docs/rest-api/api-reference/roles/list-all-roles.md#replacement_role_name) for the [deprecated roles](/docs/rest-api/api-reference/roles/list-all-roles.md#is_deprecated) in the `role` field in the [List all users within a group](/docs/developer-resources/rest-api/api-reference/groups/list-all-users-in-group.md) endpoint response. --- ## August 2025 We've introduced the `custom_column_ids` API parameter for configuring your [Google Search Ads 360](/docs/rest-api/api-reference/connections/create-connection.md?service=google_search_ads_360) custom reports. We are gradually rolling out these changes to all customers. We have improved the setup experience for FTP connections. - Added a new configuration option, **Run connection test** to perform an intermediate test during configuration - Added a new configuration option, **Preview Files** to perform an intermediate test during configuration - Added support for displaying fields based on the file type - Added a new field, **Quote character**, to use an enclosing character - Reorganised fields to make the setup form more intuitive - Removed **Infer** as an option from the **File Type** field - Removed the **Enable Advanced Options** toggle - Changed the **Null Sequence** field to a toggle - For the **Delimiter character(s)** field, we now use `,` as the default value - For the **Line Separator** field, we now use `\n` as the default value For more information, see our [setup instructions](/docs/connectors/files/ftp/setup-guide.md) and [REST API configuration](/docs/connectors/files/ftp/api-configuration.md#ftpapiconfiguration). We are gradually rolling out these changes to all existing connections. We have made changes to our Marketo connection setup form and REST API parameters to support the [Marketo SOAP API deprecation](https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/soap/soap-api#:~:text=The%20SOAP%20API%20is%20being%20deprecated%20and%20will%20no%20longer%20be%20available%20after%20October%2031st%202025). These changes won't impact how your connection syncs data to your destination. We have removed the Provide SOAP API Credentials for BULK API Quota Estimation toggle and the following related fields from the connection setup form: - SOAP API User Id - SOAP API Encryption Key - SOAP API Endpoint Similarly, we have discontinued the following parameters from the REST API Configuration: - `user_id` - `encryption_key` - `soap_uri` As of August 11, 2025, the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=double_click_campaign_manager) no longer supports the following configuration parameters for Google Campaign Manager 360 connections: - `conversion_dimensions` - `custom_floodlight_variables` - `dimensions` - `enabble_all_dimension_combinations` - `metrics` - `per_interaction_dimensions` - `report_configuration_ids` - `report_type` We will fully [sunset](/docs/getting-started/core-concepts.md#releasephases) these parameters on November 11, 2025. --- ## July 2025 We have improved the setup experience for Dropbox connections. - Added a new configuration option, **Preview Files** to perform an intermediate test during configuration - Added support for displaying fields based on the file type - Added a new field, **Quote character**, to use an enclosing character - Reorganised fields to make the setup form more intuitive - Removed **Infer** as an option from the **File Type** field - Removed the **Enable Advanced Options** toggle - Changed the **Null Sequence** field to a toggle - For the **Delimiter character(s)** field, we now use `,` as the default value - For the **Line Separator** field, we now use `\n` as the default value For more information, see our [setup instructions](/docs/connectors/files/dropbox/setup-guide.md) and [REST API configuration](/docs/connectors/files/dropbox/api-configuration.md#dropboxapiconfiguration). We are gradually rolling out these changes to all existing connections. You can now configure your Managed Data Lake Service destination using the [Fivetran REST API](/docs/rest-api/api-reference/destinations/create-destination.md?service=managed_data_lake). This feature is available only for Free, Standard, Enterprise, and Business Critical accounts. We have improved the setup experience for Box connections. - Added a new configuration option, **Preview Files** to perform an intermediate test during configuration - Added support for displaying fields based on the file type - Added a new field, **Quote character**, to use an enclosing character - Reorganised fields to make the setup form more intuitive - Removed **Infer** as an option from the **File Type** field - Removed the **Enable Advanced Options** toggle - Changed the **Null Sequence** field to a toggle - For the **Delimiter character(s)** field, we now use `,` as the default value - For the **Line Separator** field, we now use `\n` as the default value For more information, see our [setup instructions](/docs/connectors/files/box/setup-guide.md) and [REST API configuration](/docs/connectors/files/box/api-configuration.md#boxapiconfiguration). We are gradually rolling out these changes to all existing connections. Our [Proxy Agent Management API](/docs/developer-resources/rest-api/api-reference/proxy-agent.md) resource now supports the [Regenerate secrets for Proxy Agent](/docs/developer-resources/rest-api/api-reference/proxy-agent/regenerate-secrets-proxy-agent.md) method. --- ## June 2025 We have made changes to support the latest version of the Proxy Agent. We have made the following changes to the response of the [Create a Proxy Agent](/docs/rest-api/proxy-management.md#createaproxyagent) and [Retrieve Proxy Agent Details](/docs/rest-api/proxy-management.md#retrieveproxyagentdetails) of our [Proxy Agent Management API](/docs/rest-api/proxy-management.md): - Added the following parameters: - `client_cert` - the public certificate used by the proxy agent - `client_private_key` - the private key used by the proxy agent - Removed the following parameters: - `proxy_server_uri` - the proxy server URI You can now set the `prioritise_bulk_export_over_rest` parameter using the Fivetran REST API. This parameter allows your connection to use [BULK export](https://developers.marketo.com/rest-api/bulk-extract/) to extract both the `LEAD` and `ACTIVITY_*` tables to improve connection performance and reduce the number of API calls. We have improved the setup experience for Email connections. - Added a new configuration option, **Preview Files** to perform an intermediate test during configuration - Added support for displaying fields based on the file type - Added a new field, **Quote character**, to use an enclosing character - Reorganised fields to make the setup form more intuitive - Removed **Infer** as an option from the **File Type** field - Removed the **Enable Advanced Options** toggle - Changed the **Null Sequence** field to a toggle - For the **Delimiter character(s)** field, we now use `,` as the default value - For the **Line Separator** field, we now use `\n` as the default value For more information, see our [setup instructions](/docs/connectors/files/email/setup-guide-revamp.md) and [REST API configuration](/docs/rest-api/api-reference/api-configuration/connector-configuration.md#email). We are gradually rolling out these changes to all existing connections. --- ## May 2025 We have added a new authentication method for our SharePoint connector. You can now use a custom authentication method to connect your SharePoint account with Fivetran. To support these features, we have made the following changes to the connection setup form: - Added **Client ID** and **Client secret** fields, allowing you to provide your own app credentials. - Added a **Run connection test** button to validate the connection credentials. For more information, see our [setup instructions](/docs/connectors/files/share-point/setup-guide.md) and [REST API configuration](/docs/rest-api/api-reference/connections/create-connection.md?service=share-point). We are gradually rolling out these changes to all existing connections. We now support syncing files to multiple destination tables and handling file patterns in [Merge Mode](/docs/connectors/files/google-drive.md#mergemode). To support these features, we have made the following changes to the connection setup form: - Added the **Files** field and sub-fields **Table name** and **File pattern**, that enable you to define destination tables and specify the file pattern names. - Renamed the **Destination table** field to **Table group name** to enable unique identification of connections that share the same destination schema name. Also, we have discontinued the `table` and `pattern` configuration parameters for all Google Drive connections and will delete them by August 31, 2025. For more information, see our [setup instructions](/docs/connectors/files/google-drive/setup-guide.md) and [REST API configuration](/docs/rest-api/api-reference/connections/create-connection.md?service=google_drive). We are gradually rolling out these enhancements to all existing connections. The `groupId` parameter is now optional when creating a [Hybrid Deployment Agent](/docs/core-concepts/deployment-models/hybrid-deployment.md) using our [REST API](/docs/developer-resources/rest-api.md). If not provided, Fivetran sets its value to null, allowing for more flexible agent management. As a result, We made the following updates to our [Role-Based Access Control model](/docs/getting-started/fivetran-dashboard/account-settings/role-based-access-control.md): - In the REST API, the `DESTINATION_CONNECTION_MANAGE` permission is replaced by the `ACCOUNT_DESTINATION_CREATE` permission for the following endpoints: - [Create a Hybrid Ddeployment Agent](/docs/rest-api/api-reference/hybrid-deployment-agent-management/create-local-processing-agent.md#createahybriddeploymentagent) - [Delete a Hybrid Deployment Agent](/docs/rest-api/api-reference/hybrid-deployment-agent-management/delete-local-processing-agent.md#deleteahybriddeploymentagent) - [Regenerate Authentication Keys](/docs/rest-api/api-reference/hybrid-deployment-agent-management/re-auth-local-processing-agent.md#regenerateauthenticationkeys) - [Reset Credentials](/docs/rest-api/api-reference/hybrid-deployment-agent-management/reset-local-processing-agent-credentials.md#resetcredentials). - The System Keys rules are now managed at the account level. --- ## April 2025 We now support syncing files to multiple destination tables and handling file patterns. To support these features, we have made the following changes to the connection setup form: - Added the **Files** field and sub-fields **Table name** and **File pattern**, that enable you to define destination tables and specify the file pattern names. - Renamed the **Destination table** field to **Table group name** to enable unique identification of connections that share the same destination schema name. Also, we have discontinued the `table` and `pattern` configuration parameters for all Amazon S3 connections and will delete them by August 31, 2025. For more information, see our [setup instructions](/docs/connectors/files/amazon-s3/setup-guide.md) and [REST API configuration](/docs/rest-api/api-reference/connections/create-connection.md?service=s3). We are gradually rolling out these enhancements to all existing connections. We now support syncing files to multiple destination tables and handling file patterns. To support these features, we have made the following changes to the connection setup form: - Added the **Files** field and sub-fields **Table name** and **File pattern**, that enable you to define destination tables and specify the file pattern names. - Renamed the **Destination table** field to **Table group name** to enable unique identification of connections that share the same destination schema name. Also, we have discontinued the `table` and `pattern` configuration parameters for all Azure Blob Storage connections and will delete them by August 31, 2025. For more information, see our [setup instructions](/docs/connectors/files/azure-blob-storage/setup-guide.md) and [REST API configuration](/docs/rest-api/api-reference/connections/create-connection.md?service=azure_blob_storage). We are gradually rolling out these enhancements to all existing connections. We have removed the dbt Transformation and Quickstart Transformation resources in our [REST API](/docs/developer-resources/rest-api.md). Use the [Transformation Management](/docs/developer-resources/rest-api/api-reference/transformation-management.md) resource instead. --- ## March 2025 We are now requiring Base64URL encoding for certificate and fingerprint hashes in the REST API request path-parameters for the following endpoints: - [Get connection certificate details](/docs/developer-resources/rest-api/api-reference/certificates/get-connection-fingerprint-details.md) - [Get destination certificate details](/docs/developer-resources/rest-api/api-reference/certificates/get-destination-fingerprint-details.md) - [Revoke connection certificate](/docs/developer-resources/rest-api/api-reference/certificates/revoke-connection-certificate.md) - [Revoke destination certificate](/docs/developer-resources/rest-api/api-reference/certificates/revoke-destination-certificate.md) - [Get connection fingerprint details](/docs/developer-resources/rest-api/api-reference/certificates/get-connection-fingerprint-details.md) - [Get destination fingerprint details](/docs/developer-resources/rest-api/api-reference/certificates/get-destination-fingerprint-details.md) - [Revoke connection fingerprint](/docs/developer-resources/rest-api/api-reference/certificates/revoke-connection-fingerprint.md) - [Revoke destination fingerprint](/docs/developer-resources/rest-api/api-reference/certificates/revoke-destination-fingerprint.md) The certificate and fingerprint hashes in the REST API response body are still returned in raw format. The new `id` field is added to the response body of all certificate and fingerprint endpoints. This field contains the Base64URL encoded certificate or fingerprint hash. Using the raw format for certificate and fingerprint hashes in the request path-params is deprecated and will no longer be supported as of May 1, 2025. The response of the [List all roles](/docs/developer-resources/rest-api/api-reference/roles/list-all-roles.md) endpoint has been expanded with the following fields: - is_deprecated: defines whether the role is deprecated - replacement_role_name: the name of the new role replacing the deprecated role. --- ## February 2025 The [Retrieve Function Connection State](/docs/rest-api/api-reference/connectors/connector-state.md) and [Update Function Connection State](/docs/rest-api/api-reference/connectors/modify-connector-state.md) endpoints in our [REST API](/docs/developer-resources/rest-api.md) that allow you to get and update the state of [Functions](/docs/connectors/functions.md) and [Connector SDK](/docs/connectors/connector-sdk.md) connections are [generally available](/docs/core-concepts.md#releasephases). We have removed the dbt Transformation resource in our [REST API](/docs/developer-resources/rest-api.md). Use the [Transformation Management](/docs/developer-resources/rest-api/api-reference/transformation-management.md) resource instead. We have renamed the Connector Management API to the [Connection Management API](/docs/developer-resources/rest-api/api-reference/connections.md) and the Connector Schema Management API to the [Connection Schema Management API](/docs/developer-resources/rest-api/api-reference/connection-schema.md) to align with our [terminology](/docs/getting-started/faq.md#whatsthedifferencebetweenaconnectorandaconnection). We have also updated all API paths from `/connectors` to `/connections`, while continuing to support both access methods. We have updated the relevant paths in the following resources from `/connectors` to `/connections`, while continuing to support both access methods: - [Team](/docs/developer-resources/rest-api/api-reference/teams.md) - [User](/docs/developer-resources/rest-api/api-reference/users.md) - [Certificate](/docs/developer-resources/rest-api/api-reference/certificates.md) - [Group](/docs/developer-resources/rest-api/api-reference/groups.md) Our [REST API](/docs/developer-resources/rest-api.md) responses now use the `"yyyy-MM-dd'T'HH:mm:ss.SSSSSS'Z'"` [timestamp format](/docs/developer-resources/rest-api/getting-started.md#response). --- ## January 2025 We now support the following Xray data residency regions: - Australia - EU - Global - USA Previously, we supported only the Global region. We have added a new drop-down menu, **Region**, to the connector setup form. The drop-down menu allows you to select the Xray data residency regions. For more information, see our [setup instructions](/docs/connectors/applications/xray/setup-guide.md). We have deprecated the [dbt Transformation](/docs/rest-api/api-reference/dbt-transformation-management.md) and [Quickstart Transformation](/docs/rest-api/api-reference/qdm-transformation-management.md) resources in our [REST API](/docs/developer-resources/rest-api.md). Use the [Transformation Management](/docs/developer-resources/rest-api/api-reference/transformation-management.md) resource instead. Effective January 5, 2025, the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=airtable) no longer supports the `base_id` and `table_name` configuration parameters for Airtable connections. We will [sunset](/docs/getting-started/core-concepts.md#releasephases) these parameters on April 5, 2025. We are introducing changes to our History mode feature to prevent data loss during re-syncs. Effective January 15, 2025, the `Last Modified Time` field must be present in all source tables that have history mode enabled. We have updated the connection methods for configuring the Azure Service Bus connector via the REST API. We now use `DIRECT`, `SSH_TUNNEL`, and `PRIVATE_LINK` for configuration. Previously, we used `direct`, `sshTunnel`, and `privateLink`. For more information, see our [REST API configuration](/docs/rest-api/api-reference/connections/create-connection.md?service=azure_service_bus). --- ## December 2024 We have added a new parameter, `password`, to the [REST API configuration](/docs/rest-api/api-reference/connections/create-connection.md?service=delighted). We have improved the setup experience for our Azure Blob Storage connector. New connections created on or after December 20, 2024, will have the following changes in the connection setup form: - Added a new configuration option, **Run connection test** to perform an intermediate test during configuration - Added a new configuration option, **Preview Files**, to perform an intermediate test during configuration - Added support for displaying fields based on the file type - Added a new field, **Quote character**, to use an enclosing character - Reorganised fields to make the setup form more intuitive - Removed **Infer** as an option from the **File Type** field - Removed the **Enable Advanced Options** toggle - Changed the **Null Sequence** field to a toggle - For the **Delimiter character(s)** field, we now use `,` as the default value - For the **Line Separator** field, we now use `\n` as the default value For more information, see our [setup instructions](/docs/connectors/files/azure-blob-storage/setup-guide.md) and [REST API configuration](/docs/rest-api/api-reference/connections/create-connection.md?service=azure_blob_storage). We are gradually rolling out these changes to all existing connections. We have improved the setup experience for our Sharepoint connector. New connections created on or after December 20, 2024, will have the following changes in the connection setup form: - Added a new configuration option, **Preview Files** to perform an intermediate test during configuration - Added support for displaying fields based on the file type - Added a new field, **Quote character**, to use an enclosing character - Reorganised fields to make the setup form more intuitive - Removed **Infer** as an option from the **File Type** field - Removed the **Enable Advanced Options** toggle - Changed the **Null Sequence** field to a toggle - For the **Delimiter character(s)** field, we now use `,` as the default value - For the **Line Separator** field, we now use `\n` as the default value For more information, see our [setup instructions](/docs/connectors/files/share-point/setup-guide.md) and [REST API configuration](/docs/rest-api/api-reference/connections/create-connection.md?service=share_point). We are gradually rolling out these changes to all existing connections. We have improved the setup experience for our Google Cloud Storage connector. New connections created on or after December 20, 2024, will have the following changes in the connector setup form: - Added a new configuration option, **Run connection test** to perform an intermediate test during configuration - Added a new configuration option, **Preview Files** to perform an intermediate test during configuration - Added support for displaying fields based on the file type - Added a new field, **Quote character**, to use an enclosing character - Reorganised fields to make the setup form more intuitive - Removed **Infer** as an option from the **File Type** field - Removed the **Enable Advanced Options** toggle - Changed the **Null Sequence** field to a toggle - For the **Delimiter character(s)** field, we now use `,` as the default value - For the **Line Separator** field, we now use `\n` as the default value For more information, see our [setup instructions](/docs/connectors/files/google-cloud-storage/setup-guide.md) and [REST API configuration](/docs/rest-api/api-reference/connections/create-connection.md?service=gcs). We are gradually rolling out these changes to all existing connections. We have updated the connection method for configuring a connector through REST API. We now use `DIRECT` and `SSH_TUNNEL` for configuration. Previously, we used `direct` and `sshTunnel`. For more information, see our [REST API configuration](/docs/rest-api/api-reference/connections/create-connection.md?service=sftp). --- ## November 2024 We have implemented a new Log Service Management API endpoint for our [REST API](/docs/developer-resources/rest-api.md). You can now leverage the new [List all logging services within account](/docs/developer-resources/rest-api/api-reference/log-service-management.md) feature. We have improved the connector setup experience and made the following changes to the connection setup form: - Added a new configuration option, **Preview Files**, to perform an intermediate test during configuration - Added support for displaying fields based on the file type - Added a new field, **Quote character**, to use an enclosing character - Reorganised fields to make the setup form more intuitive - Removed **Infer** as an option from the **File Type** field - Removed the **Enable Advanced Options** toggle - Changed the **Null Sequence** field to a toggle - For the **Delimiter character(s)** field, we now use `,` as the default value - For the **Line Separator** field, we now use `\n` as the default value For more information, see our [setup instructions](/docs/connectors/files/sftp/setup-guide.md) and [REST API configuration](/docs/rest-api/api-reference/connections/create-connection.md?service=sftp). We are gradually rolling out these changes to all existing connections. You can now manage connections you built with Connector SDK using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=statsig). This feature is available for Free, Standard, Enterprise, and Business Critical accounts. Note that you cannot create a connection using Fivetran REST API. --- ## October 2024 You can now configure the primary key used for file process and load using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=s3). You can now configure your Adyen connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=adyen). This feature is available only for Free, Standard, Enterprise, and Business Critical accounts. --- ## September 2024 We have implemented a new Destination Management API endpoint for our [REST API](/docs/developer-resources/rest-api.md). You can now leverage the new [List all destinations within an account](/docs/developer-resources/rest-api/api-reference/destinations/list-destinations.md) feature. We added a new tab where you can add, view, and rotate the previously introduced [System Keys](/docs/changelog/2024/august-2024.md#systemkeysintherestapi) in your [Fivetran dashboard](https://fivetran.com/dashboard/account/general/system-keys). To manage System Keys, you must have administrative permissions on the account. Learn more in our [System Keys management documentation](/docs/developer-resources/rest-api/api-reference/system-key.md). ![system_keys_list](changelogMedia2058525192) You can add a new System Key by uploading a JSON file with the key access rules. We then validate the file and show a summary of key permissions. ![add_system_key](changelogMedia1489614420) We have renamed our Local Processing Agent Management API to [Hybrid Deployment Agent Management API](/docs/developer-resources/rest-api/api-reference/hybrid-deployment-agent-management.md). We will stop supporting the previous paths that were applicable to the Local Processing Agent Management API in 3 months from now. You must migrate to the new API before we stop supporting the old paths. We have added a new parameter, `hybrid_deployment_agent_id`, to the [Connector Management API](/docs/developer-resources/rest-api/api-reference/connections.md) and [Destination Management API](/docs/developer-resources/rest-api/api-reference/destinations.md). The new parameter defines the Hybrid Deployment Agent ID and is a duplicate of the `local_processing_agent_id` parameter. We will remove the `local_processing_agent_id` parameter in future. We now restrict API users from triggering syncs if: - the `append_file_option` field is set to the `upsert_file_with_primary_keys` value - primary keys are not defined in the schema configuration We also restrict the following actions: - Creating a new connection in an un-paused state via API - Updating the connection's `paused` field to `false` via API request - Forcing the connection sync or [re-sync](/docs/getting-started/glossary.md#resync) via API request --- ## August 2024 We have implemented a new Connector Management API endpoint for our [REST API](/docs/developer-resources/rest-api.md). You can now leverage the new [List all connections within account](/docs/developer-resources/rest-api/api-reference/connections/list-connections.md) feature. We have implemented a new [Quickstart Transformations Management](/docs/rest-api/api-reference/qdm-transformation-management.md) resource for managing QDM transformations. You can now leverage the following new features: - [Create Quickstart Package](/docs/rest-api/api-reference/qdm-transformation-management/create-qdm-package.md) - [Retrieve Quickstart Packages](/docs/rest-api/api-reference/qdm-transformation-management/list-qdm-packages.md) - [Retrieve Quickstart Package Details](/docs/rest-api/api-reference/qdm-transformation-management/qdm-package-details.md) - [Modify Quickstart Package](/docs/rest-api/api-reference/qdm-transformation-management/update-qdm-package.md) - [Upgrade Quickstart Package version](/docs/rest-api/api-reference/qdm-transformation-management/upgrade-qdm-package.md) - [Delete Quickstart Package](/docs/rest-api/api-reference/qdm-transformation-management/delete-qdm-package.md) - [Retrieve Quickstart Package Models](/docs/rest-api/api-reference/qdm-transformation-management/list-qdm-package-models.md) - [Create Quickstart Transformation](/docs/rest-api/api-reference/qdm-transformation-management/create-qdm-transformation.md) - [Retrieve Quickstart Transformations](/docs/rest-api/api-reference/qdm-transformation-management/list-qdm-transformations.md) - [Retrieve Quickstart Transformation Details](/docs/rest-api/api-reference/qdm-transformation-management/qdm-transformation-details.md) - [Modify Quickstart Transformation](/docs/rest-api/api-reference/qdm-transformation-management/modify-qdm-transformation.md) - [Delete Quickstart Transformation](/docs/rest-api/api-reference/qdm-transformation-management/delete-qdm-transformation.md) - [Cancel Quickstart Transformation](/docs/rest-api/api-reference/qdm-transformation-management/cancel-qdm-transformation.md) - [Run Quickstart Transformation](/docs/rest-api/api-reference/qdm-transformation-management/run-qdm-transformation.md) We have implemented a new [REST API](/docs/developer-resources/rest-api.md) resource for managing System Keys. These keys are divorced from users, and therefore easier to manage and audit, especially for users with SAML. For more information, see our [System Keys reference documentation](/docs/developer-resources/rest-api/getting-started/authentication/system-keys.md). You can now leverage the following new features: - [Create a new System Key](/docs/developer-resources/rest-api/api-reference/system-key/create-system-key.md) - [List all System Keys](/docs/developer-resources/rest-api/api-reference/system-key/get-system-keys.md) - [Retrieve System Key details](/docs/developer-resources/rest-api/api-reference/system-key/get-system-key-details.md) - [Update a System Key](/docs/developer-resources/rest-api/api-reference/system-key/update-system-key.md) - [Delete a System Key](/docs/developer-resources/rest-api/api-reference/system-key/delete-system-key.md) - [Rotate a System Key](/docs/developer-resources/rest-api/api-reference/system-key/rotate-system-key.md) --- ## July 2024 We have added the [Magic Folder Mode functionality](/docs/connectors/files.md#magicfoldermode) to our SFTP connector. For connections created after July 22, 2024, you can now opt to sync files as unique tables within a schema in your destination. You can either select **Magic Folder** or **Merge Mode** as your sync strategy, in the connector setup form. For more information, see our [setup instructions](/docs/connectors/files/sftp/setup-guide.md) and [REST API configuration](/docs/rest-api/api-reference/connections/create-connection.md?service=sftp). --- ## June 2024 We have added a new field, `supports_columns_config`, to the response of our [REST API Retrieve a Connection Schema Config endpoint](/docs/developer-resources/rest-api/api-reference/connection-schema/connection-schema-config.md). The `supports_columns_config` field indicates whether the table supports column configuration. We have added the following new fields to the response for our [REST API Retrieve connector types](/docs/developer-resources/rest-api/api-reference/connections.md): - `supported_features` - `service_status_updated_at` The `data` field contains all fields returned in the response in the old format. An example of the new response format: ```json { "code": "Success", "data": { "items": [ { "id": "facebook_ads", "name": "Facebook Ads", "type": "Marketing", "connector_class": "standard", "description": "Facebook Ads provides attribute data on Facebook Ads", "icon_url": "https://fivetran.com/integrations/facebook/resources/facebook.svg", "icons": [ "https://fivetran.com/integrations/facebook/resources/facebook-logo.svg", "https://fivetran.com/integrations/facebook/resources/facebook-logo.png" ], "link_to_docs": "https://fivetran.com/docs/connectors/applications/facebook-ads", "link_to_erd": "https://fivetran.com/docs/connectors/applications/facebook-ads#schemainformation", "service_status": "general_availability", "service_status_updated_at": "2024-01-01", "supported_features": [ { "id": "CUSTOM_DATA", "notes": "" }, { "id": "CAPTURE_DELETES", "notes": "" }, { "id": "DATA_BLOCKING", "notes": "Column level" }, { "id": "COLUMN_HASHING", "notes": "" }, { "id": "RE_SYNC", "notes": "" }, { "id": "HISTORY", "notes": "" }, { "id": "API_CONFIGURABLE", "notes": "API Configuration" }, { "id": "PRIORITY_FIRST_SYNC", "notes": "All tables" }, { "id": "FIVETRAN_DATA_MODELS", "notes": "" }, { "id": "PRIVATE_NETWORKING", "notes": "" }, { "id": "AUTHORIZATION_VIA_API", "notes": "" } ] } ] } } ``` --- ## May 2024 To [Create a Private Link](/docs/developer-resources/rest-api/api-reference/private-links/create-private-link.md) using our [Private Link Management API](/docs/developer-resources/rest-api/api-reference/private-links.md), you now must specify the `service` and `region` parameter values in the request instead of `group_id`. This enables you to use a single private link for all destinations with the same service and region. To [Create a Proxy Agent](/docs/developer-resources/rest-api/api-reference/proxy-agent/create-proxy-agent.md) using our [Proxy Agent Management API](/docs/developer-resources/rest-api/api-reference/proxy-agent.md), you now must specify the `group_region` parameter value in the request instead of `group_id`. This enables you to use a single proxy agents for all connections in a specified region. We have added the following parameters in the [Connection Management API](/docs/developer-resources/rest-api/api-reference/connections.md): - `proxy_agent_id` - defines the proxy ID - `private_link_id` - defines the private link ID. - `networking_method` - defines the connection method. Possible values are as follows: - `Directly` - direct connection - `PrivateLink` - connection via private link - `ProxyAgent` - connection via proxy - `SshTunnel` - connection via SSH Tunnel. We have added the following parameters in the [Destination Management API](/docs/developer-resources/rest-api/api-reference/destinations.md): - `private_link_id` - defines the private link ID. - `networking_method` - defines the connection method. Possible values are as follows: - `Directly` - direct connection - `PrivateLink` - connection via private link - `SshTunnel` - connection via SSH Tunnel. Our [Connection Management API](/docs/developer-resources/rest-api/api-reference/connections.md) now supports a new endpoint, [`Create a Connection Schema Config`](/docs/developer-resources/rest-api/api-reference/connection-schema/pre-create-connection-schema-config.md). The endpoint allows you to configure the schema before the initial sync without reloading it. --- ## April 2024 We now support the [OAuth machine-to-machine (M2M) authentication type](https://docs.databricks.com/en/dev-tools/auth/oauth-m2m.html) to connect to the Databricks destinations hosted on AWS and Azure. You can use this authentication type only for the destinations that are _not_ connected to Fivetran using AWS PrivateLink and Azure Private Link. To support this enhancement, we have made the following changes: - Added a new drop-down menu, **Authentication Type**, to the setup form. The drop-down menu allows you to choose the authentication method you want Fivetran to use. - Added two new fields, **OAuth 2.0 Client ID** and **OAuth 2.0 Secret**, to the destination setup form. - Added two new parameters, `oauth2_client_id` and `oauth2_secret`, to the [Fivetran REST API](/docs/rest-api/api-reference/destinations/create-destination.md?service=databricks). For more information, see our [setup instructions](/docs/destinations/databricks/databricks-setup-guide.md) and [REST API documentation](/docs/rest-api/api-reference/destinations/create-destination.md?service=databricks). We are gradually rolling these changes to all existing destinations. We now sync data from the columns whose name start with a numeric character as Databricks has started supporting such column names. Previously, we did not sync any data from columns whose name started with a numeric character. To backfill the historical data for these columns, [re-sync the associated tables](/docs/core-concepts/features.md#tableresync). We are gradually rolling this change to all existing destinations. We now support syncing PGP (Pretty Good Privacy) encrypted files. We have added a new advanced configuration, **PGP Encryption Options**, to the connector setup form. For more information, see our [setup instructions](/docs/connectors/files/google-cloud-storage/setup-guide.md) and the [REST API config](/docs/rest-api/api-reference/connections/create-connection.md?service=gcs). Our [Hybrid Deployment Agent Management API](/docs/developer-resources/rest-api/api-reference/hybrid-deployment-agent-management.md) resource is now [Private Preview](/docs/core-concepts.md#releasephases). You can now leverage the following features: - [Create a Hybrid Deployment Agent](/docs/developer-resources/rest-api/api-reference/hybrid-deployment-agent-management/create-hybrid-deployment-agent.md) - [List Hybrid Deployment Agents](/docs/developer-resources/rest-api/api-reference/hybrid-deployment-agent-management/get-hybrid-deployment-agent-list.md) - [Retrieve Hybrid Deployment Agent Details](/docs/developer-resources/rest-api/api-reference/hybrid-deployment-agent-management/get-hybrid-deployment-agent.md) - [Delete a Hybrid Deployment Agent](/docs/developer-resources/rest-api/api-reference/hybrid-deployment-agent-management/delete-hybrid-deployment-agent.md) - [Regenerate authentication keys for a Hybrid Deployment Agent](/docs/developer-resources/rest-api/api-reference/hybrid-deployment-agent-management/re-auth-hybrid-deployment-agent.md) Our commercetools connector is now [generally available](/docs/getting-started/core-concepts.md#releasephases). [Read our commercetools connector documentation.](/docs/connectors/applications/commercetools.md). You can now configure your commercetools connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=commercetools). This feature is available for Free, Standard, Enterprise, and Business Critical accounts. --- ## March 2024 Our [Proxy Agent Management API](/docs/developer-resources/rest-api/api-reference/proxy-agent.md) resource is now in [beta](/docs/core-concepts.md#releasephases). You can now leverage the following features: - [Create a Proxy Agent](/docs/developer-resources/rest-api/api-reference/proxy-agent/create-proxy-agent.md) - [List all Proxy Agents](/docs/developer-resources/rest-api/api-reference/proxy-agent/get-proxy-agent.md) - [Retrieve Proxy Agent Details](/docs/developer-resources/rest-api/api-reference/proxy-agent/get-proxy-agent-details.md) - [Delete a Proxy Agent](/docs/developer-resources/rest-api/api-reference/proxy-agent/delete-proxy-agent.md) - [Returns all connections attached to the proxy agent](/docs/developer-resources/rest-api/api-reference/proxy-agent/get-proxy-agent-connections.md) - [Attach connection to the proxy agent](/docs/developer-resources/rest-api/api-reference/proxy-agent.md) - [Detach connection from the proxy agent](/docs/developer-resources/rest-api/api-reference/proxy-agent.md) We have added a new configuration option, **Primary Key used for file process and load**, to the connector setup form to support syncing files with custom primary keys. You can now select the custom primary keys during the connector configuration and use them to update or insert new rows in your destination. We process the most recently modified files to your destination. For more information, see our [setup instructions](/docs/connectors/files/google-cloud-storage.md#upsertwithcustomprimarykeys). We have added a new toggle, **Non-standard character escaping**, to the connector setup form to support the non-standard ways of escaping characters. If your CSV generator uses non-standard ways of escaping character, set the toggle to ON and in the **Character Escaping options** drop-down menu, select one of the following options: - **Custom Escape Character**: To process CSV files that use custom escape character to escape quotation marks. - **Delimited Only**: To process CSV files that don't use escape character to escape quotation marks and process with delimiter only. For more information, see our [setup instructions](/docs/connectors/files/google-cloud-storage/setup-guide.md) and [REST API config](/docs/rest-api/api-reference/connections/create-connection.md?service=gcs). We are gradually rolling out this change to all existing connections. You can now configure your Duoplane connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=duoplane). This feature is available for Free, Standard, Enterprise, and Business Critical accounts. We have renamed the API key field to Personal API token in the CircleCI [connection setup form](/docs/connectors/applications/circleci/setup-guide.md) and [API configuration parameters](/docs/rest-api/api-reference/connections/create-connection.md?service=circleci). You can now configure your Freshdesk Contact Center connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=freshdesk_contact_center). This feature is available for Free, Standard, Enterprise, and Business Critical accounts. We have added a new field, `daylight_saving_time_enabled`, for the following endpoints: - [Create a destination](/docs/developer-resources/rest-api/api-reference/destinations/create-destination.md) - [Retrieve destination details](/docs/developer-resources/rest-api/api-reference/destinations/destination-details.md) - [Modify a destination](/docs/developer-resources/rest-api/api-reference/destinations/modify-destination.md) If the field value is set to `true`, the UTC offset is shifted in accordance with the daylight saving time. You can use this option _only_ for the US region. --- ## February 2024 We now use [API v4](https://developer.concur.com/api-reference/common/lists/v4.list.html) of SAP Concur to sync the `LIST` table. Previously, we used API v3 of SAP Concur to sync the table. To ensure data integrity, we recommend that you re-sync the `LIST` table. We are gradually rolling out this improvement to all existing connections. You can now specify your custom API base URL while setting up your connector. To support this enhancement, we have made the following changes: - Added a new option, **CUSTOM**, to the **API server region** drop-down menu and a new field, **Access URL**, to the connector setup form. - Added a new parameter, `custom_url`, to the Fivetran REST API. For more information, see our [setup instructions](/docs/connectors/applications/dbt-platform/setup-guide.md) and [REST API documentation](/docs/rest-api/api-reference/connections/create-connection.md?service=dbt_cloud). We have renamed the **API Key** field to **User token** in the connector setup form. We have also modified our REST API configuration parameters and replaced the `api_key` parameter with `user_token`. For more information, see our [setup instructions](/docs/connectors/applications/sonarqube/setup-guide.md) and [REST API config](/docs/rest-api/api-reference/connections/create-connection.md?service=sonarqube). --- ## January 2024 Our [HVR Registration API](/docs/developer-resources/rest-api/api-reference/hvr-register-hub.md) resource is now in [beta](/docs/core-concepts.md#releasephases). You can now leverage the [Register a new hub](/docs/developer-resources/rest-api/api-reference/hvr-register-hub/hvr-register-hub.md) feature. We have added a new toggle, **Non-standard character escaping?**, to the connector setup form to support the non-standard ways of escaping characters. If your CSV generator uses non-standard ways of escaping characters, set the toggle to ON and in the **Character Escaping options** drop-down menu, select one of the following options: - **Custom Escape Character**: To process CSV files that use custom escape characters to escape quotation marks. - **Delimited Only**: To process CSV files that don't use escape characters to escape quotation marks and process with delimiter only. For more information, see our [setup instructions](/docs/connectors/files/amazon-s3/setup-guide.md) and [REST API config](/docs/rest-api/api-reference/connections/create-connection.md?service=s3). We are gradually rolling out this change to all existing connections. We have added a new configuration option, **Primary Key used for file process and load**, in the connector setup form to support syncing files with custom primary keys. You can now select the custom primary keys during the connector configuration and use them to update or insert new rows in your destination. We process the most recently modified files to your destination. For more information see our [setup instructions](/docs/connectors/files/amazon-s3.md#upsertwithcustomprimarykeys). We no longer use your Integral Ad Science client ID and client secret to access and sync your data. To support this enhancement, we have made the following changes: - Removed the **Client ID** and **Client Secret** fields from the connector setup form. - Removed the `client_id` and `client_secret` parameters from the REST API configuration. For more information, see our [setup instructions](/docs/connectors/applications/integral-ad-science/setup-guide.md) and [REST API config](/docs/rest-api/api-reference/connections/create-connection.md?service=integral_ad_science). We now use both project access tokens and account access tokens to access and sync your Rollbar data. To facilitate this enhancement, we have made the following changes: - Added a new field, **Project access token**, and renamed the **Access Token** field to **Account access token** in the connector setup form - Added a new parameter, `project_access_token`, and renamed the `access_token` parameter to `account_access_token` in the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=rollbar) For more information, see our [setup guide](/docs/connectors/applications/rollbar/setup-guide.md) and [API connection configuration documentation](/docs/rest-api/api-reference/connections/create-connection.md?service=rollbar). You can now configure your Buildkite connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=buildkite). This feature is available for Free, Standard, Enterprise, and Business Critical accounts. You can now configure your Campaign Monitor connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=campaignmonitor). This feature is available for Free, Standard, Enterprise, and Business Critical accounts. You can now configure your ChartMogul connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=chartmogul). This feature is available for Free, Standard, Enterprise, and Business Critical accounts. You can now configure your Chorus connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=chorusai). This feature is available for Free, Standard, Enterprise, and Business Critical accounts. You can now configure your Close connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=close). This feature is available for Free, Standard, Enterprise, and Business Critical accounts. You can now configure your Freightview connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=freightview). This feature is available for Free, Standard, Enterprise, and Business Critical accounts. You can now configure your Lob connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=lob). This feature is available for Free, Standard, Enterprise, and Business Critical accounts. You can now configure your Monday.com connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=monday). This feature is available for Free, Standard, Enterprise, and Business Critical accounts. You can now configure your Rarible connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=rarible). This feature is available for Free, Standard, Enterprise, and Business Critical accounts. You can now configure your Statsig connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=statsig). This feature is available for Free, Standard, Enterprise, and Business Critical accounts. You can now configure your Ramp connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=ramp). This feature is available for Free, Standard, Enterprise, and Business Critical accounts. --- ## December 2023 We have implemented new Connector Management API endpoints for our [REST API](/docs/developer-resources/rest-api.md). You can now leverage the following new features: - [Delete Blocked Column](/docs/developer-resources/rest-api/api-reference/connection-schema/delete-column-connection-config.md) - [Delete Blocked Columns](/docs/developer-resources/rest-api/api-reference/connection-schema/delete-multiple-columns-connection-config.md) We now display the `created_at` field for each user in the response for the following endpoints: - [Add a user to a team](/docs/developer-resources/rest-api/api-reference/teams/add-user-to-team.md) - [List all user memberships](/docs/developer-resources/rest-api/api-reference/teams/list-users-in-team.md) - [Modify a user membership](/docs/developer-resources/rest-api/api-reference/teams/update-user-membership.md) - [Retrieve user membership](/docs/developer-resources/rest-api/api-reference/teams/get-user-in-team.md) We now return `group_id`, `role`, and `created_at` for the [Update group membership](/docs/developer-resources/rest-api/api-reference/teams/update-team-membership-in-group.md) endpoint. We now return `connector_id`, `role`, and `created_at` for the [Update connection membership](/docs/developer-resources/rest-api/api-reference/teams/update-team-membership-in-connection.md) endpoint. --- ## November 2023 You can now specify custom payloads as key-value pairs when you configure the Azure Functions connector using our [REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=azure_function). Our [Log Service Management API](/docs/developer-resources/rest-api/api-reference/log-service-management.md) resource is now [generally available](/docs/core-concepts.md#releasephases). You can now leverage the following features: - [Create a Log Service](/docs/developer-resources/rest-api/api-reference/log-service-management/add-log-service.md) - [Retrieve Log Service Details](/docs/developer-resources/rest-api/api-reference/log-service-management/get-log-service-details.md) - [Update a Log Service](/docs/developer-resources/rest-api/api-reference/log-service-management/update-log-service.md) - [Delete a Log Service](/docs/developer-resources/rest-api/api-reference/log-service-management/delete-log-service.md) - [Run Log Service Setup Tests](/docs/developer-resources/rest-api/api-reference/log-service-management/run-setup-tests-log-service.md) You can now configure your OneLake destination using the [Fivetran REST API](/docs/rest-api/api-reference/destinations/create-destination.md?service=onelake). --- ## October 2023 We no longer support the PLAINTEXT security protocol. We support only SASL. In the destination setup form, we have removed the **Security Protocol** drop-down menu. In the [REST API configuration](/docs/rest-api/api-reference/destinations/create-destination.md?service=confluent_cloud_wh), we no longer support the `PLAINTEXT` value for the `security_protocol` parameter. We have transferred pre-built reports from the connector setup form to the Schema tab of your Fivetran dashboard. Pre-built reports are now included by default and are treated as metadata tables, which means the only configurable option for them is select or deselect. This change is applicable to all new connections created after October 13, 2023. You can now use the Connector Management API to modify pre-built reports in the same way as metadata tables. To do so, submit API requests to the [Update a connection schema config](/docs/developer-resources/rest-api/api-reference/connection-schema/modify-connection-schema-config.md) endpoint. You can now configure the API usage limit of the Kustomer connector using our REST API. Previously, the default API usage limit was 90%. For more information, see our [Kustomer API Configuration documentation](/docs/rest-api/api-reference/connections/create-connection.md?service=kustomer). --- ## September 2023 We have implemented new Group Management API endpoints for our [REST API](/docs/developer-resources/rest-api.md). You can now leverage the following new features: - [Retrieve group public SSH key](/docs/developer-resources/rest-api/api-reference/groups/group-ssh-public-key.md) - [Retrieve group service account](/docs/developer-resources/rest-api/api-reference/groups/group-service-account.md) You can now configure your Slack connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=slack). This feature is available only for Free, Standard, Enterprise, and Business Critical accounts. You can now configure your Azure Data Lake Storage (ADLS) destination using the [Fivetran REST API](/docs/rest-api/api-reference/destinations/create-destination.md?service=adls). You can now specify secrets as key-pair values when you configure the Azure Functions connector using our [REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=azure_function). You can now specify secrets as key-pair values when you configure the Google Cloud Functions connector using our [REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=google_cloud_function). --- ## August 2023 You can now configure your Chargebee Product Catalog 1.0 connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=chargebee_product_catalog_1). This feature is available only for Free, Standard, Enterprise, and Business Critical accounts. We now validate that the `external_id` value that you specify when creating the Amazon S3 connector using the REST API is the same as your Fivetran account's `group_id`. Make sure to choose any of the `group_id` from your Fivetran account as the `external_id` parameter value. To find the `group_id`, use the [List All Groups endpoint](/docs/developer-resources/rest-api/api-reference/groups/list-all-groups.md). You can now configure your Chargebee Product Catalog 2.0 connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=chargebee_product_catalog_2). This feature is available only for Free, Standard, Enterprise, and Business Critical accounts. You can now configure your Aircall connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=aircall). This feature is available only for the Free, Standard, Enterprise, and Business Critical accounts. [Fivetran provider for Terraform](https://registry.terraform.io/providers/fivetran/fivetran/1.0.0) is now [generally available](/docs/core-concepts.md#releasephases). - For the [Transformations for dbt Core Management API](/docs/rest-api/api-reference/dbt-transformation-management.md), we added a new field, `environment_vars`. You can now manage the list of environment variables defined as key-value pairs. - The `enabled` field in the [Log Service Management API](/docs/developer-resources/rest-api/api-reference/log-service-management.md)'s [Create a Log Service](/docs/developer-resources/rest-api/api-reference/log-service-management/add-log-service.md) method now has the `true` value by default. - We added a new field, `connector_class`, in the [Retrieve connector types](#retrieveconnectortypes) and [Retrieve connector type details](#retrieveconnectortypedetails) methods. This field contains the connector category (`standard` or `lite`). Learn more about connector categories in our [Differences between Standard and Lite connectors documentation](/docs/connectors/applications/lite-connectors.md#differencesbetweenstandardandliteconnectors). Our [Log Service Management API](/docs/developer-resources/rest-api/api-reference/log-service-management.md) resource is now in [beta](/docs/core-concepts.md#releasephases). You can now leverage the following features: - [Create a Log Service](/docs/developer-resources/rest-api/api-reference/log-service-management/add-log-service.md) - [Retrieve Log Service Details](/docs/developer-resources/rest-api/api-reference/log-service-management/get-log-service-details.md) - [Update a Log Service](/docs/developer-resources/rest-api/api-reference/log-service-management/update-log-service.md) - [Delete a Log Service](/docs/developer-resources/rest-api/api-reference/log-service-management/delete-log-service.md) - [Run Log Service Setup Tests](/docs/developer-resources/rest-api/api-reference/log-service-management/run-setup-tests-log-service.md) We have changed the Salesfore connector's API response to the [Retrieve Connection Details](/docs/developer-resources/rest-api/api-reference/connections/connection-details.md) API request to return the `connecting_user_email`, `organization_id`, and `username` fields in the `config` section of the response instead of the `source_sync_details` section. Our [dbt Transformations Management API](/docs/rest-api/api-reference/dbt-transformation-management.md) is now [Beta](/docs/core-concepts.md#releasephases). You can now leverage the following features: - [Create dbt Project](/docs/rest-api/api-reference/dbt-transformation-management/create-dbt-project.md) - [Retrieve dbt Projects](/docs/rest-api/api-reference/dbt-transformation-management/list-dbt-projects.md) - [Retrieve dbt Project details](/docs/rest-api/api-reference/dbt-transformation-management/dbt-project-details.md) - [Test dbt Project](/docs/rest-api/api-reference/dbt-transformation-management/test-dbt-project.md) - [Retrieve dbt Project Models](/docs/rest-api/api-reference/dbt-transformation-management/list-dbt-project-models.md) - [Retrieve dbt Project Model details](/docs/rest-api/api-reference/dbt-transformation-management/dbt-model-details.md) - [Create dbt Transformation](/docs/rest-api/api-reference/dbt-transformation-management/create-dbt-transformation.md) - [Retrieve dbt Transformations](/docs/rest-api/api-reference/dbt-transformation-management/list-dbt-project-transformations.md) - [Retrieve dbt Transformation details](/docs/rest-api/api-reference/dbt-transformation-management/dbt-transformation-details.md) - [Modify dbt Transformation](/docs/rest-api/api-reference/dbt-transformation-management/modify-dbt-transformation.md) - [Delete dbt Transformation](/docs/rest-api/api-reference/dbt-transformation-management/delete-dbt-transformation.md) - [Cancel dbt Transformation](/docs/rest-api/api-reference/dbt-transformation-management/cancel-dbt-transformation.md) - [Run dbt Transformation](/docs/rest-api/api-reference/dbt-transformation-management/run-dbt-transformation.md) You can now specify the events and custom events that you want to sync when you configure the Iterable connector using our [REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=iterable). Our [Webhook Management API](/docs/developer-resources/rest-api/api-reference/webhooks.md) is now [generally available](/docs/core-concepts.md#releasephases). You can now configure your Survicate connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=survicate). This feature is available only for the Free, Standard, Enterprise, and Business Critical accounts. We have added the [Log Service Management API](/docs/developer-resources/rest-api/api-reference/log-service-management.md) and [Transformations for dbt Core Management API](/docs/rest-api/api-reference/dbt-transformation-management.md) to our [Postman collection](/docs/developer-resources/rest-api/api-tools.md#fivetranrestapipostmancollection). You can now configure your Drift connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=drift). This feature is available only for Free, Standard, Enterprise, and Business Critical accounts. You can now configure your Subscript connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=subscript). This feature is available only for Free, Standard, Enterprise, and Business Critical accounts. You can now configure your Ironclad connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=ironclad). This feature is available only for Free, Standard, Enterprise, and Business Critical accounts. You can now configure your Sonarqube connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=sonarqube). This feature is available only for Free, Standard, Enterprise, and Business Critical accounts. You can now configure your GoCardless connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=gocardless). This feature is available only for Free, Standard, Enterprise, and Business Critical accounts. --- ## July 2023 We have updated the Adobe Analytics connector's REST API configuration parameters to support aggregating data by week. Learn more in our [Adobe Analytics Connection Config documentation](/docs/rest-api/api-reference/connections/create-connection.md?service=adobe_analytics). You can now opt to sync Salesforce formula fields using our REST API. For more information, see our [API Configuration documentation](/docs/rest-api/api-reference/connections/create-connection.md?service=salesforce). You can now configure your Split connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=splitio). This feature is available only for Free, Standard, Enterprise, and Business Critical accounts. You can now configure your Assembled connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=assembled). This feature is available only for Free, Standard, Enterprise, and Business Critical accounts. We have made the `active` field optional in the [Create Account Webhook](/docs/developer-resources/rest-api/api-reference/webhooks/create-account-webhook.md) and [Create Group Webhook](/docs/developer-resources/rest-api/api-reference/webhooks/create-group-webhook.md) endpoint requests. By default, the field value is set to `true`. We have implemented two new endpoints in our [REST API](/docs/developer-resources/rest-api.md), [Retrieve Function Connection State](/docs/developer-resources/rest-api/api-reference/connections/connection-state.md) and [Update Function Connection State](/docs/developer-resources/rest-api/api-reference/connections/modify-connection-state.md) that allow you to get and update the state of [Functions](/docs/connectors/functions.md) connections, respectively. This feature is in [beta](/docs/core-concepts.md#releasephases). You can now configure your Open Exchange Rates connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=open_exchange_rates). This feature is available only for Free, Standard, Enterprise, and Business Critical accounts. We have changed the response code for the [Delete Webhook endpoint](/docs/developer-resources/rest-api/api-reference/webhooks/delete-webhook.md) from HTTP 204 to HTTP 200. We now support the following new [webhook events](/docs/developer-resources/rest-api/api-reference/webhooks.md): - connection_successful - connection_failure - create_connector - pause_connector - resume_connector - edit_connector - delete_connector - force_update_connector - resync_connector - resync_table --- ## June 2023 You can now configure your Calendly connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=calendly). This feature is available only for Free, Standard, Enterprise, and Business Critical accounts. We now support the `edit_connector` webhook event for manual or automatic connector status changes. Namely, this webhook event is raised for `setup-state` and `schema-status` property changes, which are reflected in `editType`. The following `edit_connector` webhook events are shown below as being relevant for the [How to Set Up a Schema Before the Initial Sync](/docs/developer-resources/rest-api/tutorials/schema-status.md) use case. ```json { event: 'edit_connector', // ... editType: 'UPDATE_SETUP_STATE', properties: { setupState: 'connected' }, oldProperties: { setupState: 'incomplete' } } { event: 'edit_connector', // ... editType: 'UPDATE_SETUP_STATE', properties: { setupState: 'broken' }, oldProperties: { setupState: 'connected' } } { event: 'edit_connector', // ... editType: 'UPDATE_SCHEMA_STATUS', properties: { schemaStatus: 'blocked_on_capture' }, oldProperties: { schemaStatus: 'ready' } } { event: 'edit_connector', // ... editType: 'UPDATE_SCHEMA_STATUS', properties: { schemaStatus: 'blocked_on_customer' }, oldProperties: { schemaStatus: 'blocked_on_capture' } } { event: 'edit_connector', // ... editType: 'UPDATE_SCHEMA_STATUS', properties: { schemaStatus: 'ready' }, oldProperties: { schemaStatus: 'blocked_on_customer' } } ``` You can now configure your BigCommerce connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=big_commerce). This feature is available only for Free, Standard, Enterprise, and Business Critical accounts. Now, when you configure the AWS Lambda connector using our [REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=aws_lambda), you can: - Connect using AWS PrivateLink if your Lambda function and destination are in the same AWS Region. This feature is available only on the [Business Critical plan](https://www.fivetran.com/pricing/features). - Select your sync method. You can opt to sync directly or through an S3 bucket. You can now configure the API usage limit of the Qualtrics connector using our REST API. For more information, see our [Qualtrics API Configuration](/docs/rest-api/api-reference/connections/create-connection.md?service=qualtrics) documentation. --- ## May 2023 Now, we deactivate a [webhook](/docs/developer-resources/rest-api/api-reference/webhooks.md) if it consistently fails for more than three days and only responds with non-2xx codes. To [activate](#active) the webhook, ensure that the setup is correct by [retrieving the webhook details](#retrievewebhookdetails) and [updating](#updatewebhook) them with corrected information along with passing `"active": true` in the request. Alternatively, you can create a new webhook. You can now configure your S3 Data Lake destination using the [Fivetran REST API](/docs/rest-api/api-reference/destinations/create-destination.md?service=new_s3_datalake). You can now configure your Confluent Cloud destination using the [Fivetran REST API](/docs/rest-api/api-reference/destinations/create-destination.md?service=confluent_cloud_wh). --- ## April 2023 You can now configure your Lattice connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=lattice). This feature is available only for Free, Standard, Enterprise, and Business Critical accounts. You can now configure your Fountain connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=fountain). This feature is available only for Free, Standard, Enterprise, and Business Critical accounts. --- ## March 2023 For the `service` parameter in the API request for our [Databricks destination](/docs/rest-api/api-reference/destinations/create-destination.md?service=databricks), you now need to specify `databricks` as a value. The old values `databricks_aws` and `databricks_azure` are still valid. You can now configure your Salesforce Commerce Cloud connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=salesforce_commerce_cloud). This feature is available only for Free, Standard, Enterprise, and Business Critical accounts. We have added the following new fields to the response for our [REST API Webhook endpoints](/docs/developer-resources/rest-api/api-reference/webhooks.md): - `code` - `message` - `data` The `data` field contains all fields returned in the response in the old format. An example of the previous response format: ```json { "id": "program_quoth", "type": "account", "url": "https://your-host.your-domain/webhook", "events": [ "sync_start", "sync_end" ], "active": true, "secret": "******", "created_at": "2022-04-29T09:41:08.583Z", "created_by": "_airworthy" } ``` An example of the new response format: ```json { "code": "Success", "message": "Account webhook has been created", "data": { "id": "program_quoth", "type": "account", "url": "https://your-host.your-domain/webhook", "events": [ "sync_start", "sync_end" ], "active": true, "secret": "******", "created_at": "2022-04-29T09:41:08.583Z", "created_by": "_airworthy" } } ``` Fivetran now takes into account all connections specifics and returns the correct `name_in_destination` field value for schemas in the response for the following REST API endpoints: - [Retrieve a connection schema config](/docs/developer-resources/rest-api/api-reference/connection-schema/connection-schema-config.md) - [Reload a connection schema config](/docs/developer-resources/rest-api/api-reference/connection-schema/reload-connection-schema-config.md) - [Update a connection schema config](/docs/developer-resources/rest-api/api-reference/connection-schema/modify-connection-schema-config.md) - [Update a connection database schema config](/docs/developer-resources/rest-api/api-reference/connection-schema/modify-connection-database-schema-config.md) - [Update a connection table config](/docs/developer-resources/rest-api/api-reference/connection-schema/modify-connection-table-config.md) - [Update a connection column config](/docs/developer-resources/rest-api/api-reference/connection-schema/modify-connection-column-config.md) Previously, we returned the schema name only with the [generic naming rules](/docs/getting-started/core-concepts.md#schema-naming-rule-set) applied. --- ## February 2023 You can now configure your High-Volume Agent Db2 for i connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=db2i_hva). This feature is available only for Free, Standard, Enterprise, and Business Critical accounts. You can now configure your Crossbeam connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=crossbeam). This feature is available only for Free, Standard, Enterprise, and Business Critical accounts. You can now configure your Gong connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=gongio). This feature is available only for Free, Standard, Enterprise, and Business Critical accounts. --- ## January 2023 You can now configure your Okta connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=okta). This feature is available only for Free, Standard, Enterprise, and Business Critical accounts. You can now generate [scoped API keys](/docs/developer-resources/rest-api/getting-started/authentication.md#scopedapikey) to use with our [REST API](/docs/rest-api.md). --- ## December 2022 You can now configure your WooCommerce connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=woocommerce). This feature is available only for Free, Standard, Enterprise, and Business Critical accounts. --- ## November 2022 You can now specify secrets as key-pair values when you configure the Lambda connector using our [REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=aws_lambda). In the LinkedIn Ad Analytics [REST API configuration](/docs/rest-api/api-reference/connections/create-connection.md?service=linkedin_ads), we have removed the 90-day option from the `postClickAttributionWindowSize` and `viewThroughAttributionWindowSize` fields because data older than 30 days cannot be updated. You can now configure your Azure Service Bus connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=azure_service_bus). The feature is available only for Free, Standard, Enterprise, and Business Critical accounts. Now, you can configure the API usage limit of the Zendesk Support connector using our REST API. Previously, the default API usage limit was 90%. For more information, see our [Zendesk Support API Configuration](/docs/rest-api/api-reference/connections/create-connection.md?service=zendesk) documentation. You can now configure your ActiveCampaign connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=activecampaign). This feature is available only for Free, Standard, Enterprise, and Business Critical accounts. --- ## October 2022 We have added the `schema_status` parameter to our [Update a connection endpoint](/docs/developer-resources/rest-api/api-reference/connections/modify-connection.md). You can use it to capture the connection schema before the initial sync. For more information, see our [documentation](/docs/developer-resources/rest-api/tutorials/schema-status.md). --- ## September 2022 We have extended [packed mode](/docs/connectors/databases/mongodb.md#packmode) support to our [REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=mongo). You can now select the sync mode for your database tables and also specify the tables you want to sync using packed mode. We have extended [packed mode](/docs/connectors/databases/dynamodb.md#syncmodeoptions) support to our [REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=dynamodb). You can now select the sync mode for your database tables and also specify the tables you want to sync using packed mode. --- ## August 2022 We have added a new [check](/docs/developer-resources/rest-api/api-reference/webhooks.md) that we perform during the [webhook](/docs/developer-resources/rest-api/api-reference/webhooks.md) creation or activation. The endpoint specified in the payload should exist and return a successful HTTP code. Otherwise, we will return an `HTTP 400 Bad Request` error. We have added a new `icons` field to the [Retrieve source metadata](/docs/developer-resources/rest-api/api-reference/connector-metadata/metadata-connectors.md) and [Retrieve connection configuration metadata](/docs/developer-resources/rest-api/api-reference/connector-metadata/metadata-connector-config.md) endpoint responses. This field contains a list of additional icon URLs in different formats (for example, .svg or .png) for the connector. We have changed the retry algorithm for sending webhooks. We now use an exponential backoff strategy - we wait 6 minutes before the first retry, 21 minutes before the second retry, and so on. Learn more in our [Retries documentation](/docs/developer-resources/rest-api/api-reference/webhooks.md). --- ## July 2022 You can now configure your OneDrive connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=one_drive). This feature is available only for Free, Standard, Enterprise, and Business Critical accounts. We have expanded the [Create a connection](/docs/developer-resources/rest-api/api-reference/connections/create-connection.md) and [Update a connection](/docs/developer-resources/rest-api/api-reference/connections/modify-connection.md) endpoints of our [REST API](/docs/developer-resources/rest-api/getting-started.md). Now you can authorize the [Intercom](/docs/rest-api/api-reference/connections/create-connection.md?service=intercom) connector by adding the `auth` section to payloads. We have added two new optional parameters, `is_account_level_connector` and `group`, to the [Fivetran Platform Connector REST API Request](/docs/rest-api/api-reference/connections/create-connection.md?service=fivetran_log). You can now opt to retrieve account-level logs. We have implemented email notification that informs you about webhook event sending failure. To turn it on, go to [Account](https://fivetran.com/dashboard/notifications/account) notifications page and change the `Receive an email when webhook events failed to be sent` value. We have added the [Webhook management endpoints](/docs/developer-resources/rest-api/api-reference/webhooks.md) to our [Postman collection](/docs/developer-resources/rest-api/api-tools.md#fivetranrestapipostmancollection). --- ## June 2022 In the `sync mode` parameter of the [Google Campaign Manager 360 API configuration](/docs/rest-api/api-reference/connections/create-connection.md?service=double_click_campaign_manager), we replaced the following: - `AllAccounts` value with `ALL_PROFILES` - `SpecificAccounts` value with `SPECIFIC_PROFILES` We have updated the Adobe Analytics connector's REST API configuration parameters to support separate configuration for each table. Learn more in our [Adobe Analytics Connection Config documentation](/docs/rest-api/api-reference/connections/create-connection.md?service=adobe_analytics). --- ## May 2022 We have implemented a new API endpoint for our [REST API](/docs/developer-resources/rest-api.md), [Re-sync Connection Data (Historical Sync)](/docs/developer-resources/rest-api/api-reference/connections/resync-connection.md), that allows you to trigger a full historical sync of a connector or multiple schema tables within a connector. We have updated the [Sync Connection Data](/docs/developer-resources/rest-api/api-reference/connections/sync-connection.md) endpoint with a new path, `sync`. We also added a new payload parameter, `force`, that allows you to force a sync, even if a sync is already in progress. --- ## April 2022 We have implemented a new resource, [Webhook Management](/docs/developer-resources/rest-api/api-reference/webhooks.md), for our [REST API](/docs/developer-resources/rest-api.md). This feature is in [beta](/docs/core-concepts.md#releasephases). You can now leverage the following new features: - [Create account webhook](/docs/developer-resources/rest-api/api-reference/webhooks/create-account-webhook.md) - [Create group webhook](/docs/developer-resources/rest-api/api-reference/webhooks/create-group-webhook.md) - [Retrieve webhook details](/docs/developer-resources/rest-api/api-reference/webhooks/webhook-details.md) - [Update webhook](/docs/developer-resources/rest-api/api-reference/webhooks/modify-webhook.md) - [Delete webhook](/docs/developer-resources/rest-api/api-reference/webhooks/delete-webhook.md) - [Retrieve the list of webhooks](/docs/developer-resources/rest-api/api-reference/webhooks/list-all-webhooks.md) - [Test webhook](/docs/developer-resources/rest-api/api-reference/webhooks/test-webhook.md) We have implemented the following new API endpoints for our [REST API](/docs/developer-resources/rest-api.md): - New resources: [Team Management](/docs/developer-resources/rest-api/api-reference/teams.md) `Private Preview` - New endpoints in User Management: [Connector memberships](/docs/developer-resources/rest-api/api-reference/users/get-user-memberships-in-connections.md) `Private Preview` We have expanded the [Create a connection](/docs/developer-resources/rest-api/api-reference/connections/create-connection.md) and [Update a connection](/docs/developer-resources/rest-api/api-reference/connections/modify-connection.md) endpoints of our REST API. Now you can authorize the [Pinterest Ads](/docs/rest-api/api-reference/connections/create-connection.md?service=pinterest_ads) connection by adding the `auth` section to payloads. We have expanded the [Create a connection](/docs/developer-resources/rest-api/api-reference/connections/create-connection.md) and [Update a connection](/docs/developer-resources/rest-api/api-reference/connections/modify-connection.md) endpoints of our REST API. Now you can authorize the [Twitter Organic](/docs/rest-api/api-reference/connections/create-connection.md?service=twitter) connector by adding the `auth` section to payloads. We have expanded the [Create a connection](/docs/developer-resources/rest-api/api-reference/connections/create-connection.md) and [Update a connection](/docs/developer-resources/rest-api/api-reference/connections/modify-connection.md) endpoints of our [REST API](/docs/developer-resources/rest-api/getting-started.md). Now you can authorize the [Google Search Console](/docs/rest-api/api-reference/connections/create-connection.md?service=google_search_console) connector by adding the `auth` section to payloads. We have expanded the [Create a connection](/docs/developer-resources/rest-api/api-reference/connections/create-connection.md) and [Update a connection](/docs/developer-resources/rest-api/api-reference/connections/modify-connection.md) endpoints of our REST API. Now you can authorize the [YouTube Analytics](/docs/rest-api/api-reference/connections/create-connection.md?service=youtube_analytics) connector by adding the `auth` section to payloads. --- ## March 2022 We have expanded the public API endpoints [Create a connection](/docs/developer-resources/rest-api/api-reference/connections/create-connection.md) and [Update a connection](/docs/developer-resources/rest-api/api-reference/connections/modify-connection.md). Now you can authorize the [Instagram Business](/docs/rest-api/api-reference/connections/create-connection.md?service=instagram_business) connector by adding the `auth` section to payloads. We have expanded the public API endpoints [Create a connection](/docs/developer-resources/rest-api/api-reference/connections/create-connection.md) and [Update a connection](/docs/developer-resources/rest-api/api-reference/connections/modify-connection.md). Now you can authorize the [Zoho CRM](/docs/rest-api/api-reference/connections/create-connection.md?service=zoho_crm) connection by adding the `auth` section to payloads. We've updated the REST API config format for the Google Ads connector. See the [Google Ads configuration section in our REST API documentation](/docs/rest-api/api-reference/connections/create-connection.md?service=google_ads) for details. --- ## February 2022 We have changed the [Add a User to a Group](/docs/developer-resources/rest-api/api-reference/groups/add-user-to-group.md) API response message to more accurately reflect the action performed. Before: ```json { "code": "Success", "message": "User has been invited to the group" } ``` Now: ```json { "code": "Success", "message": "User has been added to the group" } ``` We have updated the Adobe Analytics connector's REST API configuration parameters to support aggregating data by month, quarter, and year. Learn more in our [Adobe Analytics Connection Config documentation](/docs/rest-api/api-reference/connections/create-connection.md?service=adobe_analytics). We have added the following new regions: - `AWS_AP_SOUTHEAST_2` - `AWS_EU_CENTRAL_1` - `AWS_EU_WEST_1` - `AWS_EU_WEST_2` - `AWS_US_EAST_1` - `AWS_US_EAST_2` - `AWS_US_WEST_2` - `AZURE_AUSTRALIAEAST` - `AZURE_EASTUS2` - `GCP_ASIA_SOUTH1` - `GCP_ASIA_SOUTHEAST1` - `GCP_AUSTRALIA_SOUTHEAST1` - `GCP_EUROPE_WEST2` - `GCP_EUROPE_WEST3` - `GCP_NORTHAMERICA_NORTHEAST1` - `GCP_US_EAST4` - `GCP_US_WEST1` We have deprecated the following regions: - `APAC` - `CANADA` - `EU` - `SINGAPORE` - `UK` - `US` --- ## January 2022 We have implemented the following new API endpoints for our [REST API](/docs/developer-resources/rest-api.md): New resources: [Role Management](/docs/developer-resources/rest-api/api-reference/roles.md) `Beta` New endpoints in User Management: - [Group memberships](/docs/developer-resources/rest-api/api-reference/users/get-user-membership-in-group.md) `Beta` - [Delete user role in account](/docs/developer-resources/rest-api/api-reference/users/delete-user-membership-in-account.md) --- ## December 2021 We have removed the **Show** button in the API config section on the Security tab of your [Account Management page](/docs/developer-resources/rest-api/getting-started.md). Click the **Generate** button to view your API key and secret. Click **Generate new secret** to generate a new API secret and replace the existing secret. ![api_config_improvements](changelogMedia525003641) We now use `connector-types` instead of `connectors` in the paths for the following metadata endpoints: - [Retrieve source metadata](/docs/developer-resources/rest-api/api-reference/connector-metadata/metadata-connectors.md) - the new path format is as follows: https://api.fivetran.com/v1/metadata/connector-types - [Retrieve connection config metadata](/docs/developer-resources/rest-api/api-reference/connector-metadata/metadata-connector-config.md) - the new path format is as follows: https://api.fivetran.com/v1/metadata/connector-types/{connector_type} We support the old path format for backward compatibility. [The sunset date](/docs/core-concepts.md#releasephases) for the old path format is April 1, 2022. --- ## November 2021 You can now use a custom `external_id` parameter when you create a new Amazon S3 connector with the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=s3). > **Note:** Connections created in the Fivetran dashboard do not support custom `external_id` values, so they use the connector's `group_id` by default instead. --- ## October 2021 You can now configure your Google Drive connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=google_drive). This feature is available only for Standard, Enterprise, and Business Critical accounts. For improved security, we will remove the **Show** button in the API config section on the Security tab of your [Account Management page](/docs/developer-resources/rest-api/getting-started.md). The API key and secret are essentially credentials that allow you to access your account using the API. Never share your API key or secret with anyone. We now return the `connector_id` field in the Connect Card token endpoint response. For more information, see our [Connect Card documentation](/docs/developer-resources/rest-api/getting-started/connect-card.md). You can now configure your Box connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=box). This feature is available only for Standard, Enterprise, and Business Critical accounts. --- ## September 2021 We have implemented a new API endpoint for our [REST API](/docs/developer-resources/rest-api.md), [Retrieve connection configuration metadata](/docs/developer-resources/rest-api/api-reference/connector-metadata/metadata-connector-config.md). For accounts created after September 9, 2021, we return the connector configuration response in the V2 format by default. See our [Retrieve Connection Details endpoint documentation](/docs/developer-resources/rest-api/api-reference/connections/connection-details.md) for details. You can now re-sync data for multiple tables using the [Re-sync Connection Table Data endpoint](/docs/developer-resources/rest-api/api-reference/connection-schema/resync-tables.md). --- ## August 2021 We have added validation for the `schema` and `table` path parameters for the [Re-sync Connection Table Data endpoint](/docs/developer-resources/rest-api/api-reference/connection-schema/resync-tables.md). For a request to succeed, you need to specify its parameters correctly. When you call this endpoint with an incorrect `schema` value, you receive the following error: ```terraform HTTP 404 "message" : "Cannot find entity 'Schema' with id ''." ``` > **Note:** Your previously successful request may fail with the error, indicating that you have been using the wrong `schema` value. You can find the name of your database schema and table on the Schema tab of the connector details page. > **Note:** Make sure you don't use the connector schema name instead of the database schema name. See our [Re-sync Connection Table Data endpoint documentation](/docs/developer-resources/rest-api/api-reference/connection-schema/resync-tables.md) for details. --- ## July 2021 We now display the `role` field for each user in the response for the following endpoints: - [Retrieve user details](/docs/developer-resources/rest-api/api-reference/users/user-details.md) - [Invite a user](/docs/developer-resources/rest-api/api-reference/users/create-user.md) - [Update a user](/docs/developer-resources/rest-api/api-reference/users/modify-user.md) - [List all users within a group](/docs/developer-resources/rest-api/api-reference/groups/list-all-users-in-group.md) You can now configure your Sage Intacct connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=sage_intacct). This feature is available only for Standard and Enterprise accounts. We have changed the data type of the `picture` field defining the user avatar to STRING. Now, we support both image URL (for example, `http://mycompany.com/avatars/john_white.png`) and Base64 data URI (for example, `data:image/png;base64,aHR0cDovL215Y29tcGFueS5jb20vYXZhdGFycy9qb2huX3doaXRlLnBuZw==`) values for this field. See our [User Management endpoint documentation](/docs/developer-resources/rest-api/api-reference/users.md). You can now configure your SAP Concur connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=concur). This feature is only available for Standard and Enterprise accounts. We have expanded the current public API endpoints [Create a connection](/docs/developer-resources/rest-api/api-reference/connections/create-connection.md) and [Update a connection](/docs/developer-resources/rest-api/api-reference/connections/modify-connection.md). Now, you can create or modify the connector that will be paused after the trial period by specifying the `pause_after_trial` request parameter. --- ## June 2021 We have expanded the [Create a connection](/docs/developer-resources/rest-api/api-reference/connections/create-connection.md) endpoint. Now, you can: - set the frequency of your syncs using the `sync_frequency` request parameter - set the start time of your daily syncs using the `daily_sync_time` request parameter if you set the `sync_frequency` parameter to `1440` We have implemented a new Group Management API endpoint for our [REST API](/docs/developer-resources/rest-api.md). You can now leverage the new [Modify a group](/docs/developer-resources/rest-api/api-reference/groups/modify-group.md) feature. We now display the `role` field for each user in the response for the [List All Users](/docs/developer-resources/rest-api/api-reference/users/list-all-users.md) endpoint. --- ## May 2021 We have expanded the public API endpoints [Create a connection](/docs/developer-resources/rest-api/api-reference/connections/create-connection.md) and [Update a connection](/docs/developer-resources/rest-api/api-reference/connections/modify-connection.md). Now you can authorize the [Asana](/docs/rest-api/api-reference/connections/create-connection.md?service=asana) connection by adding the `auth` section to payloads. We have implemented a new Group Management API endpoint for our [REST API](/docs/developer-resources/rest-api.md). You can now leverage the new [Delete a group](/docs/developer-resources/rest-api/api-reference/groups/delete-group.md) feature. --- ## April 2021 We have expanded the [Create a connection](/docs/developer-resources/rest-api/api-reference/connections/create-connection.md) and [Update a connection](/docs/developer-resources/rest-api/api-reference/connections/modify-connection.md) public API endpoints. Now you can authorize the following connections by adding the `auth` section to payloads: - [Microsoft Advertising](/docs/rest-api/api-reference/connections/create-connection.md?service=bingads) - [Snapchat Ads](/docs/rest-api/api-reference/connections/create-connection.md?service=snapchat_ads) We have added a schema filter to our [List All Connections within a Group endpoint](/docs/developer-resources/rest-api/api-reference/groups/list-all-connections-in-group.md). Specify the schema of a connector as a value of the `schema` GET parameter to perform filtering and retrieve only information for that connector. We have published [Postman collection](/docs/developer-resources/rest-api/getting-started.md#postmancollection), which contains templates to help you create API requests for all endpoints supported by Fivetran. --- ## March 2021 We have implemented new API endpoints for our [REST API](/docs/developer-resources/rest-api.md): #### Destination Management - [Run destination setup tests](/docs/developer-resources/rest-api/api-reference/destinations/run-destination-setup-tests.md) #### Certificate Management - [Approve a destination certificate](/docs/developer-resources/rest-api/api-reference/certificates/approve-destination-certificate.md) - [Approve a destination fingerprint](/docs/developer-resources/rest-api/api-reference/certificates/approve-destination-fingerprint.md) You can also approve certificates and fingerprints automatically by specifying `true` as a value of the new `trust_certificates` and `trust_fingerprints` parameters in the existing Destination Management API endpoints: - [Create a destination](/docs/developer-resources/rest-api/api-reference/destinations/create-destination.md) - [Modify a destination](/docs/developer-resources/rest-api/api-reference/destinations/modify-destination.md) Now, you can set the time your daily syncs start using the `daily_sync_time` request parameter for the [Update a connection](/docs/developer-resources/rest-api/api-reference/connections/modify-connection.md) endpoint. We now display the `name_in_destination` field for each schema, table, and column in the response for the following endpoints: - [Retrieve a connection schema config](/docs/developer-resources/rest-api/api-reference/connection-schema/connection-schema-config.md) - [Retrieve source table columns config](/docs/developer-resources/rest-api/api-reference/connection-schema/connection-column-config.md) - [Reload a connection schema config](/docs/developer-resources/rest-api/api-reference/connection-schema/reload-connection-schema-config.md) - [Update a connection schema config](/docs/developer-resources/rest-api/api-reference/connection-schema/modify-connection-schema-config.md) - [Update a connection database schema config](/docs/developer-resources/rest-api/api-reference/connection-schema/modify-connection-database-schema-config.md) - [Update a connection table config](/docs/developer-resources/rest-api/api-reference/connection-schema/modify-connection-table-config.md) - [Update a connection column config](/docs/developer-resources/rest-api/api-reference/connection-schema/modify-connection-column-config.md) We now support the `timeframe_months` field for Facebook Ads connections created using the [Create a connection endpoint](/docs/rest-api/api-reference/connections/create-connection.md?service=facebook_ads). Learn more about Facebook Ads connector management in our [REST API documentation](/docs/rest-api/api-reference/connections/create-connection.md?service=facebook_ads). --- ## February 2021 Our Jira connector no longer uses the `use_webhooks` configuration field. --- ## January 2021 We have implemented a new Certificate Management API endpoint for our [REST API](/docs/developer-resources/rest-api.md). You can now leverage the new [Approve a connection fingerprint](/docs/developer-resources/rest-api/api-reference/certificates/approve-connection-fingerprint.md) feature. You can also approve fingerprints automatically by specifying `true` as a value of the new `trust_fingerprints` parameter in the existing Connector Management API endpoints: - [Create a connection](/docs/developer-resources/rest-api/api-reference/connections/create-connection.md) - [Update a connection](/docs/developer-resources/rest-api/api-reference/connections/modify-connection.md) - [Run connection setup tests](/docs/developer-resources/rest-api/api-reference/connections/run-setup-tests.md) We have introduced a new (v2) connector configuration return format for the following endpoints: - [Retrieve connection details](/docs/developer-resources/rest-api/api-reference/connections/connection-details.md) - [Create a connection](/docs/developer-resources/rest-api/api-reference/connections/create-connection.md) - [Update a connection](/docs/developer-resources/rest-api/api-reference/connections/modify-connection.md) - [Run connector setup tests](/docs/developer-resources/rest-api/api-reference/connections/run-setup-tests.md) We have expanded the public API endpoints [Create a connection](/docs/developer-resources/rest-api/api-reference/connections/create-connection.md) and [Update a connection](/docs/developer-resources/rest-api/api-reference/connections/modify-connection.md). Now you can authorize the following connections by adding the `auth` section to payloads: - [QuickBooks](/docs/rest-api/api-reference/connections/create-connection.md?service=quickbooks) - [Shopify](/docs/rest-api/api-reference/connections/create-connection.md?service=shopify) --- ## December 2020 We have implemented new Connector and Destination Management API endpoints for our [REST API](/docs/developer-resources/rest-api.md). You can now leverage the following new features: - [Delete a destination](/docs/developer-resources/rest-api/api-reference/destinations/delete-destination.md) - [Retrieve source metadata](/docs/developer-resources/rest-api/api-reference/connector-metadata/metadata-connectors.md) We have expanded the public API endpoints [Create a connection](/docs/developer-resources/rest-api/api-reference/connections/create-connection.md) and [Update a connection](/docs/developer-resources/rest-api/api-reference/connections/modify-connection.md). Now you can authorize the following connectors by adding the `auth` section to payloads: - [AdRoll](/docs/rest-api/api-reference/connections/create-connection.md?service=adroll) - [Facebook Pages](/docs/rest-api/api-reference/connections/create-connection.md?service=facebook_pages) - [Front](/docs/rest-api/api-reference/connections/create-connection.md?service=front) - [Google Ad Manager](/docs/rest-api/api-reference/connections/create-connection.md?service=double_click_publishers) - [Help Scout](/docs/rest-api/api-reference/connections/create-connection.md?service=helpscout) - [LinkedIn Ad Analytics](/docs/rest-api/api-reference/connections/create-connection.md?service=linkedin_ads) - [Optimizely](/docs/rest-api/api-reference/connections/create-connection.md?service=optimizely) - [Pipedrive](/docs/rest-api/api-reference/connections/create-connection.md?service=pipedrive) - [SurveyMonkey](/docs/rest-api/api-reference/connections/create-connection.md?service=survey_monkey) - [Zendesk Chat](/docs/rest-api/api-reference/connections/create-connection.md?service=zendesk_chat) - [Zendesk Support](/docs/rest-api/api-reference/connections/create-connection.md?service=zendesk) --- ## November 2020 We have expanded the public API endpoints [Create a connection](/docs/developer-resources/rest-api/api-reference/connections/create-connection.md) and [Update a connection](/docs/developer-resources/rest-api/api-reference/connections/modify-connection.md). Now you can authorize the following connectors by adding the `auth` section to payloads: - [Google Campaign Manager 360](/docs/rest-api/api-reference/connections/create-connection.md?service=double_click_campaign_manager) - [Google Ads](/docs/rest-api/api-reference/connections/create-connection.md?service=google_ads) - [Google Sheets](/docs/rest-api/api-reference/connections/create-connection.md?service=google_sheets) - [HubSpot](/docs/rest-api/api-reference/connections/create-connection.md?service=hubspot) --- ## October 2020 We have made changes to all public API endpoints that return the table and column configs as a response. Now you can see patch settings information for tables and columns in the response. It may help you understand whether you are allowed to enable or disable sync for them in the connector standard config. See the documentation for the following endpoints to learn more about the patch settings: - [Retrieve a connection schema config](/docs/developer-resources/rest-api/api-reference/connection-schema/connection-schema-config.md) - [Retrieve source table columns config](/docs/developer-resources/rest-api/api-reference/connection-schema/connection-column-config.md) - [Reload a connection schema config](/docs/developer-resources/rest-api/api-reference/connection-schema/reload-connection-schema-config.md) - [Update a connection schema config](/docs/developer-resources/rest-api/api-reference/connection-schema/modify-connection-schema-config.md) - [Update a connection database schema config](/docs/developer-resources/rest-api/api-reference/connection-schema/modify-connection-database-schema-config.md) - [Update a connection table config](/docs/developer-resources/rest-api/api-reference/connection-schema/modify-connection-table-config.md) - [Update a connection column config](/docs/developer-resources/rest-api/api-reference/connection-schema/modify-connection-column-config.md) We have expanded the public API endpoints [Create a connection](/docs/developer-resources/rest-api/api-reference/connections/create-connection.md) and [Update a connection](/docs/developer-resources/rest-api/api-reference/connections/modify-connection.md). Now you can authorize the following connections by adding the `auth` section to payloads: - [Microsoft Dynamics 365 CRM](/docs/rest-api/api-reference/connections/create-connection.md?service=dynamics_365) - [Salesforce](/docs/rest-api/api-reference/connections/create-connection.md?service=salesforce) --- ## September 2020 We have implemented a new Connector Management API endpoint for our [REST API](/docs/developer-resources/rest-api.md). You can now leverage the new [Retrieve Source Table Columns Config](/docs/developer-resources/rest-api/api-reference/connection-schema/connection-column-config.md) feature. We have added a new optional parameter, `hide_setup_guide`, to our [Connect Card](/docs/developer-resources/rest-api/getting-started/connect-card.md). It lets you hide the embedded setup guide. --- ## August 2020 We have updated the connector's REST API configuration parameters to support [JSON Web Token (JWT) Authentication](https://www.adobe.io/authentication/auth-methods.html#!AdobeDocs/adobeio-auth/master/JWT/JWT.md). See our [Adobe Analytics Connection Config documentation](/docs/rest-api/api-reference/connections/create-connection.md?service=adobe_analytics) for more information. We have updated the REST API configuration parameters to support new authentication mechanisms for the following connectors: - [Adobe Analytics](/docs/connectors/applications/adobe-analytics.md) now supports [JSON Web Token (JWT) Authentication](https://www.adobe.io/authentication/auth-methods.html#!AdobeDocs/adobeio-auth/master/JWT/JWT.md). See our [Adobe Analytics Connection Config documentation](/docs/rest-api/api-reference/connections/create-connection.md?service=adobe_analytics) for more information. - [Twilio](/docs/connectors/applications/twilio.md) now supports authentication using [API Keys](https://www.twilio.com/docs/usage/requests-to-twilio#api-keys). See our [Twilio Connector Config documentation](/docs/rest-api/api-reference/connections/create-connection.md?service=twilio) for more information. We made our [REST API](/docs/developer-resources/rest-api.md) available for all Trial accounts. To learn about limitations for Trials as compared to Standard and Enterprise accounts, read our [rate-limiting documentation](/docs/rest-api/rate-limiting.md). Our Databricks REST API endpoint now supports the creation of external tables. You can now opt to create Delta tables as external tables for your [Databricks](/docs/rest-api/api-reference/destinations/create-destination.md?service=databricks) implementations. We have expanded the current public API endpoint [Reload a connection schema config](/docs/developer-resources/rest-api/api-reference/connection-schema/reload-connection-schema-config.md). Now, you can enable or disable all schemas, tables and columns in the standard config by specifying the `exclude_mode` parameter in payloads. --- ## July 2020 We have expanded the current public API endpoint [Create a connection](/docs/developer-resources/rest-api/api-reference/connections/create-connection.md). Now, you can create a new connector in a paused state by specifying the `paused` parameter in payloads. We have implemented new Destination Management API endpoints for our [REST API](/docs/developer-resources/rest-api.md). You can now leverage the new [Retrieve Destination Details](/docs/developer-resources/rest-api/api-reference/destinations/destination-details.md) feature. You can now configure your Snowplow connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=snowplow). This feature is in BETA and is available only for Standard and Enterprise accounts. You can now configure your Webhooks connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=webhooks). This feature is in BETA and is available only for Standard and Enterprise accounts. --- ## June 2020 You can now configure your Google Ad Manager connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=double_click_publishers). This feature is in BETA and available only for Standard and Enterprise accounts. We have expanded the current public API endpoint [Create a Destination](/docs/developer-resources/rest-api/api-reference/destinations/create-destination.md). Now, you can: - control whether setup test are executed automatically by specifying the `run_setup_tests` parameter. - create a Snowflake destination with password-based or key-based authentication types. Read our updated documentation about [Snowflake destination config.](/docs/rest-api/api-reference/destinations/create-destination.md?service=#snowflake) We have implemented new Connector, Group, and Destination Management API endpoints for our [REST API](/docs/developer-resources/rest-api.md). You can now leverage the following new features: - [Create a Group](/docs/developer-resources/rest-api/api-reference/groups/create-group.md) - [Create a Destination](/docs/developer-resources/rest-api/api-reference/destinations/create-destination.md) - [Modify a Destination](/docs/developer-resources/rest-api/api-reference/destinations/modify-destination.md) - [Reload a Connector Schema Config](/docs/developer-resources/rest-api/api-reference/connection-schema/reload-connection-schema-config.md) --- ## May 2020 You can now configure your Facebook Pages connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=facebook_pages). This feature is in BETA and is available only for Standard and Enterprise accounts. You can now configure your Microsoft Advertising connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=bingads). This feature is in BETA and is available only for Standard and Enterprise accounts. You can now configure your Pinterest Ads connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=pinterest_ads). This feature is in BETA and is available only for Standard and Enterprise accounts. You can now configure your Asana connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=asana). This feature is in BETA and is available only for Standard and Enterprise accounts. You can now configure your GitHub connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=github). This feature is in BETA and available only for Standard and Enterprise accounts. You can now configure your Braze connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=braze). This feature is in BETA and is available only for Standard and Enterprise accounts. You can now configure your Eloqua connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=eloqua). This feature is in BETA and is available only for Standard and Enterprise accounts. You can now configure your HubSpot connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=hubspot). This feature is in BETA and is available only for Standard and Enterprise accounts. You can now configure your Generic Oracle, RDS Oracle, and Oracle E-Business Suite connectors using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=oracle). This feature is in BETA and available only for Standard and Enterprise accounts. You can now configure your Jira connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=jira). This feature is in BETA and available only for Standard and Enterprise accounts. You can now configure your Kantata connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=kantata). This feature is in BETA and available only for Standard and Enterprise accounts. You can now configure your Dropbox connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=dropbox). This feature is in BETA and available only for Standard and Enterprise accounts. You can now configure your LinkedIn Ad Analytics connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=linkedin_ads). This feature is in BETA and is available only for Standard and Enterprise accounts. You can now configure your Snapchat Ads connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=snapchat_ads). This feature is in BETA and is available only for Standard and Enterprise accounts. You can now configure your Splunk connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=splunk). This feature is in BETA and available only for Standard and Enterprise accounts. We have modified one of our REST API configuration parameters for [Anaplan](/docs/rest-api/api-reference/connections/create-connection.md?service=anaplan). We have replaced the `exports` field with the `selected_exports` field to sync specific exports. Each export in `selected_exports` field must be in the `<workspace_id>_<model_id>_<export_id>` format. You can now configure your Mailchimp connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=mailchimp). This feature is in BETA and available only for Standard and Enterprise accounts. --- ## April 2020 You can now configure your Adobe Analytics connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=adobe_analytics). This feature is in BETA and is available only for Standard and Enterprise accounts. You can now configure your AdRoll connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=adroll). This feature is in BETA and is available only for Standard and Enterprise accounts. You can now configure your MongoDB Sharded Cluster connector through the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=mongo). This feature is in BETA and available only for Standard and Enterprise accounts. You can now configure your Xero connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=xero). This feature is in BETA and is available only for Standard and Enterprise accounts. We have added Magento MySQL and Magento MySQL RDS to the list of connectors that can be created via our [REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=mysql). You can now configure your AWS Inventory connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=aws_inventory). This feature is in BETA and is available only for Standard and Enterprise accounts. You can now configure your Google Play connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=google_play). This feature is in BETA and available only for Standard and Enterprise accounts. You can now configure your Help Scout connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=helpscout). This feature is in BETA and is available only for Standard and Enterprise accounts. You can now configure your Intercom connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=intercom). This feature is in BETA and is available only for Standard and Enterprise accounts. You can now configure your Optimizely connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=optimizely). This feature is in BETA and is available only for Standard and Enterprise accounts. You can now configure the Fivetran Platform Connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=fivetran_log). This feature is in BETA and is available only for Standard and Enterprise accounts. You can now configure your Heap connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=heap). This feature is in BETA and is available only for Standard and Enterprise accounts. You can now configure your Lightspeed Retail connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=light_speed_retail). This feature is in BETA and is available only for Standard and Enterprise accounts. You can now configure your Segment connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=segment). This feature is in BETA and is available only for Standard and Enterprise accounts. You can now configure your AppsFlyer connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=appsflyer). This feature is in BETA and is available only for Standard and Enterprise accounts. You can now configure your Pendo connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=pendo). This feature is in BETA and is available only for Standard and Enterprise accounts. You can now configure your Amplitude connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=amplitude). This feature is in BETA and is available only for Standard and Enterprise accounts. You can now generate a new API secret from the account settings form if you think your current one was compromised. Read our [REST API docs](/docs/developer-resources/rest-api/getting-started.md) to learn how to regenerate your secret. You can now configure your Microsoft Dynamics 365 CRM connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=dynamics_365). This feature is in BETA and is available only for Standard and Enterprise accounts. We have made changes to the [re-sync connection table data endpoint](/docs/developer-resources/rest-api/api-reference/connection-schema/resync-tables.md). Now, if another data sync is in progress, we will try to complete it, and if it is unsuccessful the request will be declined and the HTTP 409 Conflict error will be returned. You can now configure your Anaplan connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=anaplan). This feature is in BETA and is available only for Enterprise accounts. You can now configure your QuickBooks connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=quickbooks). This feature is in BETA and is available only for Standard and Enterprise accounts. You can now configure your Zendesk Chat connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=zendesk_chat). This feature is in BETA and is available only for Standard and Enterprise accounts. You can now configure your Shopify connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=shopify). This feature is in BETA and is available only for Standard and Enterprise accounts. --- ## March 2020 You can now configure your Google Campaign Manager 360 connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=double_click_campaign_manager). This feature is in BETA and available only for Standard and Enterprise accounts. You can now configure your ServiceNow connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=servicenow). This feature is in BETA and is available only for Standard and Enterprise accounts. We have expanded the current public API endpoints [Create a connection](/docs/developer-resources/rest-api/api-reference/connections/create-connection.md) and [Update a connection](/docs/developer-resources/rest-api/api-reference/connections/modify-connection.md). Now, you can control whether setup test are executed automatically by specifying the `run_setup_tests` parameter. [Read our REST API docs to learn how enable or disable automatic setup tests execution.](/docs/developer-resources/rest-api.md) You can now configure your Google Search Console connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=google_search_console). This feature is in BETA and available only for Standard and Enterprise accounts. You can now configure your Apple App Store connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=itunes_connect). This feature is in BETA and is available only for Standard and Enterprise accounts. We have implemented new Connection Management API endpoints for our [REST API](/docs/developer-resources/rest-api.md). You can now leverage the following new features: - [Update a Connection Database Schema Config](/docs/developer-resources/rest-api/api-reference/connection-schema/modify-connection-database-schema-config.md) - [Update a Connection Table Config](/docs/developer-resources/rest-api/api-reference/connection-schema/modify-connection-table-config.md) - [Update a Connection Column Config](/docs/developer-resources/rest-api/api-reference/connection-schema/modify-connection-column-config.md) - [Run Connection setup tests](/docs/developer-resources/rest-api/api-reference/connections/run-setup-tests.md) You can now configure your Google Ads connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=google_ads). This feature is in BETA and available only for Standard and Enterprise accounts. --- ## February 2020 You can now configure your Stripe connector using the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=stripe). This feature is in BETA and available only for Standard and Enterprise accounts. --- ## January 2020 We have expanded the current public API [Update a connection](/docs/developer-resources/rest-api/api-reference/connections/modify-connection.md) endpoint. Now you can enable or disable automatic connector sync by changing the 'schedule_type' parameter. [Read our REST API docs to learn how to do that.](/docs/developer-resources/rest-api.md) You can now configure your Square connector through the [Fivetran REST API](/docs/rest-api/api-reference/connections/create-connection.md?service=square). This feature is in BETA and available only for Standard and Enterprise accounts. You can now configure your Adobe Analytics Data Feed connector through the [Fivetran REST API](/docs/developer-resources/rest-api.md). --- ## December 2019 We have implemented new Connector Management API endpoints for our [REST API](/docs/developer-resources/rest-api.md). You can now leverage the following new features: - [Re-sync all historical data for a connection](/docs/developer-resources/rest-api/api-reference/connections/resync-connection.md) - [Sync connection data on demand (custom scheduling)](/docs/developer-resources/rest-api/api-reference/connections/sync-connection.md) - [Re-sync a specific table within a connection](/docs/developer-resources/rest-api/api-reference/connection-schema/resync-tables.md) - [Retrieve a connection schema config](/docs/developer-resources/rest-api/api-reference/connection-schema/connection-schema-config.md) - [Update a connection schema config](/docs/developer-resources/rest-api/api-reference/connection-schema/modify-connection-schema-config.md) --- ## September 2019 We have disabled `HTTP` protocol support for our [REST API](/docs/developer-resources/rest-api.md) module for both public and partner APIs. To access the Fivetran REST API, you must now use `HTTPS` protocol, which is much more secure. --- ## July 2019 You can now configure your Twitter Ads connector through the [Fivetran REST API](/docs/developer-resources/rest-api.md). This feature is in BETA and available only for Standard and Enterprise accounts. --- ## April 2019 You can now configure your Salesforce connector through the [Fivetran REST API](/docs/developer-resources/rest-api.md). This feature is in BETA and available only for Standard and Enterprise accounts. --- ## March 2019 You can now configure your Zendesk Support connector through the [Fivetran REST API](/docs/developer-resources/rest-api.md). This feature is in BETA and available only for Standard and Enterprise accounts.