Add Changelog subscribers
Adds email addresses as Changelog subscribers in bulk.
Subscribers receive email notifications when new Changelogs are published (if email notifications are enabled during publishing).
Request Body
emails- Array of email addresses to add (required, 1-1000 emails)locale- Locale for the subscribers (optional, defaults to the organization default)
Email Validation
- Every entry must be a valid email address. Otherwise nothing is added, and
detailslists the invalid entries - Emails are lowercased and duplicates are removed
Rate Limiting
This endpoint is rate limited to prevent abuse. If you need to import more subscribers, please contact support.
Response
Returns a confirmation with the count of processed emails:
{
"object": "changelog_subscribers_import",
"count": 150
}Errors
400- Invalid request (empty emails array, too many emails)403- Monthly import limit reached
Compatibility
Changelogs appear as Updates in the dashboard. Keep using /v2/outbound/changelogs, client.outbound.changelogs, and the changelog.published webhook. This reference describes Pulsar. The original /v2/changelogs routes still work; their behavior follows the selected API version. The Outbound paths require Pulsar or later. In Pulsar, the API key owner needs a full seat and the manage_changelogs permission.
Body
Email addresses to add as changelog subscribers
1 - 1000Subscriber locale. Defaults to the organization default locale.
ar, am, fa, ht, lo, my, pa, ps, so, tl, ur, he, ta, te, mr, gu, kn, ml, ha, jv, yo, ig, uz, ne, sd, az, si, km, kk, bn, bs, pt-BR, bg, ca, hr, cs, da, nl, en, et, fi, fr, de, el, hi, hu, id, it, ja, ko, lv, lt, ms, mn, nb, pl, pt, ro, ru, sr, zh-CN, sk, sl, es, sw, sv, th, zh-TW, tr, uk, vienResponse
Success