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

# Managed model

> For non-regulated entities acting as an intermediary between their users and GetEquity. Each of your users gets a real GetEquity account — a member — that you act on behalf of.

<Note>
  This is one of two ways to integrate the Investments API. If you hold your own regulatory permissions and want to run your own ledger, use the [Direct model](/docs/api-reference/investments/direct) instead.
</Note>

## Who this is for

You are not a regulated entity, so you cannot hold client assets on your own book. Instead you act as an intermediary: your app is the interface, and GetEquity holds the account and the assets for each of your users.

Every user you onboard becomes a **member** of your organisation's syndicate — a real GetEquity account with its own credentials, wallet, balances, orders and transaction history. You act on their behalf through the `api/members/{id}/*` routes using your organisation's secret key.

## How your end users are represented

You provision a member with [Create Member](/docs/api-reference/endpoint/Members/create-member). Unlike a Direct-model `customer`, this creates an account:

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

The response returns the member's `id` — which every subsequent call is scoped to — along with their KYC and verification state. Because a member is a full account, GetEquity is the ledger of record for their holdings, and their funds sit in their own wallet rather than a pooled organisation wallet.

<Tip>
  Members are created with credentials, so the same account can be reached both through your integration and directly on GetEquity. Retrieve an existing one with [Get Member by Email](/docs/api-reference/endpoint/Members/get-member-by-email) rather than creating a duplicate.
</Tip>

## The flow

<Steps>
  <Step title="Create the member">
    [Create Member](/docs/api-reference/endpoint/Members/create-member) returns the `id` used by every later call. Listen for the `member.created` webhook to confirm provisioning.
  </Step>

  <Step title="Fund their wallet">
    [Fund Member Wallet](/docs/api-reference/endpoint/Members/fund-members-wallet) generates a funding link or virtual account per currency. Funds land in the member's own wallet, not yours.
  </Step>

  <Step title="Find something to trade">
    Token discovery is shared with the Direct model — 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).
  </Step>

  <Step title="Invest on their behalf">
    Use [Buy Token](/docs/api-reference/endpoint/Members/buy-token) and [Sell Token](/docs/api-reference/endpoint/Members/sell-token) for secondary trades, or [Fund Invest](/docs/api-reference/endpoint/Members/fund-invest) for a live raise. Quote it first with [Fund Invest Quote](/docs/api-reference/endpoint/Members/fund-invest-quote).
  </Step>

  <Step title="Report back to them">
    [Member Token Balance](/docs/api-reference/endpoint/Members/member-token-balance), [Member Currency Balance](/docs/api-reference/endpoint/Members/member-currency-balance), [Member Orders](/docs/api-reference/endpoint/Members/member-orders) and [Member Transactions](/docs/api-reference/endpoint/Members/member-transactions) give you everything you need to render their portfolio.
  </Step>

  <Step title="Pay them out">
    [Withdraw from Member Wallet](/docs/api-reference/endpoint/Members/withdraw-member-wallet) debits their currency wallet to a bank account. Watch the `withdrawal.created` and `withdrawal.approved` webhooks.
  </Step>
</Steps>

## Endpoints in this model

<CardGroup cols={2}>
  <Card title="Members" icon="users" href="/docs/api-reference/endpoint/Members/members">
    The full set — provisioning, funding, trading, balances, orders, transactions and withdrawals.
  </Card>

  <Card title="Market data" icon="chart-line" href="/docs/api-reference/endpoint/Trade/get-tokens">
    Token listings, prices, historicals and search. Read-only and shared with the Direct model.
  </Card>

  <Card title="Webhooks" icon="bell" href="/docs/api-reference/endpoint/Webhook/webhook">
    `member.created`, order, transaction and withdrawal events for your syndicate.
  </Card>

  <Card title="Compare with Direct" icon="scale-balanced" href="/docs/api-reference/choosing-your-integration">
    Side-by-side comparison of the two models.
  </Card>
</CardGroup>

## Authentication

Members hold credentials of their own, but your integration does not use them. Every call you make is authenticated with your organisation's secret key, and the member is identified by the `id` in the path.

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

<Warning>
  Your secret key can act on behalf of every member in your syndicate. Keep it server-side — never ship it to a browser or mobile client.
</Warning>