VAPI•8mo ago

Facing error when trying to use Websocket transport

When I trigger this API for a websocket call:

curl --location 'https://api.vapi.ai/call' \
--header 'authorization: Bearer 90947ae3-94ca-46d2-a4a5-b7665912f759' \
--header 'content-type: application/json' \
--header 'Cookie: _cfuvid=s3GI9uVVCtYM7jKZAx106nOLCnP2xvmj5AHoWQdyJBI-1746269265225-0.0.1.1-604800000' \
--data '{
    "assistantId": "d539f5aa-59bc-4a2f-9fbd-b0a349010c2d",
    "transport": {
      "provider": "vapi.websocket"
    }
  }'

curl --location 'https://api.vapi.ai/call' \
--header 'authorization: Bearer 90947ae3-94ca-46d2-a4a5-b7665912f759' \
--header 'content-type: application/json' \
--header 'Cookie: _cfuvid=s3GI9uVVCtYM7jKZAx106nOLCnP2xvmj5AHoWQdyJBI-1746269265225-0.0.1.1-604800000' \
--data '{
    "assistantId": "d539f5aa-59bc-4a2f-9fbd-b0a349010c2d",
    "transport": {
      "provider": "vapi.websocket"
    }
  }'

curl --location 'https://api.vapi.ai/call' \
--header 'authorization: Bearer 90947ae3-94ca-46d2-a4a5-b7665912f759' \
--header 'content-type: application/json' \
--header 'Cookie: _cfuvid=s3GI9uVVCtYM7jKZAx106nOLCnP2xvmj5AHoWQdyJBI-1746269265225-0.0.1.1-604800000' \
--data '{
    "assistantId": "d539f5aa-59bc-4a2f-9fbd-b0a349010c2d",
    "transport": {
      "provider": "vapi.websocket"
    }
  }'

curl --location 'https://api.vapi.ai/call' \
--header 'authorization: Bearer 90947ae3-94ca-46d2-a4a5-b7665912f759' \
--header 'content-type: application/json' \
--header 'Cookie: _cfuvid=s3GI9uVVCtYM7jKZAx106nOLCnP2xvmj5AHoWQdyJBI-1746269265225-0.0.1.1-604800000' \
--data '{
    "assistantId": "d539f5aa-59bc-4a2f-9fbd-b0a349010c2d",
    "transport": {
      "provider": "vapi.websocket"
    }
  }'

This is the response that I get:

{
    "transport": {
        "provider": "vapi.websocket",
        "websocketCallUrl": "wss://phone-call-websocket.aws-us-west-2-backend-production1.vapi.ai/0f80953a-2a98-4150-9d7a-1cd093e318c1/transport"
    },
    "assistantId": "d539f5aa-59bc-4a2f-9fbd-b0a349010c2d",
    "id": "0f80953a-2a98-4150-9d7a-1cd093e318c1",
    "orgId": "c7eeddf1-2236-4c47-9505-cf0c1dfa66b4",
    "createdAt": "2025-05-03T10:47:45.085Z",
    "updatedAt": "2025-05-03T10:47:45.085Z",
    "type": "vapi.websocketCall",
    "status": "queued"
}

{
    "transport": {
        "provider": "vapi.websocket",
        "websocketCallUrl": "wss://phone-call-websocket.aws-us-west-2-backend-production1.vapi.ai/0f80953a-2a98-4150-9d7a-1cd093e318c1/transport"
    },
    "assistantId": "d539f5aa-59bc-4a2f-9fbd-b0a349010c2d",
    "id": "0f80953a-2a98-4150-9d7a-1cd093e318c1",
    "orgId": "c7eeddf1-2236-4c47-9505-cf0c1dfa66b4",
    "createdAt": "2025-05-03T10:47:45.085Z",
    "updatedAt": "2025-05-03T10:47:45.085Z",
    "type": "vapi.websocketCall",
    "status": "queued"
}

{
    "transport": {
        "provider": "vapi.websocket",
        "websocketCallUrl": "wss://phone-call-websocket.aws-us-west-2-backend-production1.vapi.ai/0f80953a-2a98-4150-9d7a-1cd093e318c1/transport"
    },
    "assistantId": "d539f5aa-59bc-4a2f-9fbd-b0a349010c2d",
    "id": "0f80953a-2a98-4150-9d7a-1cd093e318c1",
    "orgId": "c7eeddf1-2236-4c47-9505-cf0c1dfa66b4",
    "createdAt": "2025-05-03T10:47:45.085Z",
    "updatedAt": "2025-05-03T10:47:45.085Z",
    "type": "vapi.websocketCall",
    "status": "queued"
}

{
    "transport": {
        "provider": "vapi.websocket",
        "websocketCallUrl": "wss://phone-call-websocket.aws-us-west-2-backend-production1.vapi.ai/0f80953a-2a98-4150-9d7a-1cd093e318c1/transport"
    },
    "assistantId": "d539f5aa-59bc-4a2f-9fbd-b0a349010c2d",
    "id": "0f80953a-2a98-4150-9d7a-1cd093e318c1",
    "orgId": "c7eeddf1-2236-4c47-9505-cf0c1dfa66b4",
    "createdAt": "2025-05-03T10:47:45.085Z",
    "updatedAt": "2025-05-03T10:47:45.085Z",
    "type": "vapi.websocketCall",
    "status": "queued"
}

But when connecting the websocketCallUrl, it returns 500 internal server error (see the attached screenshot), can you please help me with this?

Vapi Support BotAPP•5/3/25, 11:04 AM

Since you're getting a 500 Internal Server Error (server-side issue), try these steps:

Retry the request
- Sometimes these errors are temporary
Check URL validity
- Ensure the websocket URL hasn't expired (they're often valid for only a short time)
Establish connections in order
- First connect to /transport/transport then to /listen/listen as the listen endpoint expects the transport connection to be established first

If the issue persists, contact Vapi support with your error details and timestamp.

Sources:

⤵️ Mention @Vapi Support Bot for follow-ups 🐥

living-lavender•5/3/25, 3:49 PM

Follow this guide, https://docs.vapi.ai/calls/websocket-transport

WebSocket Transport | Vapi

Stream audio directly via WebSockets for real-time, bidirectional communication

dual-salmonOP•5/3/25, 6:15 PM

I did try that @Sahil!
Using the curl (Create a websocket call) from the docs, I received this error:

{
    "message": [
        "assistant.property assistantId should not exist",
        "transport.audioFormat.an unknown value was passed to the validate function"
    ],
    "error": "Bad Request",
    "statusCode": 400
}

{
    "message": [
        "assistant.property assistantId should not exist",
        "transport.audioFormat.an unknown value was passed to the validate function"
    ],
    "error": "Bad Request",
    "statusCode": 400
}

Then I removed the audioFormat object, and replaced "assistant": { "assistantId": "d539f5aa-59bc-4a2f-9fbd-b0a349010c2d" },"assistant": { "assistantId": "d539f5aa-59bc-4a2f-9fbd-b0a349010c2d" }, with "assistantId": "d539f5aa-59bc-4a2f-9fbd-b0a349010c2d""assistantId": "d539f5aa-59bc-4a2f-9fbd-b0a349010c2d"

This worked fine.

But when I tried to connect to the wss endpoint, it returned "Internal Server Error" (See the screenshot attached in the previous message)

Screenshot_2025-05-03_at_11.41.32_PM.png

Screenshot_2025-05-03_at_11.43.40_PM.png

living-lavender•5/4/25, 1:44 AM

Looks like a bug cause ideally we need to provide the audioFormat otherwise it will not work.

dual-salmonOP•5/4/25, 4:32 AM

Yes @Sahil, because as per the docs, it looks straightforward. Can you get it checked once and let me know the next steps?

living-lavender•5/4/25, 5:21 AM

Sure, give me some time. Today is sunday so most of the folks are offline.

living-lavender•5/4/25, 5:21 AM

Will get back to you soon.

dual-salmonOP•5/4/25, 6:29 AM

No problem, Thanks

dual-salmonOP•5/5/25, 6:38 AM

Any updates on this @Sahil ?

living-lavender•5/5/25, 12:17 PM

They are on PST Timezone, but we will working on it.

dual-salmonOP•5/5/25, 12:18 PM

Thanks for the info @Sahil

thick-teal•5/6/25, 12:13 PM

Any update ?

KyleAPP•5/6/25, 10:01 PM

Hey @bauman you can track it over here https://vapi.steelsync.io/public-support-board

dual-salmonOP•5/20/25, 6:32 AM

It's been more than 10 days, any updates on this? @Sahil @Shubham Bajaj

KyleAPP•5/20/25, 8:26 PM

Hey Yash, we’ve got quite a bit going on right now, and honestly, we’re not seeing many complaints about this. So, it’s going to take a little longer.

Facing error when trying to use Websocket transport

Similar Threads

Similar Threads

Similar Threads