Endpoints

An endpoint is a live public URL bound to a workflow. A visitor hits the address, the workflow runs, and its result is served: a page or a data response, whatever the workflow returns. Endpoints are how anything on Tessryx becomes reachable on the web.

#What one endpoint holds

• A workflow: the logic that produces the response.
• Optionally, a content record bound as the workflow's data, so a page renders from it server-side. (Or the workflow fetches its own data, or the page loads it in the browser.)
• Methods: GET to serve; add POST to accept a submitted form or API call. Any other method gets a 405.
• Input: how the workflow's input is supplied (below).
• Caching: how long a result is reused (below).

#Pages and API routes

An endpoint covers both halves of a site:

• Pages: the HTML a visitor sees.
• API routes: the addresses a page's own buttons and forms call to do things (submit, load more, take a payment). A page and the routes it calls are all endpoints.

#Input and path parameters

An endpoint decides what input its workflow receives:

• None: a plain page that needs nothing.
• Static: a fixed input on every request.
• From the request: built from the URL. This is how one endpoint serves many pages: a slug like post/:slug captures the part after post/ and hands it to the workflow, so a single endpoint renders every blog post. A POST's submitted body can be mapped in the same way.

A malformed or unmatched URL is served as a 404: a bad address reads as "no such page," never an error that reveals how the route works.

#Caching

Caching is the biggest lever on speed and cost. An endpoint sets how long the edge may serve a cached copy:

• Cache time: how long a built page is reused before it's rebuilt. It's also how long an edit takes to appear, so keep it short while iterating (0–30s) and raise it once the page has settled (minutes to an hour).
• Serve-stale window: after the cache time lapses, keep showing the last version instantly while the next rebuilds in the background, so nobody waits.

No caching means a workflow run (and a credit) on every visit. Nothing clears a cached page on demand, so the cache time is a promise: it's the longest a change can take to show. See Credits and caching.

#Requiring sign-in

An endpoint can require a Tessryx sign-in before it serves anything. On its own that's a plain login wall: any signed-in account is let in. You can narrow it to members of your workspace holding a given role, and choose what a denied or not-signed-in visitor sees (a 403, a redirect, a login prompt, or a 401 for an API route). A gated endpoint is never shared-cached (its caching becomes browser-only), so one visitor's page is never handed to another.

#On the default address

Until you add a custom domain, a site serves from a yourname.tessryx.app address. There, pages carry a small "Served by Tessryx" badge, aren't indexed by search engines, and use the platform's robots file. All three lift the moment you serve from your own domain.