Open dyler opened 8 years ago
Hi! I wasn't aware of that... and yes that's a good idea. We should implement that.
Ok, I'm going to start doing things. I've been working in production with the library already so I'm gonna explore the API and develop the method to get DeliveryStatus with HTTP API. Also send with HTTP API. Regards!
I think this is the distribution of files we should follow to extend the Library: http://imgur.com/pXNXwTU We also should separate the Controller or API that creates the object and exposes the methods to use from the Application layer, so you create an object ElasticemailWebApi that makes use of services and DTOs and DataObjects of the project. Everything will be the same but that object would have no logic, that could be implemented in the services (HTTP calls and everything). Let me know if you like this idea. Regards!
Thanks for the good project! I see that there's a very good C# class that is downloadable from this page: http://elasticemail.com/support/http-api/integration-libraries It already has all the api calls and options implemented for v2. It may be a help with this project... Thanks again for posting your project!
Hi, i'm wondering, what are the different values that the
DeliveryStatusResponse.DeliveryStatus.Status
and what are the meanings of the individual values.
Thanks guys. Great job!
Hi, I've been using this package to consume Elastic Email's API. Yesterday I found they have an amazing HTTP API version 2 that can be consumed. This API returns JSON instead of XML (that is more friendly with c#) so I guess it's a good idea to implement version 2 for sending and getting statuses apart from other actions we can implement too.
This is the documentation: http://api.elasticemail.com/public/help#Email_header
Regards!