EasySiteControl
Custom API endpoints
Design your own API routes on a visual canvas — no server code, no glue layer.
What you get
- Your own routes at /fn/<slug> — GET, POST, PUT or DELETE
- Steps on a canvas: query records (with relation expansion), transform with JMESPath, conditions, HTTP calls, email
- Three access modes: public, API key, or your site's logged-in end users
- Per-endpoint CORS, response caching, custom status, content types and headers
- Test-run unsaved drafts and read step-by-step execution logs
The endpoint your page actually needs
Instead of stitching three API calls together in the browser, define one route that queries articles, expands each author, filters to what's live and returns exactly the JSON your page renders. The logic lives server-side, the response is cacheable, and the browser makes one request.
Serious enough for production
Endpoints answer with proper failure semantics — validation stops with your configured response, internal errors stay opaque with a traceable execution id — and every invocation is logged step by step. Content types beyond JSON mean a flow can serve an RSS feed, a sitemap or a rendered HTML fragment directly.