Advanced Analytica Advanced Analytica: IBOM
← All connectors
Chift logo

Source connector

Chift

Set up Chift as a source and move its data into your chosen destination.

Version 0.1.8 community alpha

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

  1. In the Airbyte UI’s left navigation bar, click Sources. Then click + New source in the top-right corner.
  2. Find and select Chift from the available sources.
  3. Enter a Source name of your choice.
  4. Enter the Client Id, Client Secret and Account Id from your Chift API key.
  5. Optionally, enter a Start Date in YYYY-MM-DDTHH:MM:SS format, such as 2026-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 a Z suffix.
  6. 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:

FeatureSupported?
Full Refresh SyncYes
Incremental SyncYes
Replicate Incremental DeletesNo
SSL connectionYes
NamespacesNo

Supported streams

StreamPrimary keyIncrementalChift endpoint
consumersconsumeridNoGET /consumers
connectionsconnectionidNoGET /consumers/{consumerid}/connections
syncssyncidNoGET /syncs
executionsidYesGET /syncs/{syncid}/executions
  • consumers lists the consumers, your end customers, linked to your account.
  • connections lists every active or inactive connection for each consumer returned by consumers. The data field is a free-form object. Its keys depend on the connection’s integration, so the contents vary between rows.
  • syncs lists your account’s configured syncs. These include their connections, mappings, flows and the consumers they’re activated for. The display_condition object inside each mapping’s sub_mappings[].target_field is also free-form.
  • executions lists every run of each sync returned by syncs. Each record includes the execution’s start and end timestamps. It also includes its status, such as IN PROGRESS, FINISHED, ERROR or CANCELED. Each record identifies the consumer_id and flow_id it ran for. The stream is incremental on the start timestamp 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 executions stream only filters by execution start time. It never syncs executions started before your Start Date, even if they finished afterwards.
  • The connections.data and syncs.mappings[].sub_mappings[].target_field.display_condition objects 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
VersionDatePull RequestSubject
0.1.82026-11-1091410Update dependencies
0.1.72026-11-0390488Update dependencies
0.1.62026-10-2789850Update dependencies
0.1.52026-10-2089115Update dependencies
0.1.42026-10-1388571Update dependencies
0.1.32026-10-0687789Update dependencies
0.1.22026-09-2987100Update dependencies
0.1.12026-09-2286568Update dependencies
0.1.02026-09-1677576Add 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.262026-09-1585978Update dependencies
0.0.252026-09-0885452Update dependencies
0.0.242026-08-1884529Update dependencies
0.0.232026-08-1183887Update dependencies
0.0.222026-08-0483399Update dependencies
0.0.212026-07-2882860Update dependencies
0.0.202026-07-2182371Update dependencies
0.0.192026-07-1481778Update dependencies
0.0.182026-06-3081003Update dependencies
0.0.172026-06-2380430Update dependencies
0.0.162026-06-1679800Update dependencies
0.0.152026-06-0979250Update dependencies
0.0.142026-06-0278653Update dependencies
0.0.132026-04-2877164Update dependencies
0.0.122026-04-2176551Update dependencies
0.0.112026-03-3175769Update dependencies
0.0.102026-03-1775077Update dependencies
0.0.92026-03-1074454Update dependencies
0.0.82026-02-2473822Update dependencies
0.0.72026-02-1773447Update dependencies
0.0.62026-02-1073000Update dependencies
0.0.52026-02-0372704Update dependencies
0.0.42026-01-2072112Update dependencies
0.0.32026-01-1471711Update dependencies
0.0.22025-12-1970944Update dependencies
0.0.12025-10-13Initial release by @FVidalCarneiro via Connector Builder
Advanced Analytica

Most businesses are sitting on information they can’t use at speed. The people who hold it are busy, and when they leave, the knowledge goes with them. The documents are static, and the processes around them weren’t designed for AI.

Advanced Analytica works with these businesses to turn that information into structured data assets. Once they're integrated, AI systems can govern it, and the business can use it. We bring in the strategy, the specification and the AI skills to rework how the business operates.

MOVE FAST. STAY SAFE.