Systeme.io API and MCP server

• POST

  list_transactions

  Sales from the Transactions page, with customer, offer, amount and transaction type.

  read

  Lists transactions with the same filters as the Transactions page: customer email, offer, transaction type, date range, customer country and customer type (company or individual). Results are newest first. Pass next_cursor back as cursor for the next page.

  POST /api/v1/systeme-io/list_transactions

  Input

  Input: list_transactions

  Parameter	Type	Description
  customer_email	string	Only this customer.
  offer	string	Only sales of this offer (name or ID).
  type	string	Transaction type, as in the Transactions filter.
  from	date	Start of the date range.
  to	date	End of the date range.
  customer_country	string	Two-letter country code.
  customer_type	enum	company or individual.
  limit	integer	1 to 100. Default: 50.
  cursor	string	Next page cursor from the previous call.

  Example response

  {
    "transactions": [
      {
        "transaction_id": "tr_20931",
        "customer_email": "hans@example.com",
        "offer": "Starter course",
        "amount": 97,
        "currency": "EUR",
        "type": "sale",
        "customer_country": "DE",
        "customer_type": "individual",
        "occurred_at": "2026-10-08T09:12:00Z"
      },
      {
        "transaction_id": "tr_20944",
        "customer_email": "office@example.de",
        "offer": "Pro membership",
        "amount": 49,
        "currency": "EUR",
        "type": "sale",
        "customer_country": "DE",
        "customer_type": "company",
        "occurred_at": "2026-10-09T15:40:00Z"
      }
    ],
    "next_cursor": null
  }

• POST

  get_transaction

  One sale with customer, offer, amount, payment processor charge ID and refund status.

  read

  Returns one transaction as listed on the Transactions page, with the payment processor charge ID and whether it was refunded. Use it before refund_transaction to check the amount and the customer.

  POST /api/v1/systeme-io/get_transaction

  Input

  Input: get_transaction

  Parameter	Type	Description
  transaction_id required	string	Transaction ID from list_transactions.

  Example response

  {
    "transaction_id": "tr_20931",
    "customer_email": "hans@example.com",
    "offer": "Starter course",
    "amount": 97,
    "currency": "EUR",
    "type": "sale",
    "processor_charge_id": "ch_3Q9xExample",
    "refunded": false,
    "occurred_at": "2026-10-08T09:12:00Z"
  }

• POST

  export_transactions

  Starts a CSV export of transactions; Systeme.io emails the download link to your account address.

  read

  Starts the same CSV export as the Transactions page, for transactions in an optional date range. Systeme.io emails the download link to the address of your account, so the call returns only a confirmation. The export reaches only you.

  POST /api/v1/systeme-io/export_transactions

  Input

  Input: export_transactions

  Parameter	Type	Description
  from	date	Start of the date range.
  to	date	End of the date range.
  delimiter	string	Column separator for the CSV file, as offered in the export popup.

  Example response

  {
    "status": "started",
    "delivery": "email to your account address"
  }

• POST

  list_funnel_steps

  Your sales funnels with their steps: name, type, URL path and page ID.

  read

  Lists funnels with their steps in funnel order. Each step has the ID that the page tools take as step_id. Leave funnel_id out to list every funnel.

  POST /api/v1/systeme-io/list_funnel_steps

  Input

  Input: list_funnel_steps

  Parameter	Type	Description
  funnel_id	string	Only this funnel. Default: all funnels.

  Example response

  {
    "funnels": [
      {
        "funnel_id": "f_1204",
        "name": "Webinar funnel",
        "steps": [
          {
            "step_id": "8841207",
            "name": "Webinar sales page",
            "type": "sales page",
            "path": "webinar"
          },
          {
            "step_id": "8841219",
            "name": "Thank you",
            "type": "thank you page",
            "path": "webinar-thanks"
          }
        ]
      }
    ]
  }

• POST

  get_page_content

  Text elements of a funnel page (headlines, paragraphs, buttons) with an ID per element.

  read

  Returns the text elements of one funnel page in page order, each with an element ID. Pass those IDs to update_page_text. Images and layout settings are not included.

  POST /api/v1/systeme-io/get_page_content

  Input

  Input: get_page_content

  Parameter	Type	Description
  step_id required	string	Funnel step ID from list_funnel_steps.

  Example response

  {
    "step_id": "8841207",
    "elements": [
      {
        "element_id": "headline-1a2b",
        "kind": "headline",
        "text": "Free webinar: launch your first course"
      },
      {
        "element_id": "button-9f3c",
        "kind": "button",
        "text": "Register now"
      }
    ]
  }

• POST

  list_blog_posts

  Posts of a blog with title, URL path, categories and whether each is active.

  read

  Lists the posts of one blog, with the ID that activate_blog_post takes as post_id. The blog_id of your blog is also returned, for create_blog_post. Active posts are visible on the blog; inactive ones are not.

  POST /api/v1/systeme-io/list_blog_posts

  Input

  Input: list_blog_posts

  Parameter	Type	Description
  blog_id	string	Blog to read. Default: your first blog.
  limit	integer	1 to 100. Default: 50.

  Example response

  {
    "blog_id": "blog_3302",
    "posts": [
      {
        "post_id": "bp_5498",
        "title": "Five launch mistakes",
        "path": "five-launch-mistakes",
        "categories": [
          "Marketing"
        ],
        "active": true
      }
    ],
    "next_cursor": null
  }

• POST

  update_page_text

  Change the text of chosen elements on a funnel page and save it; the rest of the page stays as it is.

  asks first write

  Changes the text of the elements you name and saves the page. Other elements, images and settings are not touched. On a live funnel visitors see the change at once. By default you confirm each call; you can switch that off for this tool.

  POST /api/v1/systeme-io/update_page_text

  Input

  Input: update_page_text

  Parameter	Type	Description
  step_id required	string	Funnel step ID from list_funnel_steps.
  changes required	object	Map of element_id from get_page_content to new text.

  Example response

  {
    "step_id": "8841207",
    "updated_elements": 2,
    "saved_at": "2026-10-11T14:05:12+02:00"
  }

• POST

  duplicate_funnel_step

  Copy a step below the original, with "(copy)" in its name; set a new URL path for the copy.

  write

  Duplicates a funnel page and places the copy below the original, named with "(copy)". Pass path to give the copy its own URL. The copy reaches no one until you link to it, and remove_funnel_step undoes it, so this call runs without asking.

  POST /api/v1/systeme-io/duplicate_funnel_step

  Input

  Input: duplicate_funnel_step

  Parameter	Type	Description
  step_id required	string	Funnel step ID from list_funnel_steps.
  path	string	URL path for the copy.

  Example response

  {
    "step_id": "8841260",
    "name": "Webinar sales page (copy)",
    "path": "webinar-b",
    "copied_from": "8841207"
  }

• POST

  remove_funnel_step

  Permanently delete a step and its page from a funnel.

  asks first write

  Deletes one step and its page from a funnel. This cannot be undone, and visitors lose the page. By default you confirm each call; you can switch that off for this tool.

  POST /api/v1/systeme-io/remove_funnel_step

  Input

  Input: remove_funnel_step

  Parameter	Type	Description
  step_id required	string	Funnel step ID from list_funnel_steps.

  Example response

  {
    "step_id": "8841219",
    "status": "removed"
  }

• POST

  refund_transaction

  Refund a sale in full through its payment gateway; an invoice with a negative amount is created.

  asks first write

  Refunds the whole sale; Systeme.io does not support partial refunds. It depends on your payment gateway: the balance must cover the refund. Afterwards the transaction shows an invoice with a negative amount, which send_invoice can email to the customer. By default you confirm each call; you can switch that off for this tool.

  POST /api/v1/systeme-io/refund_transaction

  Input

  Input: refund_transaction

  Parameter	Type	Description
  transaction_id required	string	Transaction ID from list_transactions.

  Example response

  {
    "transaction_id": "tr_20931",
    "status": "refunded",
    "refunded_amount": 97,
    "currency": "EUR"
  }

• POST

  send_invoice

  Email the invoice of a transaction to its customer.

  asks first write

  Sends the invoice of one transaction to the customer, as the Send invoice to customer action does. After a refund it sends the invoice with the negative amount. Invoices go out one at a time. By default you confirm each call; you can switch that off for this tool.

  POST /api/v1/systeme-io/send_invoice

  Input

  Input: send_invoice

  Parameter	Type	Description
  transaction_id required	string	Transaction ID from list_transactions.

  Example response

  {
    "transaction_id": "tr_20931",
    "status": "sent",
    "sent_to": "hans@example.com"
  }

• POST

  create_blog_post

  New blog post from Markdown, saved inactive so nobody sees it until you activate it.

  write

  Creates a post with a title, short description, URL path, main image and categories, and fills it with your Markdown. Categories must already exist in the blog. The post is saved inactive, so it reaches no one until activate_blog_post runs; this call runs without asking.

  POST /api/v1/systeme-io/create_blog_post

  Input

  Input: create_blog_post

  Parameter	Type	Description
  blog_id required	string	Blog ID from list_blog_posts.
  title required	string	Post title.
  body_markdown required	string	Post content. Images by URL.
  description	string	Short description shown on listing pages.
  path	string	URL path. Default: made from the title.
  categories	string[]	Names of categories that already exist in the blog.
  image_url	string	Main image.

  Example response

  {
    "post_id": "bp_5521",
    "blog_id": "blog_3302",
    "title": "How we cut onboarding time in half",
    "categories": [
      "Marketing"
    ],
    "active": false
  }

• POST

  activate_blog_post

  Show a post on your blog.

  asks first write

  Activates one post so visitors can read it on your blog. By default you confirm each call; you can switch that off for this tool.

  POST /api/v1/systeme-io/activate_blog_post

  Input

  Input: activate_blog_post

  Parameter	Type	Description
  post_id required	string	Blog post ID from list_blog_posts.

  Example response

  {
    "post_id": "bp_5521",
    "active": true
  }

Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the Authorization: Bearer header.