Hello
In the definition of the parameters of the POST /api/v2/conversations/emails/agentless endpoint, toAddresses is an array. However, whenever I try to send an email to multiple addresses, it returns a 400 error:
Email address list is too large. Only a maximum of 1 is allowed
Why is it defined as an array if only 1 is allowed? Is it planned to change this in the future?
Hi Adrian,
I just got done talking with the product manager. The team was future-proofing the API. There are a number of services involved with the agentless endpoint. Not all of the backend services support sending multiple outcomes. So to prevent having to do a breaking change in the future by moving from a non-array type to an array type, they used an array for the field and then by a maximum size of 1 on the field.
However, they didn't put that size limitation in the documentation or on the API specification. I have talked to the product manager and they will update the document. The product manager did not have an ETA on when they would update the constraint. Part of the reason for the vagueness is they have to work through whether the multiple emails being sent in the toAddresses would be part of the same conversation or would be individual conversations. That design decision has some implications for our backend billing engine.
I hope that provides some context.
Thanks,
John Carnell
Director, Developer Engagement
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.