Data export
Scheduled snapshots of your application, funding, and compliance data, built to load into your data warehouse.
On this page· 8 sections
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 for more information.
All Data Export files are encrypted with your organization's PGP key and must be decrypted before use. See Key Exchange for more information.
Export schemas#
Each export has its own page with what a row represents, when it's delivered, and a searchable list of every field.
Base export
Application event
One row per application: applicant, property, underwriting, and status.
Funding transaction
One row per ACH funding attempt, including re-attempts.
User identity
Every Lead Portal user and account in your organization.
Loan officer license
One row per license, for each loan officer.
Wholesale
Originator broker
Broker details for third-party originator setups.
Intellidebt
Liability payoff reconciliation
Direct debt payoffs, one row per paid liability.
Regulatory
HMDA
Demographics and denial reasons to help with your HMDA filing.
Regulatory
MCR
Quarterly actions for your Mortgage Call Report.
Regulatory
Complaint
One row per complaint.
Waitlist
Applicants waiting for you to launch in their state.
By arrangement
Warehouse funding queue
Loans funding today, on a partner-specific schedule.
On request
Task outcome
Outcomes of compliance subtasks, such as cancellations.
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:
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 schedule can be utilized for report generation (where intervals are at least 4 hours apart).
Entity relationship diagram (ERD)#
Questions about file formats, encryption, or environments? See the FAQ.