I'm getting the error "Invalid KB Details. Failed to validate trieve dataset: dataset not found" You can see the error in the first screenshot, and in the second you can see that trieve does have an dataset matching the provider ID I am sending. https://cdn.discordapp.com/attachments/1351972130010566698/1351972130417410193/image.png?ex=67dc51aa&is=67db002a&hm=235f8df28da89c150eaa82ff359f6d242f3538334c81b143c59da8e10b23496b& https://cdn.discordapp.com/attachments/1351972130010566698/1351972130874720376/image.png?ex=67dc51aa&is=67db002a&hm=0a9ad28cdaebc47e3b7baadfb8393282c75606d23643f9c84a905f304f5a6a59&

Are you sure that your provider credential Api Key is correct? Those are scoped per Trieve organization, so you may need a new one if you changed Trieve orgs.

I verified the correct API key as I'm able to do other requests. Also, I only have the one Org with this ID. https://cdn.discordapp.com/attachments/1351972130010566698/1352005469756981308/image.png?ex=67dc70b7&is=67db1f37&hm=f531d74c1e6ad70526a61d0b6fb2d15f8105ea4f16a13af69c445bfb203c2fcf&

@Ryan Opfer is this resolved?

I'm still getting the same error.

DM'ing you

Have you ensured your Trieve API credentails have been set on your VAPI org.

Yep, I can do other API calls.

@Ryan Opfer The KB was failing to be created because it was unable to find out if the dataset exists or not. The resolution to this was eventually creating the KB again, which you have already done. So yeah I'm putting the logs below and marking this trigger as solved.

json
{
  "message": "Invalid Knowledge Base Details. Failed to validate trieve dataset: dataset not found",
  "error": "Bad Request",
  "statusCode": 400
}

i'm facing the same problem. Is this "solution" part of a bug that was/being fixed? i already: - double checked the permissions on the api key - set trieve's api key on vapi - tried creating a new blank ds on trieve and then using it to create a kb in vapi always the same problem: dataset not found

This ticket has been marked as solved, and as a result, you will no longer receive any further responses. Kindly create a new support ticket to escalate your inquiry.