ingestr v1.0.47 - Reddit Ads OAuth and Chargebee Source

ingestr v1.0.47 was published on June 25, 2026, with the most useful change for pipeline operators in the Reddit Ads source: OAuth refresh token authentication, account discovery, and account scoped tables. The same release also adds a Chargebee source, so this is a small but practical connector release for teams pulling paid media and billing data into ELT flows.

The full release notes and downloads are on the GitHub release page.

The main Reddit Ads change is OAuth refresh token auth. That matters because ad data extraction often runs on schedules that outlive a short lived access token. A connector that can refresh credentials is less dependent on manual token rotation and less likely to fail in the middle of a daily load.

The release notes also call out POST retry support for the OAuth token request when the upstream service returns HTTP 429 or a 5xx response. Token refresh is a bad place for a pipeline to be brittle. A transient rate limit or server error should not force the whole Reddit Ads sync to fail without another attempt.

For operators, the important detail is the scope of the retry. The notes name the OAuth token request, not every Reddit Ads API call. That is still useful, but it should be read as a targeted resilience fix rather than a broad retry policy for all extraction traffic.

ingestr v1.0.47 adds account auto discovery and per table account scoping for Reddit Ads. That gives teams a cleaner path when one credential can see more than one ad account, which is common in agency, holding company, and shared analytics setups.

The useful part is not just discovery. Per table account scoping gives pipeline authors a way to separate what each table should read. That can reduce accidental wide pulls, cut down on noisy data, and make downstream table ownership easier to reason about.

This is also the area to test before rollout. If existing jobs assumed a single account shape, account discovery can change what gets selected or exposed. The release notes do not describe a breaking migration, so the safer upgrade path is to run a narrow sync first and compare row counts by account.

The release includes a new Chargebee source. The notes do not list the supported Chargebee resources, so the practical reading is simple: this release expands ingestr into another billing and subscription data system, but teams should verify table coverage against their own reporting needs before relying on it.

For data engineers, Chargebee is usually less about raw ingestion volume and more about joining subscription events, customers, invoices, plans, and revenue state with product or warehouse data. A new source can reduce custom extraction code, but only if the exposed tables match the finance and analytics questions in use.

Because the release note only says “add chargebee source”, it is worth checking the connector behavior directly in a development load. Validate table names, primary keys, incremental behavior, and how deleted or changed billing records are represented.

One listed commit replaces a test token with a low entropy fake token so gitleaks accepts it. This is mostly internal maintenance, but it is still relevant for anyone running release builds or source checks in a stricter CI environment.

Secret scanners often flag realistic looking fixture values. Moving tests toward obvious fake values reduces noise without weakening the purpose of the test. It also makes automated release checks less likely to fail for a token that was never meant to authenticate anywhere.

There is no user facing feature here. It is the kind of small repository hygiene change that keeps connector work moving through CI with fewer false alarms.

• Release page: GitHub release page
• Repository: bruin-data/ingestr
• Tag: v1.0.47