REST API · v1

API Documentation

Everything you need to integrate Multi-Site with your websites, apps, and automations. Read content, manage subscribers, send campaigns — all via a simple REST API.

Quick subscribebash

curl -X POST multi-site-manager.vercel.app/api/public/subscribe \
  -H "Authorization: Bearer YOUR_SITE_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"email": "hello@example.com", "tags": ["website"]}'

Overview

The Multi-Site Manager API lets you manage sites, contacts, content, and campaigns programmatically. There are two types of endpoints:

Public API — Designed for external websites to subscribe users. Authenticated via site API tokens.
Internal API — Used by the dashboard. No auth required in local development.

Base URL: $multi-site-manager.vercel.app/api

All request and response bodies use JSON. Set Content-Type: application/json on all requests.

Authentication

The public subscribe endpoint requires a site API token passed as a Bearer token in the Authorization header.

Each site has a unique API token generated automatically when the site is created. You can find it in the site overview page of the dashboard.

Header format

Authorization: Bearer YOUR_SITE_API_TOKEN

Keep your API tokens secret. Do not expose them in client-side JavaScript. Use them only in server-side code or secure environments.

Subscribe Endpoint

POST/api/public/subscribePublic

Subscribe a contact to a site. If the contact does not exist, it will be created. If it already exists, the existing contact will be linked to the site. If the contact is already linked, the status will be updated to subscribed.

Headers

Param	Type	Required	Description
Authorization	string	Yes	Bearer YOUR_SITE_API_TOKEN
Content-Type	string	Yes	application/json

Request Body

Param	Type	Required	Description
email	string	Yes	The contact's email address
name	string	No	The contact's display name
tags	string[]	No	Tag names to assign (created if they don't exist). Max 20 tags, 50 chars each

Example Request

cURLbash

curl -X POST multi-site-manager.vercel.app/api/public/subscribe \
  -H "Authorization: Bearer abc123def456..." \
  -H "Content-Type: application/json" \
  -d '{
    "email": "user@example.com",
    "name": "John Doe",
    "tags": ["website", "footer-form"]
  }'

Tracking tip: Use tags to track subscription sources (e.g. website, landing-page-xyz, google-ads). Tags are matched by name and created automatically if they don't exist. You can then filter contacts or send targeted campaigns to specific tags.

Success Response

200 OKjson

{
  "message": "Subscribed successfully"
}

Error Responses

401 Unauthorizedjson

{ "error": "Invalid API token" }

400 Bad Requestjson

{ "error": "email is required" }

Sites API

GET/api/sitesInternal

Returns a list of all sites, ordered by most recent first.

Example Responsejson

[
  {
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "name": "Pokennection",
    "slug": "pokennection",
    "api_token": "abc123...",
    "created_at": "2026-04-08T12:00:00.000Z"
  }
]

POST/api/sitesInternal

Create a new site.

Request Body

Param	Type	Required	Description
name	string	Yes	Display name for the site
slug	string	Yes	URL-safe identifier (unique)

cURLbash

curl -X POST multi-site-manager.vercel.app/api/sites \
  -H "Content-Type: application/json" \
  -d '{ "name": "Stay Tiny", "slug": "stay-tiny" }'

201 Createdjson

{
  "id": "...",
  "name": "Stay Tiny",
  "slug": "stay-tiny",
  "api_token": "generated-token-here",
  "created_at": "2026-04-08T12:00:00.000Z"
}

GET/api/sites/:siteIdInternal

Get a single site by ID.

Contacts API

GET/api/sites/:siteId/contactsInternal

List all contacts linked to a site, with their subscription status. Returns joined data including the contact's email and name.

Example Responsejson

[
  {
    "id": "site-contact-uuid",
    "site_id": "...",
    "contact_id": "...",
    "status": "subscribed",
    "created_at": "2026-04-08T12:00:00.000Z",
    "contact": {
      "id": "...",
      "email": "user@example.com",
      "name": "John Doe"
    }
  }
]

POST/api/sites/:siteId/contactsInternal

Manually add a contact to a site. If the email already exists globally, the existing contact will be reused. If already linked to this site, no duplicate is created.

Request Body

Param	Type	Required	Description
email	string	Yes	Contact email
name	string	No	Contact name

cURLbash

curl -X POST multi-site-manager.vercel.app/api/sites/SITE_ID/contacts \
  -H "Content-Type: application/json" \
  -d '{ "email": "new@example.com", "name": "Jane" }'

PATCH/api/sites/:siteId/contacts/:siteContactIdInternal

Update a contact's name or subscription status for this site.

Request Body

Param	Type	Required	Description
name	string	No	Update the contact's name
status	string	No	"subscribed" or "unsubscribed"

cURLbash

curl -X PATCH multi-site-manager.vercel.app/api/sites/SITE_ID/contacts/SC_ID \
  -H "Content-Type: application/json" \
  -d '{ "status": "unsubscribed" }'

Content Types API

Content types define custom schemas for your content. Each type has a set of fields that determine what metadata a content item can have. You can create types from predefined templates or build your own from scratch.

GET/api/content-type-templatesInternal

List available predefined templates (Blog Post, Devlog, Changelog, etc.).

GET/api/sites/:siteId/content-typesInternal

List all content types for a site, including their fields.

POST/api/sites/:siteId/content-typesInternal

Create a content type. Either from a template or from scratch.

From template

cURLbash

curl -X POST multi-site-manager.vercel.app/api/sites/SITE_ID/content-types \
  -H "Content-Type: application/json" \
  -d '{ "template": "blog-post" }'

Available templates: blog-post, devlog, changelog, page, newsletter, recipe, product-review.

Custom

cURLbash

curl -X POST multi-site-manager.vercel.app/api/sites/SITE_ID/content-types \
  -H "Content-Type: application/json" \
  -d '{ "name": "Game Review", "slug": "game-review", "description": "Reviews for games" }'

POST/api/sites/:siteId/content-types/:id/fieldsInternal

Add a field to a content type.

Request Body

Param	Type	Required	Description
name	string	Yes	Display name
slug	string	Yes	Identifier used in metadata
field_type	string	Yes	text, textarea, richtext, number, url, image, date, boolean, select, multiselect, tags, color, json
description	string	No	Help text
required	boolean	No	Default: false
options	object	No	{ "choices": ["a", "b"] } for select/multiselect
position	number	No	Display order (0-based)

cURLbash

curl -X POST multi-site-manager.vercel.app/api/sites/SITE_ID/content-types/TYPE_ID/fields \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Rating",
    "slug": "rating",
    "field_type": "number",
    "required": true
  }'

Content API

Content items have three fixed fields: title, body, and status. All other fields are stored in metadata(JSON), shaped by the content type's custom fields.

GET/api/content?site_id=SITE_IDInternal

List content items. Supports filtering, pagination, and dynamic metadata queries.

Query Parameters

Param	Type	Required	Description
site_id	string	Yes	The site UUID
content_type_id	string	No	Filter by content type
status	string	No	"published" or "draft"
limit	number	No	Max results (default 50, max 100)
offset	number	No	Skip N results (for pagination)
meta.*	string	No	Filter by any metadata field (see below)

Dynamic Metadata Filters

Use meta.FIELD_SLUG=value to filter by any custom field in metadata. Works for both array fields (tags, multiselect) and scalar fields (text, select).

Examplesbash

# Blog posts with tag "devlog"
curl "multi-site-manager.vercel.app/api/content?site_id=SITE_ID&meta.tags=devlog"

# Posts by a specific author
curl "multi-site-manager.vercel.app/api/content?site_id=SITE_ID&meta.author=JhonaMath"

# Easy recipes, published only, limit 5
curl "multi-site-manager.vercel.app/api/content?site_id=SITE_ID&meta.difficulty=easy&status=published&limit=5"

# Combine: blog posts with tag "gamejam" by "JhonaMath"
curl "multi-site-manager.vercel.app/api/content?site_id=SITE_ID&content_type_id=TYPE_ID&meta.tags=gamejam&meta.author=JhonaMath"

POST/api/contentInternal

Create a content item. Custom field values go in metadata.

Request Body

Param	Type	Required	Description
site_id	string	Yes	The site UUID
content_type_id	string	No	Content type UUID
title	string	Yes	Content title
slug	string	No	URL-friendly identifier
body	string	No	Content body (markdown)
metadata	object	No	Custom field values (e.g. { "tags": ["devlog"], "author": "JhonaMath" })
status	string	No	"draft" (default) or "published"

cURLbash

curl -X POST multi-site-manager.vercel.app/api/content \
  -H "Content-Type: application/json" \
  -d '{
    "site_id": "SITE_ID",
    "content_type_id": "BLOG_TYPE_ID",
    "title": "My First Post",
    "slug": "my-first-post",
    "body": "# Welcome\nThis is my first post.",
    "metadata": {
      "excerpt": "A short intro to my blog",
      "cover-image": "https://example.com/img.jpg",
      "author": "JhonaMath",
      "tags": ["devlog", "gamejam"],
      "read-time": "5 min"
    },
    "status": "published"
  }'

GET/api/content/:contentIdInternal

Get a single content item with its content type and metadata.

PATCH/api/content/:contentIdInternal

Update a content item. Only send fields you want to change.

Request Body

Param	Type	Required	Description
title	string	No	Updated title
slug	string	No	Updated slug
body	string	No	Updated body
metadata	object	No	Updated custom fields
status	string	No	"draft" or "published"
content_type_id	string	No	Change content type

DELETE/api/content/:contentIdInternal

Delete a content item.

Campaigns API

GET/api/campaigns?site_id=SITE_IDInternal

List all campaigns for a site.

POST/api/campaignsInternal

Create a new campaign draft.

Request Body

Param	Type	Required	Description
site_id	string	Yes	The site UUID
subject	string	Yes	Email subject line
content	string	No	Email body (markdown or text)

cURLbash

curl -X POST multi-site-manager.vercel.app/api/campaigns \
  -H "Content-Type: application/json" \
  -d '{
    "site_id": "SITE_ID",
    "subject": "Weekly Newsletter #1",
    "content": "Hello! Here is your weekly update..."
  }'

PATCH/api/campaigns/:campaignIdInternal

Edit a campaign's subject or content. Only draft campaigns can be edited. Sent campaigns return a 400 error.

POST/api/campaigns/:campaignId/sendInternal

Simulate sending a campaign. This creates campaign_recipients records for all subscribed contacts on the site and marks the campaign as sent.

Email sending is currently stubbed. No real emails are sent. Recipients are marked as "sent" immediately for simulation purposes.

Success Responsejson

{
  "message": "Campaign sent (simulated)",
  "recipients_count": 42
}

Error Handling

All errors return a JSON object with an error field.

Error formatjson

{ "error": "Description of what went wrong" }

HTTP Status Codes

Code	Meaning
200	Success
201	Created successfully
400	Bad request — missing or invalid fields
401	Unauthorized — invalid or missing API token
404	Resource not found
500	Server error

Integration Examples

HTML Form + JavaScript

Add a subscribe form to any website. The API call should go through your backend to keep the token secret.

Frontend (subscribe form)html

<form id="subscribe-form">
  <input type="email" name="email" placeholder="your@email.com" required />
  <input type="text" name="name" placeholder="Your name" />
  <button type="submit">Subscribe</button>
</form>

<script>
  document.getElementById('subscribe-form')
    .addEventListener('submit', async (e) => {
      e.preventDefault();
      const form = new FormData(e.target);

      // Call YOUR backend, not the API directly
      const res = await fetch('/api/subscribe', {
        method: 'POST',
        headers: { 'Content-Type': 'application/json' },
        body: JSON.stringify({
          email: form.get('email'),
          name: form.get('name'),
          tags: ['website'], // track source
        }),
      });

      if (res.ok) alert('Subscribed!');
    });
</script>

Your backend proxy (Node.js example)javascript

// server.js — keeps your API token secret
app.post('/api/subscribe', async (req, res) => {
  const response = await fetch(
    'multi-site-manager.vercel.app/api/public/subscribe',
    {
      method: 'POST',
      headers: {
        'Authorization': 'Bearer ' + process.env.SITE_API_TOKEN,
        'Content-Type': 'application/json',
      },
      body: JSON.stringify({
        email: req.body.email,
        name: req.body.name,
        tags: req.body.tags, // optional: pass tags from the client
      }),
    }
  );

  const data = await response.json();
  res.status(response.status).json(data);
});

React / Next.js Server Action

app/actions.tstypescript

'use server'

export async function subscribe(formData: FormData) {
  const res = await fetch(
    process.env.MULTI_SITE_URL + '/api/public/subscribe',
    {
      method: 'POST',
      headers: {
        'Authorization': 'Bearer ' + process.env.SITE_API_TOKEN,
        'Content-Type': 'application/json',
      },
      body: JSON.stringify({
        email: formData.get('email'),
        name: formData.get('name'),
      }),
    }
  );

  if (!res.ok) throw new Error('Subscription failed');
  return { success: true };
}

Python

subscribe.pypython

import requests

response = requests.post(
    "multi-site-manager.vercel.app/api/public/subscribe",
    headers={
        "Authorization": "Bearer YOUR_SITE_API_TOKEN",
        "Content-Type": "application/json",
    },
    json={
        "email": "user@example.com",
        "name": "John Doe",
    },
)

print(response.json())
# {'message': 'Subscribed successfully'}

REST API · v1

API Documentation

Everything you need to integrate Multi-Site with your websites, apps, and automations. Read content, manage subscribers, send campaigns — all via a simple REST API.

Quick subscribebash

curl -X POST multi-site-manager.vercel.app/api/public/subscribe \
  -H "Authorization: Bearer YOUR_SITE_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"email": "hello@example.com", "tags": ["website"]}'

Overview

The Multi-Site Manager API lets you manage sites, contacts, content, and campaigns programmatically. There are two types of endpoints:

Public API — Designed for external websites to subscribe users. Authenticated via site API tokens.
Internal API — Used by the dashboard. No auth required in local development.

Base URL: $multi-site-manager.vercel.app/api

All request and response bodies use JSON. Set Content-Type: application/json on all requests.

Authentication

The public subscribe endpoint requires a site API token passed as a Bearer token in the Authorization header.

Each site has a unique API token generated automatically when the site is created. You can find it in the site overview page of the dashboard.

Header format

Authorization: Bearer YOUR_SITE_API_TOKEN

Keep your API tokens secret. Do not expose them in client-side JavaScript. Use them only in server-side code or secure environments.

Subscribe Endpoint

POST/api/public/subscribePublic

Headers

Param	Type	Required	Description
Authorization	string	Yes	Bearer YOUR_SITE_API_TOKEN
Content-Type	string	Yes	application/json

Request Body

Param	Type	Required	Description
email	string	Yes	The contact's email address
name	string	No	The contact's display name
tags	string[]	No	Tag names to assign (created if they don't exist). Max 20 tags, 50 chars each

Example Request

cURLbash

curl -X POST multi-site-manager.vercel.app/api/public/subscribe \
  -H "Authorization: Bearer abc123def456..." \
  -H "Content-Type: application/json" \
  -d '{
    "email": "user@example.com",
    "name": "John Doe",
    "tags": ["website", "footer-form"]
  }'

Success Response

200 OKjson

{
  "message": "Subscribed successfully"
}

Error Responses

401 Unauthorizedjson

{ "error": "Invalid API token" }

400 Bad Requestjson

{ "error": "email is required" }

Sites API

GET/api/sitesInternal

Returns a list of all sites, ordered by most recent first.

Example Responsejson

[
  {
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "name": "Pokennection",
    "slug": "pokennection",
    "api_token": "abc123...",
    "created_at": "2026-04-08T12:00:00.000Z"
  }
]

POST/api/sitesInternal

Create a new site.

Request Body

Param	Type	Required	Description
name	string	Yes	Display name for the site
slug	string	Yes	URL-safe identifier (unique)

cURLbash

curl -X POST multi-site-manager.vercel.app/api/sites \
  -H "Content-Type: application/json" \
  -d '{ "name": "Stay Tiny", "slug": "stay-tiny" }'

201 Createdjson

{
  "id": "...",
  "name": "Stay Tiny",
  "slug": "stay-tiny",
  "api_token": "generated-token-here",
  "created_at": "2026-04-08T12:00:00.000Z"
}

GET/api/sites/:siteIdInternal

Get a single site by ID.

Contacts API

GET/api/sites/:siteId/contactsInternal

List all contacts linked to a site, with their subscription status. Returns joined data including the contact's email and name.

Example Responsejson

[
  {
    "id": "site-contact-uuid",
    "site_id": "...",
    "contact_id": "...",
    "status": "subscribed",
    "created_at": "2026-04-08T12:00:00.000Z",
    "contact": {
      "id": "...",
      "email": "user@example.com",
      "name": "John Doe"
    }
  }
]

POST/api/sites/:siteId/contactsInternal

Manually add a contact to a site. If the email already exists globally, the existing contact will be reused. If already linked to this site, no duplicate is created.

Request Body

Param	Type	Required	Description
email	string	Yes	Contact email
name	string	No	Contact name

cURLbash

curl -X POST multi-site-manager.vercel.app/api/sites/SITE_ID/contacts \
  -H "Content-Type: application/json" \
  -d '{ "email": "new@example.com", "name": "Jane" }'

PATCH/api/sites/:siteId/contacts/:siteContactIdInternal

Update a contact's name or subscription status for this site.

Request Body

Param	Type	Required	Description
name	string	No	Update the contact's name
status	string	No	"subscribed" or "unsubscribed"

cURLbash

curl -X PATCH multi-site-manager.vercel.app/api/sites/SITE_ID/contacts/SC_ID \
  -H "Content-Type: application/json" \
  -d '{ "status": "unsubscribed" }'

Content Types API

GET/api/content-type-templatesInternal

List available predefined templates (Blog Post, Devlog, Changelog, etc.).

GET/api/sites/:siteId/content-typesInternal

List all content types for a site, including their fields.

POST/api/sites/:siteId/content-typesInternal

Create a content type. Either from a template or from scratch.

From template

cURLbash

curl -X POST multi-site-manager.vercel.app/api/sites/SITE_ID/content-types \
  -H "Content-Type: application/json" \
  -d '{ "template": "blog-post" }'

Available templates: blog-post, devlog, changelog, page, newsletter, recipe, product-review.

Custom

cURLbash

curl -X POST multi-site-manager.vercel.app/api/sites/SITE_ID/content-types \
  -H "Content-Type: application/json" \
  -d '{ "name": "Game Review", "slug": "game-review", "description": "Reviews for games" }'

POST/api/sites/:siteId/content-types/:id/fieldsInternal

Add a field to a content type.

Request Body

Param	Type	Required	Description
name	string	Yes	Display name
slug	string	Yes	Identifier used in metadata
field_type	string	Yes	text, textarea, richtext, number, url, image, date, boolean, select, multiselect, tags, color, json
description	string	No	Help text
required	boolean	No	Default: false
options	object	No	{ "choices": ["a", "b"] } for select/multiselect
position	number	No	Display order (0-based)

cURLbash

curl -X POST multi-site-manager.vercel.app/api/sites/SITE_ID/content-types/TYPE_ID/fields \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Rating",
    "slug": "rating",
    "field_type": "number",
    "required": true
  }'

Content API

Content items have three fixed fields: title, body, and status. All other fields are stored in metadata(JSON), shaped by the content type's custom fields.

GET/api/content?site_id=SITE_IDInternal

List content items. Supports filtering, pagination, and dynamic metadata queries.

Query Parameters

Param	Type	Required	Description
site_id	string	Yes	The site UUID
content_type_id	string	No	Filter by content type
status	string	No	"published" or "draft"
limit	number	No	Max results (default 50, max 100)
offset	number	No	Skip N results (for pagination)
meta.*	string	No	Filter by any metadata field (see below)

Dynamic Metadata Filters

Use meta.FIELD_SLUG=value to filter by any custom field in metadata. Works for both array fields (tags, multiselect) and scalar fields (text, select).

Examplesbash

# Blog posts with tag "devlog"
curl "multi-site-manager.vercel.app/api/content?site_id=SITE_ID&meta.tags=devlog"

# Posts by a specific author
curl "multi-site-manager.vercel.app/api/content?site_id=SITE_ID&meta.author=JhonaMath"

# Easy recipes, published only, limit 5
curl "multi-site-manager.vercel.app/api/content?site_id=SITE_ID&meta.difficulty=easy&status=published&limit=5"

# Combine: blog posts with tag "gamejam" by "JhonaMath"
curl "multi-site-manager.vercel.app/api/content?site_id=SITE_ID&content_type_id=TYPE_ID&meta.tags=gamejam&meta.author=JhonaMath"

POST/api/contentInternal

Create a content item. Custom field values go in metadata.

Request Body

Param	Type	Required	Description
site_id	string	Yes	The site UUID
content_type_id	string	No	Content type UUID
title	string	Yes	Content title
slug	string	No	URL-friendly identifier
body	string	No	Content body (markdown)
metadata	object	No	Custom field values (e.g. { "tags": ["devlog"], "author": "JhonaMath" })
status	string	No	"draft" (default) or "published"

cURLbash

curl -X POST multi-site-manager.vercel.app/api/content \
  -H "Content-Type: application/json" \
  -d '{
    "site_id": "SITE_ID",
    "content_type_id": "BLOG_TYPE_ID",
    "title": "My First Post",
    "slug": "my-first-post",
    "body": "# Welcome\nThis is my first post.",
    "metadata": {
      "excerpt": "A short intro to my blog",
      "cover-image": "https://example.com/img.jpg",
      "author": "JhonaMath",
      "tags": ["devlog", "gamejam"],
      "read-time": "5 min"
    },
    "status": "published"
  }'

GET/api/content/:contentIdInternal

Get a single content item with its content type and metadata.

PATCH/api/content/:contentIdInternal

Update a content item. Only send fields you want to change.

Request Body

Param	Type	Required	Description
title	string	No	Updated title
slug	string	No	Updated slug
body	string	No	Updated body
metadata	object	No	Updated custom fields
status	string	No	"draft" or "published"
content_type_id	string	No	Change content type

DELETE/api/content/:contentIdInternal

Delete a content item.

Campaigns API

GET/api/campaigns?site_id=SITE_IDInternal

List all campaigns for a site.

POST/api/campaignsInternal

Create a new campaign draft.

Request Body

Param	Type	Required	Description
site_id	string	Yes	The site UUID
subject	string	Yes	Email subject line
content	string	No	Email body (markdown or text)

cURLbash

curl -X POST multi-site-manager.vercel.app/api/campaigns \
  -H "Content-Type: application/json" \
  -d '{
    "site_id": "SITE_ID",
    "subject": "Weekly Newsletter #1",
    "content": "Hello! Here is your weekly update..."
  }'

PATCH/api/campaigns/:campaignIdInternal

Edit a campaign's subject or content. Only draft campaigns can be edited. Sent campaigns return a 400 error.

POST/api/campaigns/:campaignId/sendInternal

Simulate sending a campaign. This creates campaign_recipients records for all subscribed contacts on the site and marks the campaign as sent.

Email sending is currently stubbed. No real emails are sent. Recipients are marked as "sent" immediately for simulation purposes.

Success Responsejson

{
  "message": "Campaign sent (simulated)",
  "recipients_count": 42
}

Error Handling

All errors return a JSON object with an error field.

Error formatjson

{ "error": "Description of what went wrong" }

HTTP Status Codes

Code	Meaning
200	Success
201	Created successfully
400	Bad request — missing or invalid fields
401	Unauthorized — invalid or missing API token
404	Resource not found
500	Server error

Integration Examples

HTML Form + JavaScript

Add a subscribe form to any website. The API call should go through your backend to keep the token secret.

Frontend (subscribe form)html

<form id="subscribe-form">
  <input type="email" name="email" placeholder="your@email.com" required />
  <input type="text" name="name" placeholder="Your name" />
  <button type="submit">Subscribe</button>
</form>

<script>
  document.getElementById('subscribe-form')
    .addEventListener('submit', async (e) => {
      e.preventDefault();
      const form = new FormData(e.target);

      // Call YOUR backend, not the API directly
      const res = await fetch('/api/subscribe', {
        method: 'POST',
        headers: { 'Content-Type': 'application/json' },
        body: JSON.stringify({
          email: form.get('email'),
          name: form.get('name'),
          tags: ['website'], // track source
        }),
      });

      if (res.ok) alert('Subscribed!');
    });
</script>

Your backend proxy (Node.js example)javascript

// server.js — keeps your API token secret
app.post('/api/subscribe', async (req, res) => {
  const response = await fetch(
    'multi-site-manager.vercel.app/api/public/subscribe',
    {
      method: 'POST',
      headers: {
        'Authorization': 'Bearer ' + process.env.SITE_API_TOKEN,
        'Content-Type': 'application/json',
      },
      body: JSON.stringify({
        email: req.body.email,
        name: req.body.name,
        tags: req.body.tags, // optional: pass tags from the client
      }),
    }
  );

  const data = await response.json();
  res.status(response.status).json(data);
});

React / Next.js Server Action

app/actions.tstypescript

'use server'

export async function subscribe(formData: FormData) {
  const res = await fetch(
    process.env.MULTI_SITE_URL + '/api/public/subscribe',
    {
      method: 'POST',
      headers: {
        'Authorization': 'Bearer ' + process.env.SITE_API_TOKEN,
        'Content-Type': 'application/json',
      },
      body: JSON.stringify({
        email: formData.get('email'),
        name: formData.get('name'),
      }),
    }
  );

  if (!res.ok) throw new Error('Subscription failed');
  return { success: true };
}

Python

subscribe.pypython

import requests

response = requests.post(
    "multi-site-manager.vercel.app/api/public/subscribe",
    headers={
        "Authorization": "Bearer YOUR_SITE_API_TOKEN",
        "Content-Type": "application/json",
    },
    json={
        "email": "user@example.com",
        "name": "John Doe",
    },
)

print(response.json())
# {'message': 'Subscribed successfully'}