Mailpoet

1{
2  "schemaVersion": 1,
3  "plugin": "mailpoet",
4  "displayName": "MailPoet",
5  "profileVersion": "2026-08",
6  "sourceOfTruth": "https://kb.mailpoet.com/",
7  "distribution": "wordpress-org",
8  "capabilities": [
9    "crm.email-subscription"
10  ],
11  "detect": {
12    "pluginFileIds": [
13      "mailpoet/mailpoet.php"
14    ],
15    "routes": [
16      "/mailpoet/v1/subscribers"
17    ],
18    "restNamespaces": [
19      "mailpoet/v1"
20    ],
21    "assetPathSlugs": [
22      "mailpoet"
23    ]
24  },
25  "entities": [
26    {
27      "entity": "subscriber",
28      "channel": "plugin-rest",
29      "route": "/mailpoet/v1/subscribers",
30      "recordKeyField": "id",
31      "responseEnvelope": {
32        "itemsPath": "data.items",
33        "countPath": "data.meta.count"
34      },
35      "candidateTargetRefs": [
36        "crm/email-subscription"
37      ],
38      "pitfalls": [
39        {
40          "code": "consent-status-per-record",
41          "severity": "blocker",
42          "summary": "VERIFIED LIVE against the reference store 2026-08-11: each subscriber carries status (subscribed / unconfirmed / unsubscribed — MailPoet's double opt-in flow) both at the top level and per entry in subscriptions[] (one per list/segment). Only a status of 'subscribed' is consent evidence; writing an unconfirmed or unsubscribed record as a Wix subscribed contact is a consent violation, not a data-quality nuance — see crm/email-subscription's own consent-proof-required pitfall. On this run, the first 2 of 3 inspected subscribers were 'unconfirmed'."
43        }
44      ]
45    }
46  ],
47  "quirks": [
48    "finding #28: the REST route wraps its records as { data: { items: [...], meta: { count, pages } } } instead of a flat array, and advertises no X-WP-Total/X-WP-TotalPages headers — responseEnvelope (itemsPath/countPath) is what makes this readable at all; without it the whole envelope would sample as a single opaque record with recordCount 1.",
49    "VERIFIED LIVE 2026-08-11: 306 real subscribers on the reference store, genuinely paginated (page/per_page args; 16 pages at 20/page at the default per_page).",
50    "MailPoet exposes /segments, /tags, /newsletters, /forms, /automations, /dynamic-segments, and /custom-fields under the same namespace and the same responseEnvelope shape (all VERIFIED LIVE 2026-08-11) — not profiled here. Each subscriber record already embeds its own segment_id/status pairs (subscriptions[]) and tags[], so a segment/tag NAME lookup is only needed if a migration wants human-readable list/tag names rather than ids; add /segments and /tags as additional entities if that lookup becomes necessary."
51  ]
52}