{"id":29156,"date":"2022-05-19T15:48:14","date_gmt":"2022-05-19T13:48:14","guid":{"rendered":"https:\/\/pi3g.com\/?p=29156"},"modified":"2022-05-19T15:49:04","modified_gmt":"2022-05-19T13:49:04","slug":"mailerlite-api-error-code-422-for-subscribers-endpoint","status":"publish","type":"post","link":"https:\/\/pi3g.com\/de\/mailerlite-api-error-code-422-for-subscribers-endpoint\/","title":{"rendered":"mailerlite API-Fehlercode 422 f\u00fcr den Endpunkt subscribers"},"content":{"rendered":"\n

Today, I was implementing the interfacing between PiCockpit.com<\/a> and the Mailerlite API (which we use aus our newsletter software). <\/p>\n\n\n\n

https:\/\/api.mailerlite.com\/api\/v2\/subscribers<\/a><\/p>\n\n\n\n

I got the following error message:<\/p>\n\n\n\n

{\"error\":{\"code\":422,\"message\":\"Unprocessable entity\"}}<\/code><\/pre>\n\n\n\n
The POST request was returning 422 as status code. <\/p>\n\n\n\n
Unfortunately there is little documentation about that on Mailerlite. My implementation was correct (this is Crystal Lang by the way):<\/p>\n\n\n\n
\tget \"\/test\" do |env|\n\t  body = \"{\\\"email\\\": \\\"support@example.com\\\"}\"\n\t  puts body\n      response = HTTP::Client.post(\"https:\/\/api.mailerlite.com\/api\/v2\/subscribers\", \n      \t\theaders: HTTP::Headers{\n      \t\t\t\"X-MailerLite-ApiKey\" => \"MAILERLITE_APIKEY\",\n      \t\t\t\"Content-Type\": \"application\/json\"\n      \t\t\t}, \n      \t\tbody: body)\n  \t  if response.status_code != 201 \n  \t  \tputs \"newsletter_subscription :: error code #{response.status_code}\"\n  \t  \tputs response.body\n  \t  else\n  \t  \tputs \"newsletter_subscription :: OK\"\n  \t  \tputs response.body\n  \t  end\n\tend\n<\/code><\/pre>\n\n\n\n
where MAILERLITE_APIKEY is the API key which you create in the backend:<\/p>\n\n\n\n
https:\/\/dashboard.mailerlite.com\/integrations\/api<\/a><\/p>\n\n\n\n
(Click on “Generate new token”, it is displayed only once to you).<\/p>\n\n\n\n
How to fix 422 when calling the subscribers endpoint of the Mailerlite API<\/h2>\n\n\n\n
The mailerlite support gave me the solution: <\/p>\n\n\n\n
certain email addresses are rejected – e.g. email addresses which are support@<domain>. This is due to the bounce rate being higher on them.<\/p>\n\n\n\n
How does a successful response look like?<\/h2>\n\n\n\n
With a different e-mail address, the response looks like this:<\/p>\n\n\n\n
{“id”:2348923942342834,”name”:””,”email”:”differentuser@example.com”,”sent”:0,”opened”:0,”opened_rate”:0,”clicked”:0,”clicked_rate”:0,”type”:”unconfirmed”,”country_id”:””,”signup_ip”:null,”signup_timestamp”:null,”confirmation_ip”:null,”confirmation_timestamp”:null,”fields”:[{“key”:”last_name”,”value”:””,”type”:”TEXT”},{“key”:”company”,”value”:””,”type”:”TEXT”},{“key”:”country”,”value”:””,”type”:”TEXT”},{“key”:”city”,”value”:””,”type”:”TEXT”},{“key”:”phone”,”value”:””,”type”:”TEXT”},{“key”:”state”,”value”:””,”type”:”TEXT”},{“key”:”z_i_p”,”value”:””,”type”:”TEXT”}],”date_subscribe”:”2022-05-19 12:09:24″,”date_unsubscribe”:null,”date_created”:”2022-05-19 12:09:24″,”date_updated”:”2022-05-19 12:09:24″}<\/p>\n\n\n\n
The response code is 201<\/strong>, “created”.<\/p>\n\n\n\n
Hire us<\/h2>\n\n\n\n
If you need support for your backend or frontend development, you can hire us. Get in touch for more information<\/a>.<\/p>\n\n\n\n
 <\/p>\n","protected":false},"excerpt":{"rendered":"
Heute habe ich die Schnittstelle zwischen PiCockpit.com und der Mailerlite API (die wir f\u00fcr unsere Newsletter-Software verwenden) implementiert. https:\/\/api.mailerlite.com\/api\/v2\/subscribers Ich bekam folgende Fehlermeldung: Die POST-Anfrage gab 422 als Statuscode zur\u00fcck. Leider gibt es nur wenig Dokumentation zu diesem Thema bei Mailerlite. Meine Implementierung war korrekt (dies ist \u00fcbrigens Crystal Lang):...<\/p>","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","_links_to":"","_links_to_target":""},"categories":[416],"tags":[],"class_list":["post-29156","post","type-post","status-publish","format-standard","hentry","category-crystal-language"],"_links":{"self":[{"href":"https:\/\/pi3g.com\/de\/wp-json\/wp\/v2\/posts\/29156","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pi3g.com\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pi3g.com\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pi3g.com\/de\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/pi3g.com\/de\/wp-json\/wp\/v2\/comments?post=29156"}],"version-history":[{"count":2,"href":"https:\/\/pi3g.com\/de\/wp-json\/wp\/v2\/posts\/29156\/revisions"}],"predecessor-version":[{"id":29158,"href":"https:\/\/pi3g.com\/de\/wp-json\/wp\/v2\/posts\/29156\/revisions\/29158"}],"wp:attachment":[{"href":"https:\/\/pi3g.com\/de\/wp-json\/wp\/v2\/media?parent=29156"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pi3g.com\/de\/wp-json\/wp\/v2\/categories?post=29156"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pi3g.com\/de\/wp-json\/wp\/v2\/tags?post=29156"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}