genko.me basics
How workspaces, APIs, and content fit together, and where to start reading.
genko.me is a headless CMS. You edit text and images in the dashboard, and an API delivers them to your website or app. In Next.js, the SDK fetches the content and renders the HTML, and your site's CSS handles the design.
Editors create and publish entries in the dashboard. Developers fetch those entries through the API or the SDK. You can update posts and announcements without changing your site's code each time.
Where to start
| I want to... | Start here |
|---|---|
| Create my first entry and fetch it from an app | Quickstart |
| Learn how to write and publish | Create and publish content |
| Design fields such as title and body | APIs and schemas / Fields |
| Connect an existing app | Display content with List and View / Client configuration |
| Fetch over HTTP without the SDK | REST API |
| Edit with other people | Teams and members |
| Issue an API key | Manage API keys |
| Find settings or plan screens | Workspace settings / Plans and limits |
| Fix an error | Troubleshooting |
How content reaches your site
- Choose a workspace. It is a personal or team space for your work.
- Create an API. Make one for each kind of content, such as a blog, announcements, or a profile.
- Define the schema. Set up fields such as title, body, and images.
- Save and publish an entry. Enter the draft according to the schema.
- Fetch it from your site. On the server, use your API key to fetch published content as JSON.
Terms
| Term | Meaning | Example |
|---|---|---|
| Workspace | The unit that holds APIs, media, and members. It can be personal or a team | your-workspace |
| Workspace ID | The identifier used in dashboard and delivery API URLs | your-workspace (the dashboard is at genko.me/w/your-workspace) |
| API | A group of content that shares one structure | Blog |
| Endpoint | The name you use to refer to an API in a URL or the SDK | blog |
| Schema | The fields an API accepts, with their types and constraints | Title is text, body is rich text |
| Field ID | The field name used as a JSON key and in code | title, body |
| Content / entry | One saved piece of content | One blog post |
| Entry ID | An identifier generated as a 12-character alphanumeric string on save. You can change it in entry settings; it is the id in delivery responses | abcDEF123456 |
The name shown in the dashboard and the ID you use in code are separate. For example, if you set the display name to "Post title" but the field ID is title, you read it as post.title.
Dashboard vs. delivery API
In the dashboard, you read and write content according to the permissions of the account you signed in with. The delivery API is a read-only entry point authenticated with an API key, and it normally returns only content that meets the publishing conditions.
Check drafts with preview. Having a delivery API key does not let you list every draft.
Images and files are served by URL. Unpublishing content is not the same as blocking access to a file. See Manage media as well.
Last updated: October 16, 2026