Skip to main content
The newsletter/ endpoint provides an interface for managing newsletter subscribers and newsletter target groups. You can create, update and delete target groups. You can also retrieve a list of all newsletter subscribers and create new subscribers.

Supported methods

List of all supported methods.

Data fields for target groups and subscribers

Newsletter management distinguishes two central entities: target groups and subscribers. Target groups are used for thematic or organizational classification of subscribers, for example for targeted campaigns or regional segments. Subscribers are individual users who have registered for a newsletter and optionally can be listed in several target groups at the same time. The following tables describe the respective data fields:

Data fields of a target group

Example

Data fields of a subscriber

Example

Methods for target groups

The following methods let you manage newsletter target groups. Target groups are used to segment subscribers within the shop system. Via the API you can retrieve, edit, create or deactivate existing target groups. New subscribers can only be assigned to active target groups. Deactivation means that no new entries can be added.

GET newsletter/group

This method returns a list of all target groups existing in the system. Optionally, the result list can be limited by filters on the deactivated status or the creation date. Sorting by these fields is also possible. Permissions to read newsletter data are required.

Example

Response

Filter fields

deactivated, createdAt

Sort fields

createdAt, updatedAt, name, id, deactivated

Error codes

GET newsletter/group/{id}

This method loads the details of a specific target group by its ID. Information such as name, status, time of creation and time of update is returned. Permissions to read newsletter data are required.

Example

Response

Error codes

POST newsletter/group

Creates a new newsletter target group. A name must be provided; unknown parameters lead to an error. After successful creation, the full entry with timestamps and ID is returned. Create permissions for newsletter data are required.

Example

Request body

Response

Error codes

PUT newsletter/group/{id}

This method updates the name of an existing target group by its ID. Unknown parameters in the request body lead to an error. Write permissions for newsletter data are required.

Example

Request body

Response

Error codes

DELETE newsletter/group/{id}

A target group is deactivated. From the time of deactivation, no new subscribers can join this group. Already assigned subscribers remain. Delete permissions for newsletter data are required.

Example

Response

The target group is deactivated successfully.

Error codes

Methods for subscribers

GET newsletter/subscriber

This method returns a paginated list of all newsletter subscribers in the system. The subscriber data includes, among other things, the encrypted email address, the registration date and personal information in the fields field. The results can be specifically limited via filter and sort parameters. For access, the corresponding read permissions for newsletter data are required.

Example

Response

Filter fields

targetGroupIds, createdAt

Sort fields

id, createdAt

Error codes

GET newsletter/subscriber/{id}

This method loads the full data of a single newsletter subscriber by their ID. The response additionally contains a history of all changes to the record in the changes section, if any are available. To use this method, the corresponding read permissions for newsletter data are required.

Example

Response

Error codes

POST newsletter/subscriber/

A new newsletter subscriber is created. By default, the subscriber must confirm the registration (double opt-in). Since a confirmation is required, the subscriber only appears in the subscriber list after the opt-in has been completed. To use this method, the corresponding create permissions for newsletter data are required.

Example

Request body

Response

Error codes

PUT newsletter/subscriber/{id}

This method updates the data of an existing newsletter subscriber by their ID. Only the fields email, fields (for example first name, last name) and targetGroupIds (target group membership) may be changed. Unknown parameters in the request body lead to an error.

Changing the email address

The email address is unique in the shop. If the new address already belongs to another subscriber, the request is rejected with 409 Conflict and the type "emailAlreadyExists". A change that only affects upper and lower case does not count as a change of the email address. If the email address is changed, the owner of the new address must confirm the change via double opt-in. To do this, the shop sends the double opt-in email from newsletter.newsletter → doubleOptInEmailSubscribe to the new address. The token contains the ID of the subscriber. After confirmation with NewsletterSubscribeConfirm, the new address is transferred to this subscriber. No additional subscriber is created and no welcome email is sent. Until confirmation, the following applies:
  • The stored email address remains unchanged.
  • All other changes from the request body, i.e. fields and targetGroupIds, are saved immediately and appear in changes.
  • The response additionally contains the field pendingEmail with the new, not yet confirmed address.
If the double opt-in email cannot be sent, the interface responds with 503 Service Unavailable. In this case, nothing is saved. To use this method, the corresponding write permissions for newsletter data are required.

Example

Request body

If email is also passed with a new address, the response still contains the previous address in email and the new address in pendingEmail:

Response

Error codes

Support

Bei technischen Fragen und Hilfestellungen ist unser Support-Team für Sie erreichbar: Zum Kundenportal Bitte senden Sie uns eine möglichst detaillierte Beschreibung sowie Screenshots, Requests/Antworten, damit wir Ihre Anfrage zeitnah und zielführend beantworten können.