Create Chat
Creates a new chat using a user message, optional system context, and model configuration. Useful for prompting the model within the scope of a specific project.
Usage
import { v0 } from 'v0-sdk'const result = await v0.chats.create({ system: 'You are an expert coder', message: 'Create a landing page for a new product', projectId: 'proj_123',})console.log(result)API Signature
Request
Body
Creates a new chat using a user message, optional system context, and model configuration. Useful for prompting the model within the scope of a specific project.
A list of files or assets to be included in the conversation context. Useful when the chat or task requires referencing documents, images, or other resources.
Provides system-level context or background for the chat. This is typically used to specify frameworks, tools, or development environments relevant to the task.
Determines the privacy setting of the chat. This can control whether the chat is visible only to the user, to team members, or is public.
Associates the chat with a specific project in your workspace. Helps organize and group related chats under a common project context.
Settings that control how the model behaves in the chat.
Deprecated Model ID field preserved for backward compatibility.
Enables image generations to generate up to 5 images per version.
Enables thinking to generate a response in multiple steps.
Controls how the response is delivered.
"sync": The response is returned immediately with the HTTP request."async": Returns a message placeholder immediately; use getById to poll for completion status and final output."experimental_stream": Returns content parts as Server-Sent Events for real-time streaming.
The ID of a design system to apply to this chat. Design systems provide consistent styling and components for generated UI.
Arbitrary key-value data to attach to the chat. Useful for storing additional data about the chat, such as external user IDs. Keys must be 1-40 characters, values must be 1-500 characters, and a maximum of 50 key-value pairs are allowed.
Array of MCP server IDs to enable for this chat. When provided, only the specified servers will be used. When omitted, falls back to the user's enabled MCP servers. Pass an empty array to explicitly disable all MCP servers.
Response
A unique identifier for the chat.
Fixed value identifying this object as a chat.
Deprecated: Use the privacy field instead. A chat is shareable when privacy is public or unlisted.
Defines the visibility of the chat—private, team-only, or public.
An optional name assigned to the chat by the user.
Deprecated title field preserved for backward compatibility.
The ISO timestamp representing when the chat was created.
The ISO timestamp of the last update to the chat.
Indicates whether the chat is marked as a favorite.
The ID of the user who created the chat.
Optional ID of the v0 project associated with this chat.
Web URL to view this chat in the browser.
API URL to access this chat via the API.
Full details of the most recent generated version, if available.
A unique identifier for the version.
Fixed value identifying this object as a version.
The current status of the version generation process.
Optional URL for previewing the generated output.
URL to retrieve a screenshot of this version.
The date and time when the version was created, in ISO 8601 format.
The date and time when the version was last updated, in ISO 8601 format.
A list of files that were generated or included in this version.
The canonical URL to access this chat.
All messages exchanged in the chat, including user and assistant entries.
A unique identifier for the message.
Fixed value identifying this object as a message.
The main text content of the message.
The parsed content of the message as an array structure containing AST nodes. This is an experimental field that may change.
The ISO timestamp representing when the message was created.
The ISO timestamp representing when the message was last updated.
Indicates the format or category of the message, such as plain text or code.
Specifies whether the message was sent by the user or the assistant.
The reason why the message generation finished.
API URL to access this message via the API.
The ID of the user who sent the message.
The ID of the parent message.
The URL where the attachment file can be accessed.
The original filename of the attachment.
The MIME type of the attachment file (e.g., image/png, application/pdf).
The size of the attachment file in bytes.
The base64-encoded content of the attachment file, if available.
Optional v0-specific attachment type for enhanced processing.
Optional array of files associated with the chat context.
Programming language used in the file (e.g., JavaScript, Python).
A key-value map of metadata associated with the file (e.g., path, type).
The origin or identifier of the file source (e.g., path or upload label).
Deprecated demo URL used for previewing the chat result.
The main user prompt or instruction that started the chat.
The configuration used to generate responses in this chat.
Deprecated Model ID field preserved for backward compatibility.
Enables image generations to generate up to 5 images per version.
Enables thinking to generate a response in multiple steps.
If true, the user has write access to the chat.
Arbitrary key-value data associated with this chat.