v0-sdk

This PR introduces an optional parameter to the v0 SDK, enabling more flexible request customization. Problem/Issue/Goal: The v0 SDK lacked a mechanism to include custom HTTP headers in requests. Users needed the ability to pass specific headers for various use cases (e.g., authentication, custom metadata). Fix/Solution: Extended and to include an optional parameter. This allows developers to define and send custom headers with requests made via the v0 SDK. Chat link: https://v0.app/chat/33LFeJPhvrO

Description When initializing chats via the v0 SDK using ZIP archive initialization ( with ), the created chat automatically enters v0 Beta mode. In this mode, the returned by the Platform API consistently returns HTTP 404, preventing us from displaying previews to our users. Environment SDK Version: v0.15.1 React SDK Version: v0.4.0 Backend: Node.js / NestJS Steps to Reproduce 1. Create a project via 2. Initialize a chat with ZIP archive: 3. Access Expected Behavior Chat should operate in normal (non-beta) mode should be accessible and return HTTP 200 with preview content Actual Behavior Chat enters "v0 beta" mode (UI shows: "This chat is on the v0 beta") returns HTTP 404 Subsequent calls to also return a 404 Business Impact This is a P0 production issue for us: Our product uses v0 SDK to power an App Builder feature with template-based app creation The preview functionality () is the core UX of this feature All template-based app creation is currently non-functional Multiple enterprise customers are affected No viable workaround has been identified Feature Request Please consider adding an API parameter (e.g., or ) that allows SDK consumers to explicitly opt out of beta features for production use cases. Additional Context We are happy to provide: Sample values for debugging Full request/response logs A call to discuss and reproduce the issue Thank you for your attention to this urgent matter.