REST API & API keys: Mesa

Content for any frontend

Mesa provides your published content via a clean interface (API), which your website, app or shop fetches and displays. That's the core of the “headless” principle: maintaining happens in Mesa, displaying in the frontend of your choice (e.g. Next.js, Nuxt, Astro).

What this means for you

You're not tied to a particular look. The same content can feed a website, an app and a shop, and when you renew the design someday, the content stays where it is.

Access under control

Access runs via keys (API keys) with adjustable rights. You create one key per application and can revoke it at any time: delivery stays under your control.

Cleanly documented

For developers it's clearly documented for each content area how to fetch it: no guessing, no back-and-forth questions. That makes connecting a new frontend a routine instead of a project.