Usage of Front's Events API and the q query string Our operations team would like to take advantage of Events data and I’m working on interpreting the API documentation.The documentation says: Lists all the detailed events which occured (sic) in the inboxes of the company ordered in reverse chronological order (newest first).But we are given the following query param:q stringSearch query object with optional properties before, after, or types. before and after should be a timestamp in seconds with up to 3 decimal places. types should be a list of event types. I did some digging and discovered how the Search Query Object is defined, kind of. Looks like we can search using the before: and after: available here, but this appears to only index on conversations created_at, created before/after the supplied parameter. Given that this is an event endpoint, I find this behavior confusing. Surely multiple events can occur after a conversation is created. Is the proposed way of interacting with this endpoint to:1. run a backfill, or at least for
