> ## Documentation Index
> Fetch the complete documentation index at: https://docs.finosu.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Connect your lending platform to Finosu for origination and collections.

Finosu helps lenders automate borrower outreach across origination and collections.
Use the API to enroll applications in configured calling cadences, submit
customers and loans for collections, retrieve call history, and manage servicing.

## Start building

> [card] [Make your first request](https://docs.finosu.com/concepts.md)
>
> Authenticate with your company API key and retrieve a task-type catalog.

> [card] [Choose a workflow](https://docs.finosu.com/common-workflows.md)
>
> Follow the steps for enrollment, loan boarding, call results, or stopping servicing.

## Choose your integration

| Your goal | Start here |
| - | - |
| Contact new leads or returning borrowers | [Origination overview](https://docs.finosu.com/api-reference/origination/overview.md): enroll an application or submit a list using your configured cadence. |
| Board customers and loans for collections | [Collections task types](https://docs.finosu.com/api-reference/endpoint/collections/task-types.md): follow the customer-and-loan boarding flow for your account. |
| Retrieve completed call history | [List All Calls](https://docs.finosu.com/api-reference/endpoint/calls/list.md): use filters and cursor pagination to retrieve company-wide results. |

## How it works

Your system sends requests to `https://api.finosu.com` over HTTPS using an
API key in the `X-API-Key` header. The key identifies your company; keep it on
your server and out of browser applications and source control.

Finosu processes submitted records using the workflows configured for your
company. Origination enrollment creates or reuses the customer and saves the
application's calling cadence. Collections boarding follows a separate
customer-and-loan flow. Confirm the enabled workflows with your Finosu contact
before submitting records.

A saved schedule means outreach has been scheduled. Inspect its status and
retrieve call results to follow what happens next. Call-result webhooks require
separate configuration; agree on the destination and payload with your Finosu
contact before building a receiver. Outbound callback names in the API reference
identify delivery contracts, not endpoints to call on `api.finosu.com`.

## Integration options

These guides describe integrations where your system sends records to the Finosu
API. If your integration requires Finosu to retrieve records from your system,
coordinate the data contract, authentication, and connection setup with your
Finosu contact.

Use [API Basics](https://docs.finosu.com/api-reference/introduction.md) for authentication and the base URL,
or go directly to the [Quickstart](https://docs.finosu.com/concepts.md) to make your first request.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.