Val Town Code SearchReturn to Val Town

82    // if we wanted to create a /lastUpdatedAt route,
83    // which would let us pass a val town bearer token, we could do that here
84    // gives us 10k API requests per minute instead of 1k
85    // and would work with private projects
86

19export const oldPosts: BlogPost[] = [
20  {
21    "title": "Solving the internal / external API riddle",
22    "slug": "api-conundrum",
23    "link": "/blog/api-conundrum",
24    "description": "Figuring out how to provide an API that's usable by everyone and fast for us to iterate on",
25    "pubDate": "Thu, 27 Mar 2025 00:00:00 GMT",
26    "author": "Tom MacWright",
27  },
28  {
29    "title": "API Tokens Scopes",
30    "slug": "api-token-scopes",
31    "link": "/blog/api-token-scopes",
32    "description": "Improving security with granular control over permissions",
33    "pubDate": "Fri, 01 Nov 2024 00:00:00 GMT",
59  },
60  {
61    "title": "Expanding the Vals API - RFC",
62    "slug": "expanding-the-vals-api-rfc",
63    "link": "/blog/expanding-the-vals-api-rfc",
64    "description": "Our REST API lets you do a lot - and soon it will enable more",
65    "pubDate": "Fri, 30 Jun 2023 00:00:00 GMT",
66    "author": "André Terron",
133  },
134  {
135    "title": "The perks of a good OpenAPI spec",
136    "slug": "openapi",
137    "link": "/blog/openapi",
138    "description": "Taking advantage of our typed REST API to build a platform around\nVal Town.",
139    "pubDate": "Thu, 25 Jul 2024 00:00:00 GMT",
140    "author": "Tom MacWright",
262  },
263  {
264    "title": "The API we forgot to name",
265    "slug": "the-api-we-forgot-to-name",
266    "link": "/blog/the-api-we-forgot-to-name",
267    "description": "An API that takes a Request and returns a Response - what was that, again?",
268    "pubDate": "Thu, 19 Oct 2023 00:00:00 GMT",
269    "author": "Steve Krouse",
286  },
287  {
288    "title": "Deprecating the Run API",
289    "slug": "deprecating-the-run-api",
290    "link": "/blog/deprecating-the-run-api",
291    "description": "Not every function should be an API",
292    "pubDate": "Wed, 07 Feb 2024 00:00:00 GMT",
293    "author": "André Terron",
321    "slug": "val-town-newsletter-1",
322    "link": "/blog/val-town-newsletter-1",
323    "description": "Programmatic notifications, Hacker News API, and more.",
324    "pubDate": "Wed, 04 Jan 2023 00:00:00 GMT",
325    "author": "Steve Krouse",
450    "slug": "val-town-newsletter-22",
451    "link": "/blog/val-town-newsletter-22",
452    "description": "Townie upgrades, Scoped API permissions, Fal partnership",
453    "pubDate": "Mon, 02 Dec 2024 00:00:00 GMT",
454    "author": "Steve Krouse",

8Today, we’re unifying our two primitives — *vals* and *projects* — into a single primitive: the **val**, with the best features of both.
9
10Historically, vals have been simple and lightweight, but limited to a single file. This upgrade will preserve the elegant spirit of our platform while supporting more complex code and collaborative workflows. This upgrade will help you create bigger things on Val Town – APIs, internal tools, fullstack apps, blogs ([like this one](https://www.val.town/x/valdottown/blog)), and much more – without sacrificing the simplicity you've always loved about vals.
11
12*Legacy vals* will temporarily become *projects* during this migration. Post-migration, the concept of *projects* will disappear entirely — leaving only upgraded *vals*. In short: *legacy vals* → *projects* → *vals*.
16For most users, no upgrade action is required. We’ll auto-migrate your vals next week. All existing HTTP endpoints, crons, email handlers, and custom domains will be preserved.
17
18For those with mission-critical vals or who use our API to edit or create vals, you can start upgrading your legacy vals today and integrating with our updated API.
19
20- **April 23, 2025** – Announcement of changes & API deprecations.
21- **April 30, 2025** – All remaining *legacy vals* auto-upgraded. Deprecated API routes become read-only.
22- **May 1, 2025** – The term *projects* will no longer exist — everything will simply be a *val*.
23
35[See more details in our docs.](https://docs.val.town/upgrading/legacy-vals)
36
37## API Changes
38
39Today, we're introducing the following API routes:
40
41```bash
73```
74
75View our [updated API reference here](https://docs.val.town/openapi).
76
77All `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. All deprecated API routes will continue serving historical legacy val data.
78
79### SDK changes
85
861. Upgrade your mission-critical vals early.
872. Update your Val Town API & SDK usage to `/v2` routes.
883. All remaining legacy vals migrate on **April 30, 2025**.
894. Migration completes on **May 1, 2025**.

83We didn't. We left them where they are, and proxy to them.
84
85Writing a proxy in Val Town (or any functions platform with the ['fetch handler' interface](https://blog.val.town/blog/the-api-we-forgot-to-name/)) is a delight:
86
87```ts

14app.get("/frontend/**/*", c => serveFile(c.req.path, import.meta.url));
15
16// Add your API routes here
17// app.get("/api/data", c => c.json({ hello: "world" }));
18
19// Unwrap and rethrow Hono errors as the original error

12app.get("/frontend/**/*", c => serveFile(c.req.path, import.meta.url));
13
14// Add your API routes here
15// app.get("/api/data", c => c.json({ hello: "world" }));
16
17// Unwrap and rethrow Hono errors as the original error

79  // This is a no-op if nothing's changed
80  if (!isEndpointSet) {
81    await bot.api.setWebhook(req.url, {
82      secret_token: SECRET_TOKEN,
83    });

79  // This is a no-op if nothing's changed
80  if (!isEndpointSet) {
81    await bot.api.setWebhook(req.url, {
82      secret_token: SECRET_TOKEN,
83    });

2import moment from "npm:moment-timezone";
3
4// Reddit API credentials
5const clientId = "-ngsEqbToTa_FlVv-Uy28g";
6const clientSecret = "iE3aFgBYsZvCZmyLWOlAhI9pFAQ2-g";
9async function getAccessToken() {
10  const response = await axios.post(
11    "https://www.reddit.com/api/v1/access_token",
12    new URLSearchParams({
13      grant_type: "client_credentials", // Use client credentials flow

8## Hono
9
10This app uses [Hono](https://hono.dev/) as the API framework. You can think of Hono as a replacement for [ExpressJS](https://expressjs.com/) that works in serverless environments like Val Town or Cloudflare Workers. If you come from Python or Ruby, Hono is also a lot like [Flask](https://github.com/pallets/flask) or [Sinatra](https://github.com/sinatra/sinatra), respectively.
11
12## Serving assets to the frontend
20### `index.html`
21
22The most complicated part of this backend API is serving index.html. In this app (like most apps) we serve it at the root, ie `GET /`. 
23
24We *bootstrap* `index.html` with some initial data from the server, so that it gets dynamically injected JSON data without having to make another round-trip request to the server to get that data on the frontend. This is a common pattern for client-side rendered apps.
25
26## CRUD API Routes
27
28This app has two CRUD API routes: for reading and inserting into the messages table. They both speak JSON, which is standard. They import their functions from `/backend/database/queries.ts`. These routes are called from the React app to refresh and update data.
29
30## Errors
31
32Hono and other API frameworks have a habit of swallowing up Errors. We turn off this default behavior by re-throwing errors, because we think most of the time you'll want to see the full stack trace instead of merely "Internal Server Error". You can customize how you want errors to appear.