---
title: Data integration FAQ
description: Common questions about exchanging files with Figure and ingesting Data Export files.
---

## File exchange

### Does Figure need our AWS access keys?

**Not for the recommended cross-account IAM role path** — Figure assumes your delivery role using short-lived credentials. If you use the static access key path under [Partner-hosted S3](/data-integration/file-exchange/aws-s3#partner-hosted-s3-bucket), yes: we coordinate those credentials during onboarding over a secure channel. [Partner-hosted GCS](/data-integration/file-exchange/google-cloud-storage#partner-hosted-gcs-bucket) avoids AWS keys entirely when you can use Google Cloud Storage.

### Does Figure's uploader run in AWS? Does it use an execution role in our account?

Figure's platform runs on Google Cloud. Figure does not run compute in your AWS account. For partner-hosted S3, Figure **does** call AWS APIs in your account by **assuming an IAM role you create** (Role B) with temporary credentials — Figure does not install or operate an ongoing execution role inside your VPC.

### Can Figure assume a role in our account using an ExternalId?

Yes. This is the [recommended partner-hosted S3 path](/data-integration/file-exchange/aws-s3#cross-account-iam-role-recommended). Your delivery role trust policy must allow the Figure Role A ARN for that environment (provided during onboarding) and, when required, the ExternalId you share with Figure over a secure channel.

### Do you currently support cross-account IAM role access instead of long-lived access keys?

Yes. Multiple partners deliver and receive files this way in production. Coordinate Role B, ExternalId, and bucket details with Figure during onboarding. [Partner-hosted GCS](/data-integration/file-exchange/google-cloud-storage#partner-hosted-gcs-bucket) is also keyless if you prefer Google Cloud Storage.

### What egress IP ranges does file delivery use?

See [File-exchange IP addresses](/ips#file-exchange-ip-addresses). API traffic uses a different list on the same page.

### Is there a non-production environment? Can you provide sample or dummy data?

Yes. Test and production are separate. Data Export test files use a `test_` prefix. For a schema-matched sample with dummy data, contact your Figure representative or [partner-help@figure.com](mailto:partner-help@figure.com).

### What is the expected file delivery cadence? Full snapshot or delta?

For Data Export, Figure delivers full snapshots on a configurable schedule (default tables are on [Data Export](/data-integration/data-export#delivery-schedules-and-data-freshness)). Cadence for other file exchanges is agreed during onboarding.

## Data export

### Will Figure deliver full exports or delta-files?

Figure will only deliver full exports. These are database snapshots as of when the report is generated.

### What will the file type/extension be?

Figure can send comma-separated `,` (`.csv`) or pipe-delimited `|` (`.txt`) files.
`.csv` is the default.

Only flat files are supported. Other formats like `.json`, `.xml`, `.xlsx`, or MISMO (also known as “3.4” files) are not supported.

We will apply field value quoting where necessary to escape delimiting characters.

### Can my reports be encrypted?

PGP encryption is required. Send Figure your organization's public PGP key; do not send the private key. See [Key Exchange](/key-exchange#pgp-keys-for-encryption).

### Does my organization really need to ingest all the information provided?

Your organization likely does not need to ingest all the information provided in these files. For example, broker information is only applicable to companies using a wholesale/broker model.

Review the datapoints and socialize them internally to ensure all departments (sales, compliance, business intelligence, accounting, finance, etcetera) have their needs met.

### What delivery methods are supported?

These reports can be downloaded from the Lead Portal system.

At your request, we can also deliver a copy of the reports to a secure storage solution hosted by your organization. Partner-hosted Google Cloud Storage is recommended. See [File Exchange](/data-integration/file-exchange) for setup details.

### How will test / production environments be reflected in the exports?

All files from our test environment will have a prefix `test_`. Production files will have no prefix. Export files will never mix test and production data.

See [File Naming Conventions](/data-integration/data-export#file-naming-conventions) for more detail.