Reputation: 303
We have an application which is calling the Trustpilot API to send out invitation e-mails to customers so that they can review their recent orders.
Creating the review link etc. works correctly. However, when calling the final step to actually send out the invitation e-mail, the "status" field of the response is always "notsent" and the e-mail is not sent.
The URL is https://invitations-api.trustpilot.com/v1/private/business-units/business_unit_id/invitations
The JSON response is as follows:
{
id: "<response id>",
businessUnitId: "<business unit id>",
businessUserId: "<business user id>",
recipient: {
name: "<recipient name>",
email: "<recipient email>"
},
referenceId: "<order id>",
templateId: "<default en-GB template code>",
locale: "en-GB",
sender: {
email: "[email protected]",
name: "<client name>"
},
replyTo: "[email protected]",
createdTime: "2015-04-29T14:34:40.176727Z",
preferredSendTime: "2015-04-29T14:34:40.176727Z",
sentTime: null,
tags: [ ],
redirectUri: "<trustpilot review url>",
status: "notsent",
source: "Kickstart"
}
We have not modified the SPF record for the client's domain, so I am using [email protected] as the sender and reply-to addresses. Additionally, I have set the preferred send time so that the e-mail should be sent straight away. Nothing I do is making any difference.
Can anyone advise what I might be doing wrong?
Upvotes: 2
Views: 1942
Reputation: 78
The reply-to address should be one of the pre-configured addresses in your B2B account. You can see here: https://support.trustpilot.com/hc/en-us/articles/201841237-Sender-Information
Upvotes: 0
Reputation: 303
Figured this out - the reply to address I was specifying was being rejected. Even though it was valid (or when I tried using noreply.invitations...) - I switched to using one that the client has been using themselves and they started sending straight away after that.
Upvotes: 1