Whether you need to send a few hundred emails or a few million, we’re ready to help you deliver your message. Are you ready to get started?
We gave our activity details screen some, well, new details. We now show our Message ID and your Message custom ID. We’ve also added to the timeline. For Delivery and Bounce events we show a remote server response, and for Open and Click events we show a user agent that was used by the end user. Activity details screen also got a refreshed look, with message details and timeline data nicely separated for easier reading.
Legal stuff is boring, right? Well, maybe it is, but it’s critically important for us and our customers who manage personal information of their subscribers and trust us with some of the information, so we can help them deliver relevant emails. We’ve now gathered all out legal documents under one section of the website and guarantee that there are no other documents hiding around the corner. What you see is what you get. Dive into it if you please.
When you send an email with Coresender whether it’s via API or SMTP, we always give it a unique Message ID which is immediately returned to you for future reference. You may also assign a custom ID to each email. Today, we’re expanding the search capabilities of the Activity section in out control panel. You can now search by the Message ID we’ve assigned and also by the Message custom ID that you have assigned to your email. This opens up another way to troubleshoot your integrations.
We've made sure that all timestamps that we use in our API comply with the ISO 8601 standard, which means they should be both easy to ready and easy to parse with all standard tools. For the convenience of us, humans, we've decided to always present timezone as a time difference from the UTC. Because only some of us can resolve a timezone code to an actual time difference in our heads.
In the API documentation, we've improved our request example component. Now it better shows HTTP method and allows to copy the code to clipboard. A small but often requested change. Try it yourself in the example below.
curl -X POST https://api.coresender.com/v1/suppressions \
-H 'Authorization: Bearer oauth_access_token' \
-H 'Content-Type: application/json; charset=utf-8' \
-d $'{
"account_id": "a3c69540-3324-49a7-b595-5c310d9ca867",
"reason": "Imported from our internal system",
"recipient_email": "tasha@example.com"
}'