---
title: Data export
description: Scheduled snapshots of your application, funding, and compliance data, built to load into your data warehouse.
---

## Use cases

Figure provides a set of data export files that our loan originator partners can use to access application data in bulk. These are database snapshots captured, packaged, and made available on a regular schedule.

These exports are designed to be ingested into a data warehouse. Our partners have used these files to enable integrations with their own loan origination systems, customer relationship management systems, or business intelligence reporting systems.

The report files can be used as-is, however it is recommended to ingest these files into a data warehouse.

Figure can deliver these files to a secure storage solution hosted by your organization, or they can be downloaded manually from Lead Portal. See [File Exchange](/data-integration/file-exchange) for more information.

{% callout type="info" %}

All Data Export files are encrypted with your organization's PGP key and must be decrypted before use. See [Key Exchange](/key-exchange#pgp-keys-for-encryption) for more information.

{% /callout %}

## Export schemas

Each export has its own page with what a row represents, when it's delivered, and a searchable list of every field.

{% cards columns=3 %}
{% card title="Application event" href="/data-integration/data-export/application-event" icon="file" eyebrow="Base export" %}
One row per application: applicant, property, underwriting, and status.
{% /card %}
{% card title="Funding transaction" href="/data-integration/data-export/funding-transaction" icon="receipt" %}
One row per ACH funding attempt, including re-attempts.
{% /card %}
{% card title="User identity" href="/data-integration/data-export/user-identity" icon="user" %}
Every Lead Portal user and account in your organization.
{% /card %}
{% card title="Loan officer license" href="/data-integration/data-export/loan-officer-license" icon="check" %}
One row per license, for each loan officer.
{% /card %}
{% card title="Originator broker" href="/data-integration/data-export/originator-broker" icon="building" eyebrow="Wholesale" %}
Broker details for third-party originator setups.
{% /card %}
{% card title="Liability payoff reconciliation" href="/data-integration/data-export/liability-payoff-reconciliation" icon="exchange" eyebrow="Intellidebt" %}
Direct debt payoffs, one row per paid liability.
{% /card %}
{% card title="HMDA" href="/data-integration/data-export/hmda" icon="landmark" eyebrow="Regulatory" %}
Demographics and denial reasons to help with your HMDA filing.
{% /card %}
{% card title="MCR" href="/data-integration/data-export/mcr" icon="chart" eyebrow="Regulatory" %}
Quarterly actions for your Mortgage Call Report.
{% /card %}
{% card title="Complaint" href="/data-integration/data-export/complaint" icon="help" eyebrow="Regulatory" %}
One row per complaint.
{% /card %}
{% card title="Waitlist" href="/data-integration/data-export/waitlist" icon="users" %}
Applicants waiting for you to launch in their state.
{% /card %}
{% card title="Warehouse funding queue" href="/data-integration/data-export/warehouse-funding-queue" icon="landmark" eyebrow="By arrangement" %}
Loans funding today, on a partner-specific schedule.
{% /card %}
{% card title="Task outcome" href="/data-integration/data-export/task-outcome" icon="list" eyebrow="On request" %}
Outcomes of compliance subtasks, such as cancellations.
{% /card %}
{% /cards %}

## Best practices for data warehouse ingestion

### Datatypes of date & time fields

Some exports mix `DATETIME` and `TIMESTAMP` datatypes. Unless noted otherwise, assume UTC as the timezone.

### Create field-name-specific ingestion logic

When creating your process to ingest these files, write field-name specific logic (*not* field-position specific logic) to pull fields into your data warehouse.

Figure does add fields as necessary (like when releasing new product features), and will add fields to the position we identify as most appropriate, often not at the right-most position or end of the file schema.

This approach ensures stability of your ingestion process, and allows your organization to reduce overhead by only ingesting and processing the fields they need.

## File naming conventions

The convention is:
`[partner_name]_[report_type]_[yyyymmddhhmmss].[extension]`

For example if your company is named ‘ACME Loans’, the report is `funding_transaction`, and the UTC timestamp is January 1, 2025 at 10:45:00 the file name would be:
`acme_loans_funding_transaction_20250101104500.csv`

If in the test environment, the file would be:
`test_acme_loans_funding_transaction_20250101104500.csv`

## Delivery schedules and data freshness

Data provided in these exports may be up to 8 hours old.

All delivery schedules can be modified upon request.

The recommended schedule is:

| Report Type | Delivery Schedule |
|-------------|-------------------|
| lkup_application_event{% br /%}funding_transaction | 02:45{% br /%}06:45{% br /%}10:45{% br /%}14:45{% br /%}18:45{% br /%}22:45 UTC (daily) |
| user_identity{% br /%}loan_officer_license{% br /%}originator_broker{% br /%}liability_payoff_reconciliation | 10:45 UTC (daily) |
| hmda{% br /%}mcr_v2{% br /%}complaint{% br /%}waitlist | 10:45 UTC on the 3rd of the month |

Each export's page also lists its own default schedule.

The `warehouse_funding_queue` report will be delivered on a partner-specific basis and timeline. `warehouse_funding_queue` is not subject to the 8-hour data freshness limitation.

HMDA and MCR files are not necessary to be delivered every day. We’ll generate these on the 3rd of the month at 10:45 UTC by default.

There may be a delay of a few minutes between report generation (based upon the schedule chosen) and report delivery. Any standard [unix-cron](https://crontab.guru/) schedule can be utilized for report generation (where intervals are at least 4 hours apart).

## Entity relationship diagram (ERD)
{% embed src="https://lucid.app/documents/embedded/a28ee6a6-e458-4a91-bc7f-22b1af6ff2ae" title="Data export entity relationship diagram" height=600 href="https://lucid.app/lucidchart/a28ee6a6-e458-4a91-bc7f-22b1af6ff2ae/view" /%}

Questions about file formats, encryption, or environments? See the [FAQ](/data-integration/faq#data-export).