Some of it. Device ID passback is delivered as a file drop, and most report data can be exported. There is no results API today, and a few specific exports are missing.
What you can get
Device ID passback: a CSV dropped to a cloud bucket and refreshed on a weekly cadence during the flight, carrying device ID and device type. It is included in the analytics fee and used by the large majority of customers.
Report data from the dashboard, including visits and conversions in the CSV columns.
Dashboard access itself is granted by your account executive rather than by the analytics team, which is worth knowing before you ask the wrong person.
What is missing today
No public customer API for analytics results: AdQuick has APIs, and there is developer documentation for media buying, but lift and attribution result objects are not exposed through them. Results come as files rather than as an endpoint into your warehouse.
No point-of-interest address export: the location list you uploaded cannot be pulled back out of the campaign map.
No Singular integration: app events from Singular have to be exported and uploaded to a template.
No event-level exposed-to-conversion dataset: it is not a standard output. Only converting mobile ad IDs come back, and your own internal user IDs cannot be passed through the pixel and returned matched.
If an export you need is not listed here, ask. Several of these have manual workarounds that we can run once.