501 error when hitting initiateOAuth endpoint for Quickbooks OAuth source


When attempting to create a new Quickbooks OAuth source using the initiateOAuth endpoint in Airbyte OSS running on an EKS cluster, a 501 error with no additional information is received. Other API calls are working. Check the request format and parameters for any missing or incorrect details.


Hi all, I’m currently attempting to build out an automated flow that will create a new Quickbooks OAuth source when a new tenant is onboarded onto our platform. However, I am being met with a 501 error with no other information when hitting the initiateOAuth endpoint. Airbyte OSS is running on an EKS cluster, and other API calls work. Here’s the current request format from Python:

payload = {
    "sourceType": "quickbooks",
    "redirectUrl": <VALID REDIRECT URL>,
    "workspaceid": <AIRBYTE WORKSPACE ID>,
    "oAuthInputConfiguration": {
         "client_id": <CLIENT ID>,
         "client_secret": <CLIENT SECRET>

headers = {
    "accept": "application/json",
    "content-type": "application/json"

response = <http://requests.post|requests.post>(url, json=payload, headers=headers)```
The response contains a 501 status code with no text description. Any ideas on what I'm missing?



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1718125539521499) if you want 
to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

["501-error", "initiateoauth-endpoint", "quickbooks-oauth-source", "airbyte-oss", "eks-cluster", "python-request"]

Digging further into this, I’m seeing discrepancies in lists of sources with this feature enabled across the docs. Some have Quickbooks listed, and some do not. Can someone confirm if Quickbooks sources can be created w/OAuth via API calls?