In this page you’ll find a guide through our API Version 2 by use cases. We try to answer the most common questions on how to integrate external systems with the Newsletter plugin using our REST API 2. The REST API 1 are still active and supported but they’re less complete and flexible, so we suggest to migrate as soon as you have the opportunity to review your integration.
You can look at the full API reference documentation to get every detail.
Most API calls need an authentication key to be invoked.
For this task, you should use the subscribers
endpoint with the POST
method. It accepts a JSON object in the request body containing the subscriber data (the email address is the only required field). You can even set privare lists and private profile fields.
This method requires an authentication key to be called and must never be used from a public client but only for server-to-server data exchange.
This method does only simple data cleanup and usually ends with an error only if the email address is not valid. No spam check is made since it is assumed the data provider by your other system is already correct.
This endpoint returns an error if the subscriber is already present without changing it. So you can use it only to add new subscribers.
Read more at the official sales page…
2.3.2
27/06/2023
2.3.2
27/06/2023
In this page you’ll find a guide through our API Version 2 by use cases. We try to answer the most common questions on how to integrate external systems with the Newsletter plugin using our REST API 2. The REST API 1 are still active and supported but they’re less complete and flexible, so we suggest to migrate as soon as you have the opportunity to review your integration.
You can look at the full API reference documentation to get every detail.
Most API calls need an authentication key to be invoked.
For this task, you should use the subscribers
endpoint with the POST
method. It accepts a JSON object in the request body containing the subscriber data (the email address is the only required field). You can even set privare lists and private profile fields.
This method requires an authentication key to be called and must never be used from a public client but only for server-to-server data exchange.
This method does only simple data cleanup and usually ends with an error only if the email address is not valid. No spam check is made since it is assumed the data provider by your other system is already correct.
This endpoint returns an error if the subscriber is already present without changing it. So you can use it only to add new subscribers.
Read more at the official sales page…