Skip to main content

​
Base URL

https://magic-meal-kits-xxxxx.run.app/api/v1
Replace the host with your deployment’s Cloud Run URL. Some features live under /api/v2/notion and /api/v3/notion.

​
Conventions

  • Auth: X-API-KEY header on every request (see Authentication).
  • Errors: { "success": false, "error": "..." } with standard HTTP status codes.
  • Compatibility: shipped request/response shapes are kept backward compatible — new behavior is opt-in via a query param or flag. Existing callers keep their wire contract.

​
Documented groups

Skeleton page. Per-group reference pages and the interactive OpenAPI playground land in follow-up PRs. The groupings below are the planned public surface — adjust the public/private split before authoring.

​
Core (planned: documented + interactive playground)

The broadly useful, stable endpoints most automations are built on:
  • Documents & media — PDF, YouTube, Transcription, Video
  • Content & utilities — Notion (bulk ops, AI summary, data sources, official API), Slack (markdown → blocks), JSON extract, ISO 8601, Parser, JavaScript execution
  • Social & messaging — Threads, Plaud, Tiro

​
Vertical / regional integrations (planned: documented)

Narrower-audience integrations, grouped separately:
  • Naver Commerce, Naver Blog, Coupang, Imweb, Skool, Solapi, Kakao, Paymint, Remember

​
Internal (not published)

Operational and transport endpoints intentionally kept out of the public reference — OAuth2 token internals, the MCP JSON-RPC transport (covered in the MCP tab instead), the Make.com RPC passthrough, Cloud Tasks plumbing, and license/activation endpoints.