> For the complete documentation index, see [llms.txt](https://even-financial.gitbook.io/developer-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://even-financial.gitbook.io/developer-center/native-api-integrations/heloc/dos-and-donts-for-heloc-native-partners-api.md).

# Dos & Don’ts for HELOC Native Partners (API)

## **Dos**

* DO clearly display the product type and terms.
  * Include a tooltip or tappable element with a brief product description and overview of a HELOC. (A home equity line of credit (HELOC) lets you borrow money against the equity you have in your home.)
  * Any changes must be submitted for compliance review.
  * Include amount, APR, whether APR is fixed vs. variable, estimated monthly payment, and term length.
* DO ensure the consumer can reasonably compare offers. The more the consumer can do, the better. For example:
  * Sort or filter by: APR, Term, Payment
  * Add language such as, “We think this is a good option, but there may be more.”
    * For example, our disclosures state, “We do not connect you with every lender in the market, so other lenders and loans not listed on our service may be available to you, and those other loans may have different terms and conditions, including lower rates. We cannot guarantee the lowest price or best terms available in the market.”
* DO send us property status for leads (e.g. “rent”, “own with mortgage”, or “own”). EF will exclude renters.

## **Don’ts**

* DO NOT collect or send EF more than 5 pieces of information that constitute an application, per CFPB
  * The 6 pieces of information that constitute an application are Name, Income, SSN, Loan Amount, Address, and Property Value.
  * In our Loans vertical, we require everything but property value, so do not collect/send us that datapoint.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://even-financial.gitbook.io/developer-center/native-api-integrations/heloc/dos-and-donts-for-heloc-native-partners-api.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.