Introduction

Snaapi turns structured data into production-ready APIs and MCP servers. You define the shape of your data (resources, fields, relations, permissions), and Snaapi gives you a deployable backend with authentication, documentation, admin tooling, audit logging, webhooks, and real-time event streams built in.

What problems does Snaapi solve?

Most teams ship the same set of "boring but required" pieces on every new backend.

• An auth system with users, sessions, roles, and password resets.
• A schema migration story.
• A documentation page non-technical stakeholders can read.
• An OpenAPI spec developers can import into their tools.
• Webhook delivery with retries.
• Audit logs that capture who did what.
• A way to invite teammates and manage access.

Snaapi provides all of these as platform features. You define your data model once, and the rest is generated.

Who uses Snaapi?

Snaapi is built for mixed teams. The visual builder is approachable for non-engineers (product managers, ops, data teams) who own the data model. The generated API and OpenAPI spec drop into any developer workflow.

How is this documentation organized?

• Quickstart walks through creating your first organization, API, resources, and roles end to end.
• Concepts explains the building blocks: resources, fields, content types, and relations.
• Access control covers authentication, API keys, roles, and the three-layer permission model.
• API documents the generated REST surface, filtering and pagination, and the OpenAPI spec.
• Events describes the event payloads, webhook delivery, and Server-Sent Events streaming.
• Tools covers importing and exporting resources, fields, roles, and permissions between APIs.
• AI covers Ask AI in the console and the built-in MCP server for Claude, Cursor, and other MCP clients.

If you are getting started, the Quickstart is the fastest path to a working API.