Developer API v1 & PAT
Read and write page drafts; scopes and expiry are managed in the panel, revocation too.
Developers
Connect Tecof to your own tools with the Developer API, webhooks and @tecof/mcp
Access Developer API v1 with a PAT, receive events through signed webhooks, edit theme code in the Cloud IDE and draft pages from Claude Code, Codex or Gemini.
Developer surface
Extend without breaking the standard flow; you own the theme code, publishing always happens from the panel.
API v1
/api/v1/* endpoints with a PAT
PAT
pages:read · pages:write scopes; time-limited, revocable
HMAC
X-Webhook-Event header and signature verification
@tecof/mcp
Claude Code · Codex · Gemini CLI
Capabilities
Full control when code is required
Six developer surfaces; all of them work within the same account and plan scope.
Webhooks
Order, customer and content events to your own system; verified with an HMAC signature.
Cloud IDE code access
Edit theme code from the browser; add Studio-compatible sections and elements.
@tecof/mcp
Draft pages from Claude Code, Codex or Gemini CLI; the theme catalog is read from disk.
Headless usage
Fetch content and product data from the API and render it in your own front end.
Theme code & components
Section = layout + slots, element = content. Register your own component and use it in Studio.
Getting started
Two files: one request, one .mcp.json
Get the PAT from the panel (Settings → Developer / API Keys), send the request with a Bearer header; for MCP a .mcp.json is enough.
Authentication
Authorization: Bearer tcf_… header; the key is stored hashed on the server.
Scopes
pages:read and pages:write; team membership is rechecked on every request.
Expiry & revocation
30, 90, 180 or 365 days; revoke instantly from the panel.
Store context
The key is bound to the user and the store; you do not need to send a store ID separately.
Developer API v1 · .mcp.json
# GET /api/v1/pages — sayfa taslaklarını listeleyin (PAT, scope: pages:read)curl -s "$TECOF_API_URL/api/v1/pages?themeId=$TECOF_THEME_ID" \ -H "Authorization: Bearer $TECOF_API_TOKEN" # .mcp.json — Claude Code / Codex / Gemini CLI'dan sayfa taslağı{ "mcpServers": { "tecof": { "type": "stdio", "command": "npx", "args": ["-y", "@tecof/mcp@latest"] } }}Page drafts with MCP
Get a PAT, set up MCP, write the first draft
Three steps; the draft appears in Studio, the publish decision stays in the panel.
01
Create a PAT in the panel
Settings → Developer / API Keys; pick the pages:read and pages:write scopes and the expiry.
02
Add @tecof/mcp with .mcp.json
Put a .mcp.json in your theme repo; Claude Code, Codex or Gemini CLI starts the server automatically.
03
Write a page draft
The agent builds the draft from the sections and elements in the theme catalog; you edit and publish in Studio.
Modules
Which plan includes which developer module?
API access, webhooks and Cloud IDE; each card shows the lowest plan that unlocks the module.
Loading module catalog
Frequently asked questions
Frequently asked by developers
If your question is not answered here, use the contact form.
Developer access
Set up the first site, unlock developer tools with your plan
Sign up, create a PAT in the panel and write the first draft with @tecof/mcp. Plan scope for developer modules is listed on the pricing page.
Developer API v1 · Webhooks · Cloud IDE · @tecof/mcp