We have a requirement to build a custom Web application that would allow call centre agents to view a list of mailings to a customer and then resend a particular mailing to them. This could be because they had an invalid email address (and it has now been corrected) or simply because customer can't find it in their mailbox. The current process that we have used is:1) REST API - /databases/{dbid}/contact/{id}/messages
This returns messageName and SentDate. This is used to display a list of mailings of a user.

Once an agent selects which mailing to re-send; we then have to use the following XML APIs
1) Get Message Templates. This returns all templates in the system. We then have to iterate over all and do a substring match between MailingName and MessageName to get the template ID of the mail to send.
2) Create Contact List
3) Add Contact to Contact List
4) Schedule Mailings. This requires a template ID - hence the call to Get Message Templates.

If the first RESTful API to get contact messages is enhanced to return the following additional fields; it will simplify our solution and not require us to iterate over an ever expanding list of templates.

1) TemplateId - required for schedule mailings
2) MailingId - required for forward to Friend
3) Subject - more user friendly for call center agents than Message Name