Chift
Set up the Chift source connector and find its reference information on this page.
Chift is a unified API for financial software. It connects your SaaS product to accounting, invoicing, point-of-sale and other financial tools. It uses consumers for your end customers and connections for a consumer’s link to one of those tools. syncs are data flows that Chift runs between tools. This connector reads platform metadata and your sync execution history from the Chift API. It doesn’t read financial data, such as invoices and journal entries, flowing through those connections.
Prerequisites
- A Chift account with access to the Chift platform.
- A Chift API key. In the Chift platform, open the API Keys page and click Add API Key. When you create the key, copy the Client ID and Client Secret. Chift shows the client secret only once. You’ll find your Account ID at the top left of the same page. See Chift’s Create and manage API keys guide.
Consider the following when choosing or creating your key:
- The key determines the environment. All keys use the same base URL. A key created in Chift’s Sandbox environment only sees sandbox consumers. A key created in Production only sees production consumers.
- Chift lets you restrict a key to one or more consumers. A restricted key limits the connector to data that the key can access. Use an unrestricted key to sync your whole account.
Set up Chift
- In the Airbyte UI’s left navigation bar, click Sources. Then click + New source in the top-right corner.
- Find and select Chift from the available sources.
- Enter a Source name of your choice.
- Enter the Client Id, Client Secret and Account Id from your Chift API key.
- Optionally, enter a Start Date in
YYYY-MM-DDTHH:MM:SSformat, such as2026-01-01T00:00:00. The connector only syncs executions that started on or after this date. Leave it empty to sync all executions. Other formats are rejected, including dates without times or values with aZsuffix. - Click Set up source and wait for the tests to finish.
At the start of each sync, the connector calls Chift’s POST /token endpoint to exchange your credentials for a short-lived bearer token. If the call returns a 401 error, check that all three values belong to the same API key. Also check that the key hasn’t been deleted.
Supported sync modes
The Chift source connector supports these sync modes:
| Feature | Supported? |
|---|---|
| Full Refresh Sync | Yes |
| Incremental Sync | Yes |
| Replicate Incremental Deletes | No |
| SSL connection | Yes |
| Namespaces | No |
Supported streams
| Stream | Primary key | Incremental | Chift endpoint |
|---|---|---|---|
consumers | consumerid | No | GET /consumers |
connections | connectionid | No | GET /consumers/{consumerid}/connections |
syncs | syncid | No | GET /syncs |
executions | id | Yes | GET /syncs/{syncid}/executions |
consumerslists the consumers, your end customers, linked to your account.connectionslists every active or inactive connection for each consumer returned byconsumers. Thedatafield is a free-form object. Its keys depend on the connection’s integration, so the contents vary between rows.syncslists your account’s configured syncs. These include their connections, mappings, flows and the consumers they’re activated for. Thedisplay_conditionobject inside each mapping’ssub_mappings[].target_fieldis also free-form.executionslists every run of each sync returned bysyncs. Each record includes the execution’sstartandendtimestamps. It also includes itsstatus, such asIN PROGRESS,FINISHED,ERRORorCANCELED. Each record identifies theconsumer_idandflow_idit ran for. The stream is incremental on thestarttimestamp and pages through 50 results at a time.
connections and executions are child streams. The connector always reads consumers to build connections, even when you don’t select the parent stream. It also always reads syncs to build executions, even when you don’t select the parent stream.
Limits and troubleshooting
- Chift doesn’t rate limit calls to its API, so the connector doesn’t throttle requests. Chift’s rate limit documentation explains limits that individual third-party integrations may enforce. These limits don’t affect the endpoints used by this connector.
- The
executionsstream only filters by execution start time. It never syncs executions started before your Start Date, even if they finished afterwards. - The
connections.dataandsyncs.mappings[].sub_mappings[].target_field.display_conditionobjects have no fixed schema. Destinations writing typed files store them as JSON strings. This applies to S3 and GCS destinations using Avro or Parquet format. Destinations using JSON, VARIANT or JSONB columns keep the whole object. See the migration guide for details.
IP allow list
If you use Airbyte Cloud and restrict access to specific IPs, add the Airbyte Cloud IP addresses to your allow list.
Changelog
Expand to review
| Version | Date | Pull Request | Subject |
|---|---|---|---|
| 0.1.8 | 2026-11-10 | 91410 | Update dependencies |
| 0.1.7 | 2026-11-03 | 90488 | Update dependencies |
| 0.1.6 | 2026-10-27 | 89850 | Update dependencies |
| 0.1.5 | 2026-10-20 | 89115 | Update dependencies |
| 0.1.4 | 2026-10-13 | 88571 | Update dependencies |
| 0.1.3 | 2026-10-06 | 87789 | Update dependencies |
| 0.1.2 | 2026-09-29 | 87100 | Update dependencies |
| 0.1.1 | 2026-09-22 | 86568 | Update dependencies |
| 0.1.0 | 2026-09-16 | 77576 | Add executions stream, incremental on start and paginated on page/size. Declare connections.data and target_field.display_condition schemaless, matching Chift’s contract, so schematizing destinations (S3/GCS Avro/Parquet) stop dropping their integration-defined keys - see the migration guide |
| 0.0.26 | 2026-09-15 | 85978 | Update dependencies |
| 0.0.25 | 2026-09-08 | 85452 | Update dependencies |
| 0.0.24 | 2026-08-18 | 84529 | Update dependencies |
| 0.0.23 | 2026-08-11 | 83887 | Update dependencies |
| 0.0.22 | 2026-08-04 | 83399 | Update dependencies |
| 0.0.21 | 2026-07-28 | 82860 | Update dependencies |
| 0.0.20 | 2026-07-21 | 82371 | Update dependencies |
| 0.0.19 | 2026-07-14 | 81778 | Update dependencies |
| 0.0.18 | 2026-06-30 | 81003 | Update dependencies |
| 0.0.17 | 2026-06-23 | 80430 | Update dependencies |
| 0.0.16 | 2026-06-16 | 79800 | Update dependencies |
| 0.0.15 | 2026-06-09 | 79250 | Update dependencies |
| 0.0.14 | 2026-06-02 | 78653 | Update dependencies |
| 0.0.13 | 2026-04-28 | 77164 | Update dependencies |
| 0.0.12 | 2026-04-21 | 76551 | Update dependencies |
| 0.0.11 | 2026-03-31 | 75769 | Update dependencies |
| 0.0.10 | 2026-03-17 | 75077 | Update dependencies |
| 0.0.9 | 2026-03-10 | 74454 | Update dependencies |
| 0.0.8 | 2026-02-24 | 73822 | Update dependencies |
| 0.0.7 | 2026-02-17 | 73447 | Update dependencies |
| 0.0.6 | 2026-02-10 | 73000 | Update dependencies |
| 0.0.5 | 2026-02-03 | 72704 | Update dependencies |
| 0.0.4 | 2026-01-20 | 72112 | Update dependencies |
| 0.0.3 | 2026-01-14 | 71711 | Update dependencies |
| 0.0.2 | 2025-12-19 | 70944 | Update dependencies |
| 0.0.1 | 2025-10-13 | Initial release by @FVidalCarneiro via Connector Builder |