Skip to content

Data Export API


Branch’s new Data Export API for People-Based Attribution can be used to pull granular Branch event data directly. A few important notes for this API:

  • The data will only be retrievable for the last 7 days
  • The data will only appear after end of day since it's processed every 24 hours
  • The data will not be visible prior to your whitelisting date. After you sign up, data will be generated for the next UTC day or the following UTC day.
  • The data will only be visible for your live key (not your test key)

Data Feeds is a premium solution

The Data Export API is included in Branch’s Data Feeds offering, which can be purchased according to Branch’s pricing schedule, and is available at no additional charge to customers who are on Launch and Startup plans for Journeys, Universal Email, or Universal Ads. Without Data Feeds, you can still export Branch data in CSV form directly from the Branch dashboard via Sources or CSV Exports.

Third party access

Any user with access to an account’s API keys will be able to access Branch’s Data Export API (and thus unfiltered, log-level data). As a result, we would recommend against providing third parties (agencies and ad partners) with the permissions required to view API keys - Sensitive Data and App-Level Settings - during the invitation process.

If you are looking for the legacy Data Export API, please see these docs.


In order to use this API you must have an App ID and a Branch Public Key. You must also have a Data Feeds subscription. In order to enable the Data Export API, navigate to Data Import & Export in the Branch dashboard and then toggle on the Data Export API using the slider on the Manager page.

You can find your keys in your Account Settings.

Base URL:


Query Parameters

branch_key required : The Branch key of the originating app

branch_secret required : The Branch secret key of the originating app

export_date required : The UTC date of the requested data export

Example request:

curl -X POST -H 'content-type:application/json' -d '{"branch_key":"key_live_gcASshuadd7l39m36NhdsDPWRjmkdcgh12jsg1", "branch_secret": "secret_live_ztPsdKIjUtcjkUYF732nsl81HJ75BJqiv24J86", "export_date": "2017-10-01"}'


The response payload will be in JSON format and for each export it will have an array of paths to files on S3 to download. Note that there may be multiple files (depending on the size of the day's export) and that each csv file will be gzipped.

  "eo_branch_cta_view": [""],
  "eo_click":[ ""],
  "eo_commerce_event": [""],
  "eo_custom_event": [""],
  "eo_install": [""],
  "eo_open": [""],
  "eo_pageview": [""],
  "eo_reinstall": [""],
  "eo_sms_sent": [""],
  "eo_web_session_start": [""]

All exports via Data Feeds are powered by Branch's People-Based Attribution. For an exhaustive list of events included in these exports and more detailed definitions of each event, please see the Event Ontology Data Schema.


A full day's files will be available on our S3 bucket at that location to download around 7:00pm UTC. It will return a blank array from S3 for any empty files until the UTC day is over and the data has been transfered to S3, therefore it is recommended you schedule any ETLs to fetch the data for the previous day around 7:00pm UTC (12pm PST).


Time Limits

Data will be available through the API only for 7 days after the date it's posted. If you need a record of your data for longer than 7 days, please set up a recurring export and store data in your systems.

Exporting beyond 7 days

In accordance with our internal policies related to GDPR and other data protection laws, we hash many fields, including IP address and advertising identifiers, after 7 days. This means that if you want to export data beyond 7 days, either via the Dashboard's CSV Exports or by requesting a manual data dump, these fields will no longer contain the original values. For this reason, we highly recommend you always export raw data within 7 days.