Subrite email configuration

Step 1:

Create a M2M token granting Communication permissions. You will receive the token once you click save.

Step 2:

Use the get senders API call to get sender list.

• Method: GET
• Route: {baseUrl}/api/v1/communications/email/senders
• CommunicationChannel: email
• Authorization: Bearer token (use the m2m token collected in ## details)

In the response you will find the sender list:

[
  {
    ...
    "senderName": "Subrite",
    "id": 1,
  },
  {
    ...
    "senderName": "Subrite two",
    "id": 2,
  }
]

Step 3:

Use the segments/published API call to get list.

• Method: GET
• Route: {baseUrl}/api/v1/segments/published
• Authorization: Bearer token (use the m2m token collected in ## step 1)

In the response you will find the list:

[
  {
    "id": 1,
    "name": "List 1",
    ...
},
  {
    "id": 2,
    "name": "List 2",
    ...
  }
]

Step 4:

Use the api/v1/communications/email/tokens API call to get Personalized tokens.

• Method: GET
• Route: {baseUrl}/api/v1/communications/email/tokens
• Authorization: Bearer token (use the m2m token collected in ## step 1)

In the response you will find the list:

{
  "memberInfo": [
    "fullName",
    "nickName",
    "email",
    "dateOfBirth",
    "phoneNumber",
    "address",
    "zipCode",
    "city",
    "country",
    "unsubscribeLink",
    "mufcNumber",
    "muscNumber"
  ],
  "myPageLink": [
    "consentLink",
    "invoiceLink",
    "subscriptionLink",
    "podcastLink"
  ]
}