bark: clarify mandrill vs mailchimp api key

Sending on-demand emails requires a Mandrill API key, not a Mailchimp
one. (They're part of the same company/suite now, but still use
different keys and endpoints. Mandrill and Mailchimp keys are also
called "mailchimp" and "marketing" keys respectively. Yes, in that
order.)
This commit is contained in:
fang 2023-07-18 23:33:15 +02:00
parent 3945cc1f5f
commit 102c439b75
No known key found for this signature in database
GPG Key ID: EB035760C1BBA972
2 changed files with 3 additions and 3 deletions

View File

@ -17,7 +17,7 @@
^- form:m
=/ arg-mold
$: tlon-api-key=tape
mailchimp-api-key=tape
mandrill-api-key=tape
=ship
=carpet:hark
==
@ -44,7 +44,7 @@
:* %pass /send-mailchimp-email/(scot %p ship.u.args)
%arvo %k %fard
%bark %mailchimp-send-template %noun
!>(`[mailchimp-api-key.u.args (trip email) "landscape-weekly-digest" (template-vars ship.u.args carpet.u.args)])
!>(`[mandrill-api-key.u.args (trip email) "landscape-weekly-digest" (template-vars ship.u.args carpet.u.args)])
==
;< [wimp=wire simp=sign-arvo] bind:m take-sign-arvo
?> ?=([%send-mailchimp-email @ *] wimp)

View File

@ -1,7 +1,7 @@
:: Mailchimp/Send Template
:: send an email template via the Mailchimp Transactional API
::
:: > -bark!mailchimp-send-template "[API_KEY]" "someone@example.com" "template-name" vars :: vars is a (map cord cord)
:: > -bark!mailchimp-send-template "[MANDRILL_API_KEY]" "someone@example.com" "template-name" vars :: vars is a (map cord cord)
::
/- spider
/+ *strandio