Working with kirby is very much like if you were working with nosql db where every record by default is also URL/route endpoint (it does not have to be you can have all routing you want).
You don't have to output HTML. Kirby does not enforce templating engine so you can straight up output json on those routes.
This has been always possible with kirby.
Working with kirby is very much like if you were working with nosql db where every record by default is also URL/route endpoint (it does not have to be you can have all routing you want).
You don't have to output HTML. Kirby does not enforce templating engine so you can straight up output json on those routes.
But there might be even better ways
Make your own route endpoints https://getkirby.com/docs/guide/routing this is almost identical to how you do it in expressjs or slim
Content representations - https://getkirby.com/docs/guide/templates/content-representations - you might output multiple things at once. /calendar will be html page /calendar.json will be the same thing in json.