Call SparkPost API directly (drop unmaintained library) #203
Labels
Comments
medmunds
added a commit
that referenced
this issue
Sep 11, 2020
Switch from the (now unmaintained) python-sparkpost client library to a requests-based backend that calls SparkPost's Transmissions API directly. Also adds support for text/x-amp-html alternative parts (which are supported by the SparkPost API, but weren't by the client library). Closes #203
medmunds
added a commit
that referenced
this issue
Sep 11, 2020
Switch from the (now unmaintained) python-sparkpost client library to a requests-based backend that calls SparkPost's Transmissions API directly. Also adds support for text/x-amp-html alternative parts (which are supported by the SparkPost API, but weren't by the client library). Closes #203
|
Released in Anymail 8.0 |
medmunds
added a commit
that referenced
this issue
Nov 27, 2020
Switch from the (now unmaintained) python-sparkpost client library to a requests-based backend that calls SparkPost's Transmissions API directly. Also adds support for text/x-amp-html alternative parts (which are supported by the SparkPost API, but weren't by the client library). Closes #203
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Up to v7.x, Anymail has integrated with SparkPost through their "super-mega-official" sparkpost Python package.
Although it still seems to be working for Anymail, that package hasn't been updated in over 2.5 years, has accumulated a number of bugs and merged-but-unreleased PRs, and is apparently "no longer supported" by the company.
SparkPost has a straightforward, JSON based sending API. It would be simple to call it directly (through requests) like Anymail does with nearly every other ESP. Going through the official Python library doesn't really add any value, and actually complicates ongoing maintenance. (Anymail contains its own workarounds for some of the library issues.)
An added benefit of calling the API directly is that newer SparkPost features (e.g., subaccounts, A/B testing) would become immediately available through Anymail's
esp_extra, without having to wait for a library update (that may never be coming).This would be a breaking change, as anyone using
esp_extrawith SparkPost would need to update it to the new format. (I'm not sure how common that is with SparkPost.)The text was updated successfully, but these errors were encountered: