<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic request_id in team_log/get_events and associating API actions with events in Dropbox API Support &amp; Feedback</title>
    <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/request-id-in-team-log-get-events-and-associating-API-actions/m-p/414301#M22348</link>
    <description>&lt;P&gt;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).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is this the recommended way of doing this? Why am I seeing these numbers?&lt;/P&gt;</description>
    <pubDate>Mon, 27 Apr 2020 05:03:34 GMT</pubDate>
    <dc:creator>dtheodor</dc:creator>
    <dc:date>2020-04-27T05:03:34Z</dc:date>
    <item>
      <title>request_id in team_log/get_events and associating API actions with events</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/request-id-in-team-log-get-events-and-associating-API-actions/m-p/414301#M22348</link>
      <description>&lt;P&gt;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).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is this the recommended way of doing this? Why am I seeing these numbers?&lt;/P&gt;</description>
      <pubDate>Mon, 27 Apr 2020 05:03:34 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/request-id-in-team-log-get-events-and-associating-API-actions/m-p/414301#M22348</guid>
      <dc:creator>dtheodor</dc:creator>
      <dc:date>2020-04-27T05:03:34Z</dc:date>
    </item>
    <item>
      <title>Re: request_id in team_log/get_events and associating API actions with events</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/request-id-in-team-log-get-events-and-associating-API-actions/m-p/414589#M22355</link>
      <description>&lt;P&gt;Unfortunately, as 'X-Dropbox-Request-Id' isn't officially documented or guaranteed, I can't&amp;nbsp;recommend relying on it like this.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It can be useful when working with&amp;nbsp;Dropbox to debug issues, but we don't currently guarantee it, due to some various&amp;nbsp;backend details.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'll send this along as a feature request to make this reliable and documented, but I can't guarantee if/when that might be done. Apologies I don't have a better answer for you!&lt;/P&gt;</description>
      <pubDate>Mon, 27 Apr 2020 18:05:12 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/request-id-in-team-log-get-events-and-associating-API-actions/m-p/414589#M22355</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2020-04-27T18:05:12Z</dc:date>
    </item>
  </channel>
</rss>

