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

# Choosing your integration

> GetEquity exposes three API products. Which one you build against depends on whether you hold your own regulatory permissions, and whether you are distributing investments or issuing credit.

Before writing any code, decide which product you are integrating. The three products use different endpoints, model your end users differently, and place the ledger of record in different places.

<CardGroup cols={3}>
  <Card title="Investments API · Direct" icon="building-columns" href="/docs/api-reference/investments/direct">
    You are regulated. You keep your own ledger and attach a `customer` object to each trade.
  </Card>

  <Card title="Investments API · Managed" icon="users" href="/docs/api-reference/investments/managed">
    You are not regulated. GetEquity holds an account for each of your users as a member.
  </Card>

  <Card title="Credit API" icon="hand-holding-dollar" href="/docs/api-reference/endpoint/CreditLoan/credit-loan">
    You are a credit provider lending against portfolios held on GetEquity.
  </Card>
</CardGroup>

## At a glance

|                                            | Direct                            | Managed                                      | Credit                                     |
| :----------------------------------------- | :-------------------------------- | :------------------------------------------- | :----------------------------------------- |
| **You are**                                | A regulated entity                | An intermediary without your own permissions | A credit provider                          |
| **Ledger of record for the end user**      | You                               | GetEquity                                    | You (the loan); GetEquity (the collateral) |
| **Who GetEquity sees as the counterparty** | Your organisation                 | The individual member                        | Your organisation as creditor              |
| **End user has GetEquity credentials**     | No                                | Yes                                          | No                                         |
| **End user representation**                | A `customer` object on each trade | A member account with its own wallet         | An existing GetEquity user you lend to     |
| **Primary routes**                         | `api/token/*`, `api/customers/*`  | `api/member`, `api/members/{id}/*`           | `api/credit/*`, `api/creditor/*`           |
| **Funds settle into**                      | Your organisation wallet          | The member's own wallet                      | —                                          |

## Direct — for regulated entities

If your company already holds the permissions to hold client assets and run a ledger, you integrate as the principal. You have one organisation account and one wallet, and you trade as yourself.

Every trade carries a `customer` object identifying which of your end users the activity belongs to. GetEquity records that attribution and surfaces it back through the [Customers](/docs/api-reference/endpoint/Customers/customers) endpoints, but it never provisions an account for that person — reconciling positions to your individual users remains your responsibility.

```json POST api/token/{id}/buy theme={null}
{
  "amount": 20,
  "price": 10,
  "currency": "USD",
  "customer": {
    "name": "Rema Divine",
    "email": "rema@example.com"
  }
}
```

<Card title="Read the Direct integration guide" icon="arrow-right" href="/docs/api-reference/investments/direct" horizontal />

## Managed — for non-regulated entities

If you do not hold those permissions, you act as an intermediary between your users and GetEquity. GetEquity provisions a real account — a **member** — for each of your users, sitting inside your organisation's syndicate.

A member has their own credentials, their own wallet, their own balances, orders and transactions. You create them with [Create Member](/docs/api-reference/endpoint/Members/create-member) and then act on their behalf through the `api/members/{id}/*` routes.

```json POST api/member theme={null}
{
  "email": "willmember@example.com",
  "password": "William01",
  "fname": "William",
  "lname": "Ajasco",
  "username": "willmember",
  "phone": "08026662262"
}
```

<Card title="Read the Managed integration guide" icon="arrow-right" href="/docs/api-reference/investments/managed" horizontal />

## Credit — for credit providers

The Credit API is a separate product. Rather than distributing investments, you lend against them: a GetEquity user pledges their existing portfolio as collateral, and you issue and service the loan against it.

<Card title="Read the Credit API guide" icon="arrow-right" href="/docs/api-reference/endpoint/CreditLoan/credit-loan" horizontal />

## Shared across all three

<CardGroup cols={2}>
  <Card title="Authentication" icon="key" href="/docs/api-reference/introduction">
    Every product uses the same `Bearer` secret key issued to your organisation.
  </Card>

  <Card title="Market data" icon="chart-line" href="/docs/api-reference/endpoint/Trade/get-tokens">
    Token listings, prices, historicals and search are read-only and identical in every model.
  </Card>

  <Card title="Webhooks" icon="bell" href="/docs/api-reference/endpoint/Webhook/webhook">
    One webhook URL per organisation receives events for whichever products you use.
  </Card>

  <Card title="Sandbox" icon="flask" href="/docs/api-reference/introduction">
    All three products are available on the staging base URL before you go live.
  </Card>
</CardGroup>

<Note>
  Direct and Managed are not mixed within one integration. Pick the one that matches your regulatory position — if you are unsure which applies to you, contact [support](mailto:support@getequity.io) before you build.
</Note>