> ## 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.

# Direct model

> For regulated entities that hold their own permissions and run their own ledger. You trade as your organisation and attach a customer object to each trade.

<Note>
  This is one of two ways to integrate the Investments API. If you do not hold your own regulatory permissions, use the [Managed model](/docs/api-reference/investments/managed) instead.
</Note>

## Who this is for

You are a regulated entity — a broker, an asset manager, a licensed fintech — and you already hold the permissions to hold client assets and maintain a ledger of your end users.

In the Direct model you are GetEquity's counterparty. Your organisation has a single account and a single wallet, and every order is placed as your organisation. GetEquity does not provision accounts for your end users and does not hold a per-user balance for them.

## How your end users are represented

Each trade carries a `customer` object naming the end user the activity belongs to:

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

GetEquity stores this attribution against the order and the resulting transaction. The email address is the identity key: reuse the same address across trades and they accumulate against one customer record.

Those records are what the [Customers](/docs/api-reference/endpoint/Customers/customers) endpoints return. A customer appears there once they have traded — there is no separate call to create one.

<Warning>
  A `customer` is an attribution record, not an account. It has no credentials, no wallet and no balance of its own. Holding the position for each end user, and reconciling it against your organisation's aggregate position on GetEquity, is your responsibility as the regulated party.
</Warning>

## The flow

<Steps>
  <Step title="Fund your organisation wallet">
    Call [Fund Wallet](/docs/api-reference/endpoint/Wallet/fund-wallet) to get a virtual account or payment link. All trades settle against this single wallet.
  </Step>

  <Step title="Find something to trade">
    Use [Get All Tokens](/docs/api-reference/endpoint/Trade/get-tokens), [Get Raising Tokens](/docs/api-reference/endpoint/Trade/get-raising-tokens) or [Search Token](/docs/api-reference/endpoint/Trade/search-token) to locate the asset.
  </Step>

  <Step title="Place the order">
    Call [Buy Token](/docs/api-reference/endpoint/Trade/buy-token) or [Sell Token](/docs/api-reference/endpoint/Trade/sell-token) with the `customer` object attached. For a raise rather than a secondary trade, use [Fund Buy](/docs/api-reference/endpoint/Trade/fund-buy).
  </Step>

  <Step title="Track it">
    Orders return immediately as pending. Watch the `order.created` and `transaction.created` [webhook events](/docs/api-reference/endpoint/Webhook/webhook), or poll [Get Order](/docs/api-reference/endpoint/Orders/get-order).
  </Step>

  <Step title="Reconcile">
    Use [Get Customer Transactions](/docs/api-reference/endpoint/Transactions/get-customer-transactions) to pull activity for one end user by email, and [Get Wallet Balance](/docs/api-reference/endpoint/Wallet/get-wallet-balance) for your organisation's position.
  </Step>
</Steps>

## Endpoints in this model

<CardGroup cols={2}>
  <Card title="Trade" icon="arrow-right-arrow-left" href="/docs/api-reference/endpoint/Trade/trade">
    Buy, sell and fund-buy tokens, plus token discovery and market data.
  </Card>

  <Card title="Customers" icon="address-book" href="/docs/api-reference/endpoint/Customers/customers">
    List and search the end users you have traded on behalf of.
  </Card>

  <Card title="Orders" icon="list-check" href="/docs/api-reference/endpoint/Orders/orders">
    Retrieve and cancel orders your organisation has placed.
  </Card>

  <Card title="Transactions" icon="receipt" href="/docs/api-reference/endpoint/Transactions/transactions">
    Per-customer transaction history and total volume.
  </Card>

  <Card title="Wallet" icon="wallet" href="/docs/api-reference/endpoint/Wallet/wallet">
    Fund, withdraw from and check the balance of your organisation wallet.
  </Card>

  <Card title="Webhooks" icon="bell" href="/docs/api-reference/endpoint/Webhook/webhook">
    Order, transaction and wallet events for your organisation.
  </Card>
</CardGroup>

## Authentication

Every request uses your organisation's secret key. There are no per-user tokens in this model.

```http theme={null}
Authorization: "Bearer YOUR_SECRET_KEY"
```