Route
also: routes, routing, router, api route, route handler
The rule in your app that connects a web address to the code that should run for it, like sending /settings to the settings page.
A mapping from a URL path, and often an HTTP method, to a handler: a page to render or a function to run. Frameworks define routes through files and folders (Next.js) or in code (Express's app.get("/orders", ...)).
The directory board in an office lobby: "Accounts, 3rd floor. Support, 5th floor." The name you look up decides where you're sent.
"Page not found" after a change is often a routing problem. Knowing routes helps you ask an agent where a URL is handled, and whether a new page or endpoint was actually wired up.
The 404 happens because the route is defined as /api/workout but the app calls /api/workouts. I'll rename the route to match.
List every route in the app, which ones require the user to be logged in, and flag any that don't check.
Treating route and endpoint as always identical. An endpoint is the address a client calls; a route is the rule in your code that handles it. Routes can also serve pages.