Documentation

Build and publish your live JSON endpoint quickly.

Start with the quickstart path, then use this reference to understand the publish workflow, endpoint behavior, and practical implementation patterns.

Open quickstart

How it works

Getting started

Create a workspace, add your first project, and define your field schema.

Draft then publish

Edit draft payloads safely, then publish snapshots when content is approved.

Stable endpoint

Call one protected live endpoint from apps, ads, kiosks, and web experiences.

Controlled updates

Keep business teams fast while avoiding full CMS and backend maintenance work.

Data model

One project maps to one JSON payload. You can combine primitives, primitive lists, and repeatable object groups while preserving predictable output shape.

  • Use draft mode for in-progress content and validation.
  • Publish creates a stable live snapshot for clients.
  • Rotate API keys without changing project IDs or endpoint URL.

Yeah, I need an API... but what is it?

Think of JSON like a labeled tool box where each label points to one value, like wrench, hammer, or drill. An API is the delivery helper that hands that tool box to your website or app when it asks to see your tools. An endpoint is the exact address your app calls to pick up that box to search your toolkit. With Simple Data API, you update your content, publish it, and every app using that endpoint gets the same fresh version.

Common use cases

Teams use Simple Data API for rapid content updates without CMS overhead.

Digital out-of-home (DOOH) content feeds

Agency client data feeds

Restaurant and menu boards

Website content feeds

Ecommerce lightweight feeds

Event and venue data

Franchise multi-location brands

Email and CRM content feeds

Mobile apps with lightweight backends

Social media curation

Landing page builders

A/B testing content variants

Internal tools for non-technical teams

Game and app config files

Education and campus systems

Travel and hospitality content