API Keys
API keys are used when your website, app, or other external system needs to request content from Contismo.
They provide authenticated access outside the Studio and should be handled securely.
Key types
Section titled “Key types”Contismo supports GraphQL keys for websites and apps, and MCP keys for AI clients.
| Type | Prefix | Access |
|---|---|---|
| GraphQL - Read Only | gql_ |
Query content via GraphQL |
| GraphQL - Read/Write | gqlw_ |
Query content and run GraphQL mutations for content models, entries, and assets (create, update, delete, and status changes) |
| MCP - Read Only | mcp_ |
Read content through the MCP server |
| MCP - Read/Write | mcpw_ |
Create, update, and delete entries through the MCP server when writes are enabled |
Read/write keys cannot manage team members, billing, webhooks, or other API keys. GraphQL keys do not work on the MCP server, and MCP keys do not work on GraphQL.
Create an API key
Section titled “Create an API key”To create a new API key:
- Go to Settings → API Keys.
- Click Create API Key.
- Enter a name that helps you identify where the key will be used.
- Choose a GraphQL or MCP key type.
- Copy the key and store it somewhere safe.
Use the key
Section titled “Use the key”Include the API key in the Authorization header when making GraphQL requests. Also send the environment in the X-Environment header:
Authorization: Bearer <your-api-key>X-Environment: <environment-api-id>Read-only GraphQL keys can run queries. Read/write GraphQL keys can also run mutations — see the GraphQL API reference.
MCP keys use the same headers against the MCP endpoint. Configure models, drafts, and writes in MCP settings, then see the MCP server reference for tools and a client example.