Picture of Teenvio
Teenvio
29 Jun 2022
Reading: 3'
After several months of work, we are pleased to announce an update of our REST API to the new version V3 , with several changes and improvements. If you are currently working on sending emails with teenvio REST API technology, you will surely be interested in this article to improve your email marketing campaigns.
We have published new methods, including the launch of “full request” emails, which are very useful for low-volume transactional sending, and additional methods for managing creatives or newsletters.
Improved response standardization, returning more consistent HTTP 200, 400, 403, 404, and 500 statuses.
Requests in JSON format are allowed in addition to the classic form/data or x-www-form-urlencode.
The new v3 version is compatible with v2 requests and during 2022/2023 it would not be necessary to modify the integrations except to take advantage of the improvements in the error codes.
What has been improved in the REST API for email marketing?
OK responses do not change and continue to return HTTP 200 codes.
KO responses instead of returning HTTP 200 codes will compliance directors email lists now return codes: 400, 403, 404, 405 or 500 in most cases and depending on the nature of the error.
Credentials cannot be sent with GET parameters.
To improve security, requests will always be HTTPS.
Responses in XML or JSON depending on the Accept header.
Requests in form/data, x-www-form-urlencode or raw JSON depending on the Content-Type header.
Until when will I be able to use v2.9 and what should I do?
The previous version v2.9 of the REST API for email marketing will only be available until the end of 2023, so it is advisable to change the REST requests to the new URL as soon as possible.
In most cases only changing the URL will be required.
by
Just in case you were handling erroneous responses, you should check that your integration is now able to read HTTP status codes other than 200 to read any error messages.
If you have any questions, you can always contact our technical support department where we have developers who can review the code of your integration.
Are other APIs affected?
The POST API continues to work, but it is recommended to migrate to the REST API given its multiple advantages.
The SMTP API remains unchanged, only the security requirements are updated:
Encryption is required: You can use SMTP encryption on port 46500 or clear connection on port 2500 or 58700 but using STARTLS to start encryption.
Encryption must be TLSv1.2 or higher, excluding any other older versions.
Attempting to launch the AUTH LOGIN authentication command without prior encryption will return an error.
