docs/1.26/prisma-graphql-api/index.mdx
import Collapse from 'components/Markdown/Collapse' import Warning from 'components/Markdown/Warning'
export const meta = { title: 'Prisma GraphQL API', position: 5 }
Prisma uses GraphQL as a wire protocol. This means a Prisma service exposes a GraphQL API with CRUD and realtime operations for the service's models. This GraphQL API is not directly consumed by your frontend/mobile applications, instead you're consuming it through the Prisma client inside your application (e.g. to implement a web server with a GraphQL or REST API).
The GraphQL schema defining the types and operations of the Prisma GraphQL API is auto-generated based on the datamodel.
There are still some use cases where it can be appropriate to consume the Prisma GraphQL API directly:
| Page | Description |
|---|---|
| Concepts | Learn about the most important API concepts such as batching, Relay connections, transactions, cascading deletes, .. |
| Authentication | Learn how to protect your Prisma API using the service secret |
| Queries | Learn about the auto-generated queries in the Prisma API |
| Mutations | Learn about the auto-generated mutations in the Prisma API |
| Subscriptions | Learn about the auto-generated subscriptions in the Prisma API |
| Error Handling | Learn how Prisma deals with errors in API requests |
| Page | Description |
|---|---|
| Using the Prisma GraphQL API | Learn about various ways to consume the Prisma GraphQL API |
| Page | Description |
|---|---|
| Overview | Learn what Prisma bindings are and how they can be used to build GraphQL servers |
| Reference | API reference for Prisma bindings |