Page Comparison

...

Description

Retrieve the personalization endpoint configuration details

HTTP Method

GET

URL

Code Block

language	xml

https://services.mailup.com/API/v1.1/Rest/ConsoleService.svc/ConsolePersonalization/Endpoints/{id_endpoint}

JSON request (example)

none

JSON response (example)

Expand

Code Block

{
    "CreationDate": "2017-12-01 11:20:19Z",
    "IdEndpoint": 11,
    "Label": "My personalization",
    "Url": "https://www.mailup.com/personalization",
    "Credentials": {
        "Password": "****",
        "Username": "test"
    },
    "Headers": [],
    "Parameters": [
        {
            "Field": "[field1]",
            "FieldTestValue": "Giancarlo",
            "Name": "name"
        }
    ],
    "Recipient": {
        "Field": "[email]",
        "FieldTestValue": "test@example.com"
    },
    "UpdateDate": "2017-12-01 11:25:37Z"
}

Paging and filtering (example)

none

Create an endpoint

What to know before start creating endpoint

Expand

title	Follow these few lines to understand which data you to a create recipient-related urlWhat to know before start creating endpoint....

Does your service need a Basic authentication?	Provide Username and Password using Credentials field.
Does your service need specific headers?	Provide key-value data using Headers field.
Does your service get the recipient using email or mobile number from the url?	You can use Recipient field, providing one of theses placeholders: [email] [mobilenumber] [fieldX] where X represent the dynamic content field unique identifier
Does your service get the recipient using data from the querystring?	You can use Parameters field, providing one of these placeholders: [email] [mobilenumber] [idconsole] [idlist] [idnl] [fieldX] where X represent the dynamic content field unique identifier

...

Versions Compared

Old Version 6

New Version 7

Key

Create an endpoint

What to know before start creating endpoint