Read this before you call it. Creating a document type changes what
your borrowers are asked for, across your whole account, straight
away — and this API cannot undo it.
- It appears on every existing loan whose details match its
conditions, including loans already in progress with borrowers
part-way through. - There is no draft, no preview, and no "apply later". The change is
live the moment this call succeeds. - There is no delete in this API. If you create the wrong thing,
someone has to go into the LendingWise portal to deal with it.
Empty conditions mean "every loan", not "no loans". This is the
mistake worth guarding against, and it is why a request with no
conditionalFilters at all is refused unless you also send
appliesToAllLoans: true. Sending that flag is you saying, on the
record, that you meant every matching loan in the account.
conditionalFilters are combined with AND. A loan has to match all of them
for the document to be asked for. Any filter list you leave empty
places no restriction on that dimension.
One call can create more than one entry. fileTypes is a list, and
you get one entry back per loan type — the same way the portal shows one
row per loan type. The reply is the created type read back from the
catalog, in exactly the shape GET /api/v4/document-types returns, so
you can confirm the scoping is what you meant.
Names must be unique on your account, compared without regard to
case or accents (so Cafe and Café collide), and across every
loan type. A clash with an existing type is
refused. A clash with a deactivated type is also refused, with a
different message: reactivate the original in the portal instead, or
you will orphan its conditions and history.
This endpoint only creates. There is no update and no delete.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||

