Versions Compared

Old Version 8

changes.mady.by.user MailUp Dev Team

Saved on

compared with

New Version 9

changes.mady.by.user MailUp Dev Team

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The personalization engine allows to provide newsletters contents using Liquid template. If you can provide recipient-related JSON information data via a web service, you could use this feature to personalize your newsletter. When MailUp will send your newsletter, it will call your web service and retrieve the personalized information per recipient. To reach a specified recipient the personalization engine will create an url that contains recipent-related data that you'll define creating a personalization endpoint configuration. So, let's create your first personalization endpoint!

...

DescriptionRetrieve the list of personalization endpoints configurations

HTTP Method

GET
URL
Code Block
languagexml
https://services.mailup.com/API/v1.1/Rest/ConsoleService.svc/Console/Personalization/Endpoints
JSON request (example)none
JSON response (example)
Expand
Code Block
{
    "IsPaginated": true,
    "Items": [
        {
            "CreationDate": "2017-12-04 16:51:34Z",
            "IdEndpoint": 25,
            "Label": "pippo",
            "Url": "http://pippo.pluto/"
        },
		...
        {
            "CreationDate": "2017-12-01 11:20:19Z",
            "IdEndpoint": 11,
            "Label": "My personalization",
            "Url": "https://www.mailup.com/personalization"
        }
    ],
    "PageNumber": 0,
    "PageSize": 20,
    "Skipped": 0,
    "TotalElementsCount": 11
}
Paging and filtering (example)

5 items per page, get first page (count starts from zero)

Retrieve an orderd list of the endpoint(s) using the clause orderby="idEndpoint desc". Parameter names can be retreived from the response body. Please note that filter matching is case sensitive.

NB: no ordering filtering querystring parameter provided!

...