Feature Request: Oxen Tree API

[type-checker]

Oxen Tree API

• [ ] Support for a GitHub-like tree API for Oxen Tree API.

[jcelliott]

Do you have specific features from that you want to use? We already support a lot of similar operations with the /dir, /file, and /meta endpoints.

[type-checker]

Do you have specific features from that you want to use? We already support a lot of similar operations with the /dir, /file, and /meta endpoints.

Hi @jcelliott I’ve tried these endpoints, but they don’t return the full file and directory tree of an Oxen repository. We need an endpoint similar to GitHub’s https://api.github.com/repos/vercel/next.js/git/trees/canary?recursive=1 for Oxen, which can provide the entire file structure—including all nested files and folders—in a single, paginated response.

Key uses:

• Programmatically list all files and directories in a repository without cloning it locally.
• Obtain metadata for each file and directory, such as path, type (file or folder), size, and SHA.
• Automate workflows that require knowledge of the repository’s file organization, such as code analysis, documentation generation, or custom deployment scripts.

We require a global file search capability for our AI video platform, enabling us to list, search, and manage users generated images and videos, including their version history. The Oxen Tree API can facilitate this by providing efficient access to the repository’s full file structure and versioning information.