---
title: "Create a scoring attributes report"
method: POST
path: "/v1/scoring_attributes/reports"
tags: ["Scoring Attributes"]
---

# Create a scoring attributes report

`POST /v1/scoring_attributes/reports`

## Request body

- ReportRequest
  - `lender_reference` string, required — This is the value that can be used by the lender to identify the report request. For example, this could be the loan application number.
  - `customer_identifier` string, required — This is a customer level unique identifier. This key should not use personally identifiable information such as SSN or government ID numbers.
  - `purpose` 'decisioning' | 'verification' | 'analytics', required — This field indicates the purpose of the report. Valid values are: ‘decisioning’ for FCRA credit decisioning, ‘verification’ for non-FCRA underwriting verifications and ‘analytics’ for retroactive reports used solely for analytical purposes.
  - `cutoff_date` string, required — The latest date of financial activity that will be included in the report. In most cases, this should be set to the current date or application date. In the case of retro-scored reports, this date will be a date in the past.
  - `loan_data_enabled` boolean, nullable — This field indicates whether the lender wants to include any supplied credit card and loan data in the calculation of metrics. Value defaults to false if field is not specified.
  - `institutions` object[], required
    - `identifier` string, required — This is a unique identifier for the institution.
    - `name` string, required — This is the name of the financial institution.
    - `data_source` 'aggregation' | 'direct', required — This field indicates where the data for this institution is sourced from. Valid values are ‘aggregation’ if the data is provided via a banking aggregation provider such as Truv, and ‘direct’ if the data is sourced directly from the financial institution.
  - `accounts` object[], required
    - `identifier` string, required — This is a unique identifier for the account. If you are using an actual account number, please provide an obfuscated number that only shows the last 4 digits (e.g. XXXX1234).
    - `institution_identifier` string, required — This is a unique identifier for the account's institution.
    - `type` 'checking' | 'savings' | 'cd' | 'mm' | 'deposit' | 'credit_card' | 'loan', required — This field indicates the type of account. Valid values are ‘checking’, ‘savings’, ‘cd’, ‘mm’ (money market), ‘deposit’ (for all other deposit account types, including prepaid accounts), ‘credit_card’ and 'loan' for all other loan accounts.
    - `balance_amount` number, double, required — This is current ending balance for the account. This should reflect posted transactions It should not be the available balance which includes pending transactions. For deposit type accounts, a positive balance indicates a positive balance held by the customer whereas a negative balance means that the account has been overdrafted. For loan and credit card accounts, a positive balance indicates the amount that the customer owes the lender whereas a negative balance indicates that the bank owes the customer (less typical).
    - `balance_date` string, required — This is the as of date for the provided balance.
    - `autopay` boolean, nullable — Indicates whether the account is used as the ach autopay account for the loan product being underwritten.
  - `transactions` object[], required
    - `identifier` string, required — This is a unique identifier for the transaction.
    - `account_identifier` string, required — This is a unique identifier for the transaction's account.
    - `post_date` string, required — This is the date that the transaction was posted to the account.
    - `amount` number, double, required — This is the amount of the transaction. Negative amounts indicate withdrawals from the account whereas positive amounts indicate deposits to the account. This is true for both deposit related and loan related accounts. Note: Some aggregators use positive amounts to indicate withdrawals and the signs need to be reversed prior to submission.
    - `status` 'posted' | 'pending', required — This field indicates the posting status. Valid values are ‘posted’ and ‘pending’.
    - `description` string, required — This is the transaction description. Provide as much description information as possible. Memo, check number and other supplemental fields can be concatenated. This field can be de-personalized by replacing the first and last name with \<FNAME\> and \<LNAME\> respectively. If you choose to de-personalize the description, please note that your match should be scoped properly, e.g. contain parts of both first and last name. For example 'Dave' is both a first name and also commonly used in merchant names (e.g. Dave and Busters). An unscoped match for this first name would result in other information from being improperly removed.

## Response `201`

Successful operation

- object
  - `report_id` string — This is a unique report_id generated by the scoring attributes API to identify a report.

## Other responses

- `400` — Bad request
- `401` — HTTP 401 Unauthorized
- `403` — HTTP 403 Forbidden

---

[API](https://skmtc.dev/truv/apis/truv-api.md) · [All operations](https://skmtc.dev/truv/apis/truv-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/truv/truv-api/revisions/d7195c30b6b1/schema)