You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue tracks support for a official Sourcebot REST API. By "official", I mostly mean a documented API with a defined api surface, usage examples, etc. Having an official API would be a precursor to developing new Sourcebot clients (e.g., a CLI), as well as unlocking various automation scenarios.
Hey @brendan-kellam this appears to be like an overhead (enhancement) issue preventing the team from working on main features of Sourcebot, if that is the case I can pick this up end to end.
Any estimated deadline? or I can take my time with this. Don't want to be blocking releases.
Any status on this? Is this open for contributors to attempt? I was thinking zod -> OpenAPI 3.0 spec generation, and then just documentation. What else would be missing? I ask because this would unblock CLI implementation.
@KonradStanski yea that would be great and actually very helpful. I think the approach of having zod -> OpenAI spec would be ideal. Alternatively, you could do OpenAI spec -> zod, but no strong opinions. Zod -> OpenAI might honestly be preferred since zod feels like a better form-factor.
Activity
chore(api): Changed the search api to return raw source (instead of b…
prateek041 commentedon Oct 14, 2025
Hey @brendan-kellam this appears to be like an overhead (enhancement) issue preventing the team from working on main features of Sourcebot, if that is the case I can pick this up end to end.
Any estimated deadline? or I can take my time with this. Don't want to be blocking releases.
[-]Sourcebot REST API support[/-][+][FR] Sourcebot REST API support[/+]KonradStanski commentedon Mar 9, 2026
Any status on this? Is this open for contributors to attempt? I was thinking zod -> OpenAPI 3.0 spec generation, and then just documentation. What else would be missing? I ask because this would unblock CLI implementation.
brendan-kellam commentedon Mar 9, 2026
@KonradStanski yea that would be great and actually very helpful. I think the approach of having zod -> OpenAI spec would be ideal. Alternatively, you could do OpenAI spec -> zod, but no strong opinions. Zod -> OpenAI might honestly be preferred since zod feels like a better form-factor.
For docs, Mintlify has the concept of API docs that take a OpenAI spec and generate the docs: https://www.mintlify.com/docs/api-playground/openapi-setup