vt-blog

Today, we’re unifying our two primitives—vals and projects—into a single primitive: the val, with the best features of both.

This upgrade helps you organize complex projects more intuitively by supporting multiple files, folders, and streamlined collaboration, without sacrificing the simplicity you've always loved about Val Town.

Vals have been known for being simple and lightweight, but limited to a single file. This upgrade preserves the elegant spirit of our platform while supporting more complex code structures, including collaborative workflows with branches and pull requests.

Under the hood, legacy vals will temporarily become projects during migration. Post-migration, the concept of projects disappears entirely—leaving only upgraded, flexible vals. In short: legacy vals → projects → vals.

For most users, no upgrade action is required—we’ll auto-migrate your vals next week.

For those with mission-critical vals or who edit/create vals through our API, you can begin upgrading your legacy vals today and integrating with our new API.

• April 24, 2025 – Announcement of changes & API deprecations.
• April 30, 2025 – All remaining legacy vals auto-upgraded. Deprecated API routes become read-only.
• May 1, 2025 – The term projects will no longer exist—everything will simply be a val.

All legacy vals will automatically upgrade on April 30, 2025.

You can proactively upgrade by:

• Going to the Settings of any legacy val.
• Clicking Upgrade.

See detailed instructions in our docs.

We've streamlined our API for better consistency, flexibility, and performance. Today we introduce the following API routes:

GET /v2/vals/{val_id}
DELETE /v2/vals/{val_id}
GET /v2/vals
POST /v2/vals
GET /v2/vals/{val_id}/branches/{branch_id}
DELETE /v2/vals/{val_id}/branches/{branch_id}
GET /v2/vals/{val_id}/branches
POST /v2/vals/{val_id}/branches
GET /v2/vals/{val_id}/files
POST /v2/vals/{val_id}/files
DELETE /v2/vals/{val_id}/files
PUT /v2/vals/{val_id}/files
GET /v2/vals/{val_id}/files/content

GET /v2/alias/vals/{username}/{val_name}
GET /v2/me/vals

We are deprecating these API routes:

*   /v1/vals/*
*  /v1/projects/*
GET /v1/alias/{username}/{val_name}
GET /v1/alias/projects/{username}/{project_name}
GET /v1/me/comments
GET /v1/me/references
GET /v1/me/likes
GET /v1/me/projects
GET /v1/users/{user_id}/vals

View our updated API reference here.

We've also released a new version of the Val Town SDK, v0.39.0, using these new endpoints.

All v1/vals API routes become read-only on April 30, 2025. If you rely on writing to those routes, please upgrade to our new v2/vals API routes before then. All deprecated API routes will continue serving historical legacy val data until further notice.

1. Upgrade your mission-critical vals early.
2. Update your Val Town SDK & API usage to /v2 routes.
3. All remaining legacy vals migrate on April 30, 2025.
4. Migration completes on May 1, 2025.

We're committed to making this transition smooth for you—reach out anytime via email or Discord if you need assistance. We appreciate your help and patience through this migration. Good stuff is on the other side!