Official documentation example for workflow creation fails with API errors
I'm reporting an issue where the official example from your documentation fails when trying to create a workflow via API.
I used the exact cURL example from your documentation ( https://docs.vapi.ai/workflows/quickstart ), converted to Postman:
From documentation:
```bash
curl -X POST "https://api.vapi.ai/workflow" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "Information Gathering Demo",
"nodes": [
{
"id": "start",
"type": "conversation",
"firstMessage": "Hey there!",
"systemPrompt": "Ask users what kind of voice agent they want to build. Be friendly and conversational."
}
],
"edges": []
}'
When executing this exact JSON payload, I receive the following error response:
{
"message": [
"Workflow 'Information Gathering Demo' must have a 'start' node",
"each value in nodes.property id should not exist",
"nodes has no start node"
],
"error": "Bad Request",
"statusCode": 400
}
The API appears to reject the "id" property that is shown in the official documentation, and there's no clear way to mark a node as the start node.
Could you please:
Provide a working example that the current API accepts
Update the documentation to reflect the current API requirements
Clarify how to properly mark a start node without using the "id" field
Thank you for your assistance!
I used the exact cURL example from your documentation ( https://docs.vapi.ai/workflows/quickstart ), converted to Postman:
From documentation:
```bash
curl -X POST "https://api.vapi.ai/workflow" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "Information Gathering Demo",
"nodes": [
{
"id": "start",
"type": "conversation",
"firstMessage": "Hey there!",
"systemPrompt": "Ask users what kind of voice agent they want to build. Be friendly and conversational."
}
],
"edges": []
}'
When executing this exact JSON payload, I receive the following error response:
{
"message": [
"Workflow 'Information Gathering Demo' must have a 'start' node",
"each value in nodes.property id should not exist",
"nodes has no start node"
],
"error": "Bad Request",
"statusCode": 400
}
The API appears to reject the "id" property that is shown in the official documentation, and there's no clear way to mark a node as the start node.
Could you please:
Provide a working example that the current API accepts
Update the documentation to reflect the current API requirements
Clarify how to properly mark a start node without using the "id" field
Thank you for your assistance!
Build a simple agent that greets users and gathers basic information using Vapi workflows.
