Vashana
NO
All topics

API, MCP & multi-tenancy

Everything you can do in the Vashana UI can also be done programmatically — by your own code or by AI agents.

API keys

Get your API key under Developer tools → API Keys in your account menu. Send it in the X-API-KEY header:

curl -H "X-API-KEY: your-key" https://api.vashana.com/api/spaces

Regenerating the key invalidates the old one immediately — integrations using it must be updated.

REST API

The API covers the full platform: creations (spaces), content and files, publishing, design-system documents, brands, SEO metadata, translations, analytics, backups and more. The interactive reference lives at api.vashana.com/swagger-ui.html, with the raw OpenAPI spec at /v3/api-docs.

Typical automation examples:

  • create a space and upload content, then publish it,
  • update a page's design-system document and republish,
  • set a page's title, description and Open Graph tags, then regenerate the sitemap,
  • manage password protection or backups from CI.

MCP server

Vashana ships a Model Context Protocol server so AI assistants can build and manage sites on your behalf:

  • https://mcp.vashana.com/mcp

One endpoint serves every client — ChatGPT, Claude and anything else that speaks MCP. Connect it in your client, authenticate with your Vashana account, and the assistant gets tools for the whole loop: list your brands and sites, build a new one and follow the build, read and edit the site document, generate images, upload and protect files, and publish — with interactive UI where the client supports it.

AI work started this way draws on the same credit balance as the editor.

Multi-tenancy

Building a product on top of Vashana? Spaces support optional tenant isolation: pass an X-Tenant-Key header (any UUID you manage) when creating and accessing content, and data under different tenant keys is kept strictly separate within the same space. This lets one Vashana account serve many of your end customers.