Skip to main content
Question

identifiers vs "to" in transactional message

  • August 7, 2024
  • 1 reply
  • 65 views

Seems like it is compulsory to specify “to” address when sending a transactional message:

request='
{
  "transactional_message_id": "demo_transactional_message",
  "message_data": {
    "inviteLink": "your_invite_link"
  },
  "identifiers": {
    "id": "adc304c4-255b-42d3-bc3c-49..."
  }
}
'

echo $request | curl -v https://api.customer.io/v1/send/email \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer …...' \
-d @-

gives me:


{
  "meta": {
    "error": "Missing required field: \"to\""
  }

 

If I have to specify “to” address in the email, why do I need to specify the identifier? I was expecting that if I specify identifier (id of the person), it should automatically send the message to the email of the person associated with the id.

Can you please help me understand this?

 

Thanks,

Mayuresh

1 reply

Penny
  • 133 replies
  • August 12, 2024

Hi @Mayuresh ,

 

The reason why the identifier must be specified is so that we can associate the delivery back to the correct profile person in your Customer.io workspace. 

There could be instances in your use case where a transactional email goes out to 2 recipients, and we’d need the identifier to know which is the correct person based on the identifier to associate the delivery with.

Hopefully this helps to clarify! :)

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings