Skip to content

Developer documentation

One platform.
Four ways to build.

Use REST for structured integrations, MCP for AI agents, the Theme API for presentation, and plugins for site behavior. Explore the versioned contracts and availability of each surface.

Explore REST API Connect an AI agent Read Plugin API v1 docs
eyivo / developer
GET /api/v1/sites 200
POST /api/v1/sites/{site}/pages 201
MCP list-sites-tool ok
REST API v1 Theme API v1 MCP v1 Plugin API v1

Start building

Choose your integration surface.

Each guide starts with the contract, then moves through setup, working examples, validation, and production behavior.

Available now v1 · Content API

REST API

Manage pages, components, blogs, products, galleries, videos, menus, media, forms and site settings through scoped content tools and REST endpoints.

  • Personal access tokens
  • OAuth 2.0 + PKCE
  • Scoped access
  • Idempotent writes
Read REST API v1 docs OpenAPI JSON
Available now v1 · Liquid

Theme API

Build portable themes with Liquid templates, structured settings, reusable components, and complete demo content.

  • Liquid templates
  • Theme settings
  • 29 shared components
  • Demo content
Read Theme API v1 docs Sample theme
Available now v1 · Tools and resources

MCP

Manage pages, components, blogs, products, galleries, videos, menus, media, forms and site settings through scoped content tools and REST endpoints.

  • Streamable HTTP
  • OAuth 2.0 + PKCE
  • Personal tokens
  • Site ownership
Read MCP v1 docs
Eyivo packages only Plugin API v1

Plugins

Extend site behavior through declared hooks, form validation, and a controlled API bridge. The v1 contract is public; installation currently supports Eyivo packages only.

  • Lifecycle hooks
  • Form validation
  • Panel pages
  • Restricted runtime
Read Plugin API v1 docs

Stable by design

Contracts developers can depend on.

Eyivo keeps its integration boundaries explicit, so your applications, agents, themes, and plugins are easier to test, upgrade, and operate.

01

Versioned surfaces

REST routes, theme manifests, and plugin manifests declare the contract version they target.

02

Least-privilege access

API credentials use explicit scopes and are limited to the authenticated account.

03

Machine-readable schemas

The OpenAPI 3.1 document is the canonical REST operation and schema reference.

04

Safe publishing

Content workflows separate changes from the public site where the contract requires it.