HoplaDocs

REST API and MCP server · Hopla Pro

Hopla API and MCP server

Everything the admin panel does, available through the REST API and the MCP server: page, blocks, images, analytics, email list.

29
endpoints
25
MCP tools
120
requests per minute
curl -X POST https://app.hopla.page/api/v2/blocks \
  -H "Authorization: Bearer $HOPLA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"title": "My podcast",
       "url": "https://example.com/podcast"}'
201{ "block": { "id": "a1b2c3d4e5f6", "title": "My podcast", … } }

Resources

Every endpoint is documented in the API reference, with an interactive console.

Page

Full page and its settings: profile, theme, social links, colors, SEO.

Blocks

Page blocks: links, headings, text, videos, products, FAQ…

Analytics

Views, visitors and clicks, cookieless: visitor IP addresses are never stored.

Sharing

QR code of the page.

Images

Upload images for profile photos, thumbnails, galleries or backgrounds.

Email list

Subscribers collected by the email signup block: list, export, delete, sync to a newsletter.

Web fetching

Metadata the admin panel reads from a pasted URL: website title and image, feed posts, review rating.

Account

Plan, trial, included features, API keys and data export.

Reference values

Valid values for themes, social networks, icons and block types.

Key concepts

Base URLs

REST APIhttps://app.hopla.page/api/v2
MCP serverhttps://app.hopla.page/mcp
OpenAPI spechopla.page/docs/openapi.json, for client generation
AI agentshopla.page/docs/llms.txt, and the full documentation in llms-full.txt

Versions

This documentation covers API v2. API v1 (/api/v1), released on October 28, 2026 with French field names, remains supported for existing integrations: see Migrating from v1.

Every page of this documentation is available as Markdown: use Copy Markdown to pass it to an agent as is.