---
sidebar_position: 1
title: Automate components from your backend
sidebar_label: Automate from your backend
description: Create, clone, publish and update Myop components and flows from your own backend, CMS or internal tools with an organization API key — no dashboard, no redeploy.
keywords: [myop management api, automate ui components, update components from backend, headless component management, publish ui without deploy, programmatic component updates, marketing automation ui, iframe components api]
---
# Automate components from your backend

Teams that change their UI often (campaigns, onboarding pages, referral programs) usually already have
a system where that work starts: a CMS, a campaign tool, an internal operations console. With the Myop
management API, that system can make the change in Myop directly. No one opens the dashboard and
nothing is redeployed.

## What you can do

| Task | What happens |
|---|---|
| **Clone a component** | Copy an existing component, keep its props and behavior, and give it new content, for example a new campaign URL |
| **Add it to a flow** | Put the component on a page (a flow), or create a new flow for it |
| **Publish** | Make the change live; visitors get it on their next page load |
| **Update** | Point a component at new content; every flow that uses it updates at once |
| **Remove** | Take a component off a flow |
| **List and read** | See your organization's components and what each flow serves |

All of it is plain HTTPS with JSON, called from your server.

## A typical automation

A marketing team launches a new referral page every few weeks. Their operations tool now does it in one
step:

1. Clone the existing referral component, with the new landing page as its content.
2. Add the clone to the referral flow and publish it.
3. When the campaign ends, update the URL or remove the component from the flow.

In code, each step is one call:

```js
const myop = (method, path, body) =>
  fetch(`https://cloud.myop.dev${path}`, {
    method,
    headers: {
      Authorization: `Bearer ${process.env.MYOP_API_KEY}`,
      "Content-Type": "application/json",
    },
    body: body && JSON.stringify(body),
  }).then((res) => res.json());

const { item: component } = await myop("GET", `/component?id=${templateId}`);
// …give it the new URL, save it as a new component, add it to the flow
```

Enterprise customers get the full reference, with every endpoint and ready-to-use code for each task,
when access is turned on.

## How access works

- **Your key, your organization.** You create the key in the dashboard
  (**Rollout → Settings → Self-Hosting → API Keys**). It acts only inside your organization.
- **Change access is granted per key.** New keys can only export. Myop turns on the ability to change
  components and flows for the specific key you name, so a key used by your CI cannot change live content.
- **Server-side only.** Keep the key on your backend. Anyone holding it can change your live UI.
- **Revoke any time.** An organization admin can revoke the key in the dashboard; it stops working
  immediately.
- **Every change is attributed** to the key that made it.

## What it covers

The management API works with the components and flows your team already runs, including components
that load your own pages in an iframe. HTML components built with AI are created and published through
the [Myop MCP server](/docs/mcp-setup).

## Get access

The management API is available to enterprise organizations.
[Book a technical intro](https://calendly.com/hadar-myop/myop-technical-intro) and we'll turn it on for
your key and send you the full reference.