assistant
# support
j
Hi team, can somebody help me to know how can I get the assistant object back on a request via api? the get assistant by id is not returning the assistant object .... https://cdn.discordapp.com/attachments/1420677715669028864/1420677716004442163/image.png?ex=68d644ba&is=68d4f33a&hm=6687a60488d3d6dcaf49580be8da8507e02d4f04fbbe4ceceb635921bf8395ec&
v
Looks like your call is only giving back the config details instead of the full assistant object. I can help you check if it’s the right endpoint or if something extra needs to be passed in the request. Just to be clear, are you calling the Assistants API directly, or are you trying to fetch it through a campaign/session in VAPI? @Javi
v
Thanks for sharing the details and examples. From what I see, the get assistant endpoint returns configuration and metadata, but not the full runtime assistant object, which is why Postman and API docs show the same. I can help you verify if you need to fetch it through a session/call object or adjust parameters to get the complete payload. Are you looking to retrieve it for active calls or just the static assistant definition? This way, we can pinpoint the most reliable method. @Javi
j
Hi @Vercel , I need it just to load the full information on my client side for edit purposes , I have my own frontend creation/edition assistants intarfaces , so, to edit all I need first to show all to my clients , that is the reason because I need the full Assistant object back
v
I see what you’re aiming for, you need the full assistant object so your clients can edit everything in your frontend. The default endpoint won’t return all of that directly, but there’s a clean way to piece it together or wrap it so you always get the full payload. I’ve done this setup before and can walk you through the exact steps. Let’s chat privately and I’ll help you sort it out. @Javi
c
checking if this is resolved/solved for you?
j
Hi Kyle, not yet
Hi @Shubham Bajaj please, can you help me with this?
c
We apologize for the delay in responses lately. We are in process of making some changes to our workflow in how we handle support requests. The good news is that we are starting to get back on track of having a 48 hour response time and we would like to start cleaning up anything old. With that being said, just wanted to check in with you to see if you have made any progress or changes to your project since support has last reached out.
2 Views