dbt Cloud Integration on cloud.airbyte.com always returns dbt Cloud denied access

[jholder-methodic]

I am prototyping an integration for a customer and I have a trial airbyte cloud account as well as a trial DBT account. I have looked at various pieces of documentation, including this one that includes the 403 forbidden error information. Unfortunately for a DBT trial account, I can't select enterprise, and I don't have control of the IP addresses allowed. Is there some other way to get this to work? I wasn't expecting to be hung up on this step.

I have tried the dbt Access URL as:

• Blank
• https://my-access-id.us1.dbt.com
• my-access-id.us1.dbt.com EDIT: THIS APPEARS TO BE THE CORRECT THING TO PLACE IN THE URL BOX
• cloud.getdbt.com

DBT side shows the service token has not been used. There are no logs anywhere I can see to further troubleshoot this on my own.

Thanks for any pointers.

Full error message:

dbt Cloud denied access. Please verify your service token and access URL

[jholder-methodic]

According to dev tools in the browser, this is what is coming back from DBT cloud:

{
    "status": 400,
    "type": "error:dbtcloud/access-denied",
    "title": "Incorrect integration credentials",
    "detail": "The integration service denied access.",
    "documentationUrl": null,
    "data": {
        "host": "dbtcloud.com",
        "code": 401,
        "message": "listAccounts call failed with: 401 - {\"status\": {\"code\": 401, \"is_success\": false, \"user_message\": \"Invalid token.\", \"developer_message\": null}, \"data\": null}"
    }
}

I am continuing to dig around.

[jholder-methodic]

And here seems to be the issue. I placed the access URL given to me in my DBT account, and I get this error instead:

{
    "status": 400,
    "type": "error:dbtcloud/access-denied",
    "title": "Incorrect integration credentials",
    "detail": "The integration service denied access.",
    "documentationUrl": null,
    "data": {
        "host": "XXXX.us1.dbt.com",
        "code": 401,
        "message": "listAccounts call failed with: 401 - {\"status\": {\"code\": 401, \"is_success\": false, \"user_message\": \"The API is not accessible to unpaid accounts.\", \"developer_message\": null}, \"data\": null}"
    }
}

I will see about getting the DBT account paid for and will reopen this issue if that doesn't work.

[jholder-methodic]

I got the customer to put in a CC on DBT, but I am still getting the same error, reopening this.

[jholder-methodic]

I am theorizing that DBT seems to have been taken over by bean-counters intent on squeezing as much revenue as possible from their userbase. API access apparently used to work with the trial account, and now it doesn't. I made a DBT support ticket, and they said a starter account (100/seat/month with 2 seats - which we have already PAID) does not have API access. I asked the DBT AI chatbot, and it said a Teams account has API access. But there is no teams account, so I think this could all be a recent thing. I will update this thread with more information once I speak to sales.

[jholder-methodic]

I think this is the answer:
https://www.tobikodata.com/blog/dbt-fusion-death-of-dbt-core