- 24 Sep 2024
- 4 Minuten zu lesen
- Drucken
- DunkelHell
- pdf
eDiscovery APIs in Airtable
- Aktualisiert am 24 Sep 2024
- 4 Minuten zu lesen
- Drucken
- DunkelHell
- pdf
Enterprise Scale | |
Admins only | |
Platform(s) | Web/Browser, Mac app, and Windows app |
Related reading |
Airtable provides a set of eDiscovery APIs to customers on our Enterprise Scale plan to export base data from Airtable. Customers can use these exports to review base content or preserve base data in third-party systems for compliance reviews and other security purposes.
eDiscovery Overview
There may be scenarios where you need to export the data stored within Airtable as part of a legal review hold or other compliance-related scenario. We provide a set of APIs that allow you to export the data stored in bases in formats that meet your team’s needs (CSV and JSON). We also provide metadata about base usage to better inform your team’s assessment of base data.
Getting an eDiscovery Export
NOTE
To use eDiscovery APIs in Airtable, you must be an admin in your organization and provision a PAT with the required permissions.
The eDiscovery API allows you to asynchronously request an export and then check the status of your export request.
Creating an export request: Step 1
NOTE
Before starting the export process, locate the base ID you are trying to export (formatted as appxxxxxxxx).
To locate your base ID:
Visit your admin panel.
Click Bases.
Search for your preferred base under the “Base name” column.
Base IDs are visible immediately below your base’s name.
NOTE
You can also use audit logs if you need to determine which bases you need to export based on specific activity of users within your organization.
To access your audit logs:
Visit your admin panel.
Click Reports.
Enter your preferred date and select any necessary filters under the "Audit log" section.
Click Download report or Generate new report.
NOTE
Additionally, you can review user details in the admin panel to understand which bases your users can access.
To access your user details:
Visit your admin panel.
Click Users.
Click on your preferred user’s name.
Click Bases.
Creating an export request: Step 2
NOTE
After locating your base ID, POST a request to the Create eDiscovery API endpoint. Detailed documentation is available here.
Currently, bases can only be exported one at a time.
You can request that an email be sent to you once the request is submitted, which proactively notifies you when the export request is complete and provides a download link.
The default export format is a JSON object, but CSV is also available.
10 minutes is the maximum time we allow an export request to run.
If your request succeeds, you will receive a response with an
enterpriseTaskId
. You will use this value to check the status of your export request.
Checking your export status
NOTE
You can review your eDiscovery export status by making a GET request to the eDiscovery API endpoint ( details here).
Your export will be in one of the following states:
Pending – the export task is queued but has not started.
Processing - the export task is in process.
Error - the export task failed and hit an unexpected error. In this circumstance, you should retry or submit a support request.
Done – the export is complete, and the request should contain links to the export files.
Suppose you do not specify the enterpriseTaskId
when checking the export status. In that case, you will receive a list of all in-progress and past export requests and their status. The endpoint will return all exports created by all admins across the organization.
Export format breakdown
The eDiscovery APIs contain an export of the data stored within your base—including all raw data stored within a base’s tables and all active record comments within your base.
Export format breakdown details
The following values are not included in exports:
Calculated column values (like rollups or formulas)
Interface layout information
Automation configuration details
Extension usage and details
NOTE
Exports do not contain record revision history or information about deleted records. If you want to monitor a change log of all Airtable data and store it in a 3p system, check out our Data Loss Prevention offerings.
JSON export details
NOTE
The default behavior of the eDiscovery API is to provide an export in a single JSON file. The JSON file contains each record's raw details, metadata, and comments.
Important objects in the JSON export
Field name | Description |
---|---|
tablesById | Contains a map of tables in the base with details including its name, time created, and the relevant fields within the table. |
recordsById | Contains a map of records by recordID with each record including the list of corresponding field values. |
recordCommentsById | Contains comment details for each specific record. |
recordsMetadataById | Contains list of metadata for each record in the table:
|
CSV export details
NOTE
Another option for customers is to export base data as a CSV. The eDiscovery API returns a URL into a .zip file containing the relevant CSV structure for a base.
Two CSVs are generated per base table. The first CSV contains the table export, while the second contains all the comments made on records within that table. The CSV table export contains all non-calculated fields for the records in a table. Additionally, to provide more metadata about the table, the CSV has the following additional information:
The record creation and last modified times.
The userID of the user who created and last modified the record.
Known limitations:
Calculated columns do not have values in the export, but the column are present in the export.
This includes formulas, rollups, and lookup fields.