Issue with Chargebee connector compatibility with API endpoint versions

Slack Knowledge Base Q&A Connector Questions
, , , ,
1

Summary

The user is experiencing a 400 status code error with the Chargebee connector due to compatibility issues with different versions of the API endpoint. They suspect it may be related to a recent commit and pull request in the Airbyte repository.


Question

Hi Community, we recently start having issue with <https://docs.airbyte.com/integrations/sources/chargebee|Chargebee connector >: https://{domain}.<http://chargebee.com/api/v2/plans?sort_by%5Basc%5D=updated_at&include_deleted=true&updated_at%5Bbetween%5D=%5B1641027600%2C+1643705999%5D|chargebee.com/api/v2/plans?sort_by%5Basc%5D=updated_at&include_deleted=true&updated_at%5Bbetween%5D=%5B1641027600%2C+1643705999%5D> failed with status code 400 and error message The API endpoint is incompatible with the product catalog version. You are calling product catalog 1.0 API endpoint but you are using product catalog 2.0

I guess it’s related to latest commit: https://github.com/airbytehq/airbyte/commit/7c6b528e1f057921d24b48faee4ec31a5782a145 & https://github.com/airbytehq/airbyte/pull/48133|PR

We still observing this issues for plans, addons endpoints. Could you please help us to understand whether this is known issue?


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["chargebee-connector", "api-endpoint", "compatibility-issue", "product-catalog", "400-error", "github-commit", "github-pull-request"]
2

We have the same issue <@U07V94Z5PAM>. Did you already found a solution?

3

We disabled endpoints from v1

4

Sounds like an easy solution! Are you on the latest version of the connector?

5

Yup, and with recent it still doesn’t work

6

Thank you for your help, much appreciated! We will go for the same solution