Quickstart
This guide takes you from a fresh Mojimoto project to live content you can fetch from your own front end. You will model a content type, add and publish an entry, then read it back over the delivery API with the public read token every project already has.
1. Create a space
Sign up and create your first project — a space is where one site or app lives. Every space starts on a 14-day free trial with no card required, and comes with a default Production environment and an en-gb locale.
2. Model a content type
Open Content model and add a type. A "collection" holds many entries (like Blog post or Team member); a "single" holds exactly one (like Site settings). Give it a few typed fields — a Short text for the title, a Slug so it is addressable, and a Rich text for the body.
Field changes save the moment you make them — there is no separate "save schema" step to forget.
3. Add and publish an entry
Switch to Content, create an entry of your new type, fill in the fields, and press Publish. Drafts auto-save as you type; publishing is what makes an entry visible to the delivery API.
4. Fetch it from your front end
Every space carries a permanent public read token (find it on the API keys page). Published content is public, so this token is safe to ship. Read your entries with a single GET request:
curl https://your-domain.com/api/v1/your-project/documents \ -H "Authorization: Bearer mjmt_your_public_read_token"
You get back a typed, predictable JSON document for each published entry — the shape mirrors the model you designed:
{
"results": [
{
"id": 42,
"uid": "hello-world",
"type": "blog_post",
"lang": "en-gb",
"status": "published",
"data": { "title": "Hello world", "body": "<p>…</p>" }
}
],
"total_results": 1,
"page": 1,
"per_page": 20,
"lang": "en-gb"
}
Where to next
That is the whole loop: model, publish, fetch. From here, learn to shape your model properly, query exactly what you need, and wire publishing to rebuild your site.
Design content types with typed fields, reusable components, and references — a model your front end can rely on.
Query published content by type, slug and locale, paginate, sort, and resolve references — all from one REST endpoint.
Fire an outbound, HMAC-signed webhook when content is published — to rebuild a static site or sync an integration.