{"id":23649,"date":"2019-07-16T00:00:00","date_gmt":"2019-07-16T00:00:00","guid":{"rendered":"https:\/\/www.mailgun.com\/blog\/nueva-events-api-seguimiento-detallado-de-emails-y-busqueda\/"},"modified":"2026-09-16T10:55:58","modified_gmt":"2026-09-16T10:55:58","slug":"nueva-events-api-seguimiento-detallado-de-emails-y-busqueda","status":"publish","type":"blog","link":"https:\/\/www.mailgun.com\/es\/blog\/product\/nueva-events-api-seguimiento-detallado-de-emails-y-busqueda\/","title":{"rendered":"Nueva Events API, seguimiento detallado de emails y b\u00fasqueda"},"content":{"rendered":"\n

We are excited to announce the release of our latest API to make life easier for developers. Our completely refactored Events API makes it easy and fast to determine exactly what happened with each and every one of your emails. Just like Fedex gives you a tracking number that lets you follow the entire shipping process, our events API lets you keep track of every single event associated with your email, even events that occur after the email was delivered.<\/p>\n\n

We\u2019ve also updated the Logs<\/a> tab in our control panel to use the Events API so you\u2019ll see more detailed information there, as well. You will now see events that occur after the email is delivered like opens and clicks. You can also perform more detailed searches, like search for all the events that happened to a particular message by searching by message-id.<\/p>\n\n

These detailed logs are available at no additional charge for Mailgun customers. Customers using a free-trial account will receive at least 2 days of event storage, and customers with a paid account, will receive at least 30 days.<\/p>\n\n

Now, onto the details of why we are so excited about the new API:<\/p>\n\n

Powerful<\/h2>\n\n

Mailgun customers regularly send millions of emails per month, so finding the status of a specific email can be like finding a needle in a haystack. To help with this, we\u2019ve added a bunch of filtering parameters and allow you to combine filters to create complex queries. We have also improved the method for polling the API. Previously, our Events API just had simple skip and limit parameters to specify which portions of the logs you wanted to fetch. This was cumbersome and resulted in poor performance. With the new Events API, we\u2019ve provided parameters that allow you to specify a time period in addition to the ability to specify ascending or descending order. We also provide URLs in the response for retrieving the next and previous pages, giving you the ability to easily traverse log data, no matter how many records are returned. If the end date of the time range is not specified and the traversal is ascending (forward in time) you will eventually receive an empty page (i.e., end of the data set). You can use the same URL at a later time and the result will contain log entries written since the previous request.<\/p>\n\n

Performant<\/h2>\n\n

We built the API to be highly performant, even across 10s of millions of log entries. To do this, we built the API on top of\u00a0ElasticSearch<\/a>, an open source framework for building real-time search and analytics. We will do a follow up post about the architectural details.<\/p>\n\n

Below are the parameters and some examples of how to use the API.<\/p>\n\n

API Parameters<\/h2>\n\n
\"Screen_Shot_2019-08-27_at_14\"<\/figure>\n\n

Filter Field Parameters<\/h2>\n\n
\"Screen_Shot_2019-08-27_at_14\"<\/figure>\n\n

You can create complex queries by combining parameters:<\/p>\n\n

\"Screen_Shot_2019-08-27_at_14\"<\/figure>\n\n

Here are some examples: Subject is \u201cOnly one day left to save!\u201d AND recipient is \u201ccustomer@example.com\u201d OR \u201cpaul@example.com\u201d<\/p>\n

\r\n