Hey 👋 I'm doing a job of rewriting my back-end code thanks to the server-sdk ! However, it's very painful to see that the types are not respected in many different places 😭 Just with the endpoints GET /call and the end-of-call reports, I can highlight many issues... here are two as examples Get /call Call id 5caf9c9b-2da8-4a21-83e8-e58363c66789 (see image). Doesn't seem to respect the CallDto type: where is my assistantId stored ? Well, in a weird attribute assistant.*parentId *?! Where does that come from ? Seems to occur for all web calls. EoCall report See below extract from an EoCall report for call e21b9436-6a32-4e10-b3a9-ed91922719c6. It has attribute assistant_id (with underscore) instead of assistantId 😢 I have many other situations where some attributes is there or is not there depending on whether we call web vs phone, etc. "call": { "id": "e21b9436-6a32-4e10-b3a9-ed91922719c6", "org_id": "3a97126a-a8ca-4efa-98fb-f732f631caf2", "created_at": "2025-03-09T14:59:16.778Z", "updated_at": "2025-03-09T14:59:16.778Z", "type": "inboundPhoneCall", "monitor": { "listen_url": "wss://phone-call-websocket.aws-us-west-2-backend-production1.vapi.ai/e21b9436-6a32-4e10-b3a9-ed91922719c6/listen", "control_url": "https://phone-call-websocket.aws-us-west-2-backend-production1.vapi.ai/e21b9436-6a32-4e10-b3a9-ed91922719c6/control" }, "transport": {}, "phone_call_provider": "vonage", "phone_call_provider_id": "CON-882ec50a-9ef1-4dd3-83ff-efab4a292739", "phone_call_transport": "pstn", "status": "ringing", "assistant_id": "17ce7337-2aa8-4813-9daf-fdcdfabc7989", "phone_number_id": "4d982680-ebbb-4150-a80a-487cc5bf96b0", "customer": { "number": "+32492858550" } }, https://cdn.discordapp.com/attachments/1348313755083083848/1348313755712356425/image.png?ex=67cf0289&is=67cdb109&hm=79bb8d99ca117264c6cd3d896b6223bcbab7bc91e94f6b9b7a1531a9b50c370d&

Can you please create ticket on the github? If you don't get the response let me know.

Right but the server sdk is automatically generated anyway, right ? Still better to go down that road ?

Hey Jeebs, creating that ticket on github will still be the best route as it will go directly to the engineering team.