I can't seem to pass it as a parameter, and my appointment sets are failing with a 401. From testing this appears to be due to a missing locationid parameter. I have oauth set up at the agency level - does it need to be set at the subaccount level for these tools to work? The check availabiltiy tool works fine. We dont need the contact tools because we pass in contactiD and that part works fine.

Generate and use an OAuth token scoped to the subaccount not the agency, then pass it in the Authorization header along with the correct locationId, this will resolve the 401 error..

Thanks, is tehre any way to use multiple subaccounts with one VAPI acccount?

Yes, through “Organizations” feature, this allows you to manage separate workspaces under one main account..

Perfect, thanks!

Is there a workaround we can use to other than the creating a new organisation fro each sub account? @Chris Sloane