> For the complete documentation index, see [llms.txt](https://developers.gallantreecapital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.gallantreecapital.com/getting-started/overview.md).

# Overview

The Gallantree Developer API lets you build against loan management data — capital programs, products, loans, organisations, and individuals — programmatically. This is the same platform commercial lenders use to originate and service loans, exposed through a versioned REST surface.

## What you can do today

* **Read** loans, organisations, individuals, capital programs, products, collaterals, and base rates.
* **Write** loans, organisations, and individuals — either via a full create-through-API flow or the handover ingestion endpoint used by API-native integrations.
* **Upload** documents against loans and applications.
* **Subscribe** to webhooks and receive signed event notifications when data changes.
* **Rotate** credentials with an overlap window so you never have to take an integration offline.

The full surface is enumerated in the [API reference](/reference/openapi.md).

## What's on the way

Tier 2 endpoints (investments, treasury, portfolio analytics, fees, accounting), SDK libraries (TypeScript, Python), and enterprise security options (mTLS, IP allowlisting on production keys) are scheduled for the next release.

## How the API is organised

```
https://developers.gallantreecapital.com/api/v1/<resource>
```

* **`v1`** — the current API version. The URL is the version boundary; there is no header-based versioning. See [API versioning](/guides/versioning.md).
* **`<resource>`** — a plural noun (`loans`, `organisations`, `individuals`, …). Reads use `GET`, writes use `POST`/`PUT`/`DELETE`.
* **Authentication** — every request carries an `x-api-key` header issued to your developer app. See [Authentication with API keys](/guides/authentication.md).
* **Scopes** — your app declares which data it needs; the API enforces the intersection.

The base URL for all examples in these docs is `https://developers.gallantreecapital.com`. If your integration needs to hit a specific environment directly, see [Environments](/getting-started/environments.md).

## Where to go next

* Want to make your first call? Follow the four-step [quickstart](/getting-started/first-request.md).
* Building a webhook integration? Start with [Subscribe to events](/webhooks/subscribe.md).
* Need the OpenAPI spec? It's rendered on the [API reference](/reference/openapi.md) page and downloadable as YAML.

## A note on style

Every guide in these docs ends with a runnable example. Copy, paste, replace the placeholder credentials, and it should work against the sandbox environment. If a snippet doesn't work as documented, the bug is in the docs — [tell us](https://github.com/Token-Gesture/lms/issues/new) so we can fix it.


---

# 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://developers.gallantreecapital.com/getting-started/overview.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.