I am developing Dropbox apps, utilizing both User and Business endpoints to perform actions on files, as well as the event log for analytics purposes. I am looking to associate file actions performed by the app through API calls (e.g., a file download through the "/files/download" endpoint) with the corresponding events as they appear in the event log (e.g. the corresponding "file_download" event).
As far as I can tell, the only deterministic way to associate API actions with their correspondings events is through the "origin.access_method.api.request_id" attribute of the events. There's an undocumented "x-dropbox-request-id" header returned in all HTTP POST API requests to dropbox, which must carry the same value with the event field.
I have some reservations about whether this works, because from a quick look at event data I retrieve from the API, only 70% of events with the api access method carry a proper request_id, such as "dbarid:d34db33f890..." . The rest of them have a placeholder value of "dbarid:". There's nothing special I can point out about the events missing the request-id, they are recent events of a multitude of event types. Also the fact that the request-id header is undocumented is discouraging.
Is this the recommended way of doing this? Why am I seeing these numbers?
