Bulk subscriber operations added to the REST API
This end point provides the same functionality as bulk move, copy, delete and tag functions in the app’s UI.
Author Archives: Phil Hollows
API Q1 2022 Update
There have been no material changes to the FeedBlitz APIs this quarter.
Triggers API – New Events Added
Paralleling the changes in the FeedBlitz UI, the triggers REST API has been updated to include two new event types: Open and Click. These events trigger actions when an open is recorded, or any tracked link clicked. A great use of these events is to add subscribers who engage to a group, which you can
New Ad Insertion Shortcodes
Four new mailing shortcode tags are now available to control ads in your mailings, if you want to earn income passively from your mailstream and still maintain per-list or per-mailing control. Ad insertion tags are: <$BlogItemMarqueeAd$> <$BlogItemBannerAd$> <$BlogItemRectangleAd$> Specify these in a mailing to insert the relevant ad type. These work even when you have
New Capabilities for the /feed resource in the REST API
The /feeds API resource has been a long-standing part of the FeedBlitz REST API, but it was a tad limited. It only supported the GET method and was pretty limited in what it told you about the feed itself. So I’m excited to announce the following changes to the RSS feed API: It tells you
FrankenFunnels! Adding “keepalive” to make funnels behave like lists
The REST API has been updated to include the new “keepalive” parameter for an autoresponder (funnel). By default it’s off – a funnel is a funnel is a funnel, and once the subscriber finishes it, they’re done. But once you set keepalive to be on, things change. Instead, when the sequence completes, the subscriber stays
Overriding the sender information in funnel entries
The REST API now allows you to override the default funnel campaign’s sender information (the from name, address and reply-to values) for individual entries. The details are in the “Mail Action” section of the funnel sequence management API. An example use case is a new customer onboarding sequence. You might have the default sender be
Resending and Receipts
The FeedBlitz transactional email API has been extended to enable an email to be resent. In addition, the core call to send an email has been extended to allow you to request delivery and / or read receipts (although you might not get them; sending these notifications is optional).
Attachments!
FeedBlitz now supports attachments in single mailings for the /sendmail and /newsflash resources.
Welcome to the FeedBlitz API web site!
We’re excited to have brought our API documentation online for the first time. Watch this space for change / release notes.