Data Export
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.
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
File Descriptions
- Application Event
- Funding Transaction
- User Identity
- Loan Officer License
- Originator Broker
- Liability Payoff Reconciliation
- HMDA
- MCR
- Complaint
- Waitlist
Delivery Schedules and Data Freshness
Figure creates the database snapshots every 4 hours. This is a fixed schedule.
Figure can send these snapshots at any time, but the underlying data is refreshed every 4 hours.
All delivery schedules can be modified upon request.
The recommended schedule is:
| Report Type | Delivery Schedule |
|---|---|
| lkup_application_event, funding_transaction, funding | 02:45, 06:45, 10:45, 14:45, 18:45, 22:45 UTC (daily) |
| user_identity, loan_officer_license, originator_broker, liability_payoff_reconciliation | 10:45 UTC (daily) |
| hmda, mcr_v2, complaint, waitlist | 10:45 UTC on the 3rd of the month |
The warehouse_funding_queue report will be delivered on a partner-specific basis and timeline.
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)
Export Contents FAQ
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?
We support (and strongly encourage) PGP encryption, just send us the public key you’d like us to encrypt with.
All files must be encrypted if encryption is enabled.
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. See File Exchange for more information.
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 for more detail.