> ## Documentation Index > Fetch the complete documentation index at: https://developers.investorlift.com/llms.txt > Use this file to discover all available pages before exploring further. # The Marketplace API > A read and write API for the Investorlift marketplace, Mogul: sellers publish and manage deals, buyers search and make offers, with an OAuth token. The Marketplace API is in a private beta. It answers only for accounts Investorlift has enabled. [Access](/marketplace/access) says how to ask for one. A route shape on these pages can change before the beta ends. The changelog records every change. The Marketplace API is a read and write API for the Investorlift marketplace, Mogul. It answers at `https://api.investorlift.com/marketplace/v1`. A seller creates and publishes deals from a CRM and gets every buyer action back. A buyer searches the deals Mogul shows them and makes offers from their own tools. The token is an OAuth token for your Investorlift account, and no call costs a God Mode credit. A publish spends the organization's Mogul credits, as it does in the app. ## Two sides and one profile Every route lives under one side. | Route | Acts for | What it does | | -------------------------- | ----------------- | ----------------------------------------------------------------------------------------------------------- | | `/marketplace/v1/sell/...` | Your organization | Drafts, media, documents, publish, status, offers, inquiries, leads, reviews, settings, webhooks and events | | `/marketplace/v1/buy/...` | You as a buyer | Search, deal reads, offers, inquiries, address requests, buy boxes, proof of funds, webhooks and events | | `GET /marketplace/v1/me` | Both | What this token can do now | The token names a person. On every request the API loads that person's organization, role and designations. A `/sell/` route needs an organization with the `seller` designation. A `/buy/` route needs the `buyer` designation. One account with both designations uses both sides with one token. `GET /me` answers the sides the token reaches, the trust tier, the remainder of each cap today and the terms each side accepted. Call it first. ## Who it is for | Person | What you build | | ------------------------------------------- | ---------------------------------------------------------------------------------------------- | | A wholesaler's dispositions team | A deal created from your CRM and published, and every buyer action in your CRM within a minute | | An operator with several teams | Deal status written from your system of record, with one connection per team | | An acquisitions team with a model | A search of the deals you see, an offer from your own workflow, and the counters tracked | | An individual investor with an AI assistant | An offer or an inquiry through the assistant, with a confirmation step before every offer | | Any buyer | A seller's profile and reviews beside the deal, before an offer | | A CRM vendor | One OAuth connection per customer, a typed event catalogue and a replay path | ## What sellers get * The deal lifecycle the app has. You create a draft, add photos and the acquisition contract, publish, and move the deal through the app's own status rules. * The same paid path as the app. A publish spends the organization's Mogul credits, and the API charges no card. * A log of an offer you took off the platform. * Every offer, inquiry, address request and lead on your deals, two ways: signed webhooks, and an ordered events feed for replay. * Your own offers, with accept, decline and counter. * The buyer's email and phone on your own leads, with `contacts:read` and the owner or admin role. ## What buyers get * The deals you already see on Mogul, under the same visibility rules and the same address gate, 25 to a page. * The actions that move a deal: an offer, a counter, an inquiry, an address request. * A two-step offer. The preview shows the deal's terms and your standing and writes nothing. The submit sends the preview's token back, and the API runs every check again. * A seller's public profile and reviews, one seller at a time. * Your buy boxes and your proof of funds. ## What it never returns, at any scope * The recommendation lists, the shared and rented buyers, and any buyer who has not acted on your own deal. * The contract price and the spread of a deal, to anyone but its seller. * Another buyer's offers, the count of offers on a deal, or the high offer. * A cross-seller review table or ranking, and the identity of a reviewer. * The seller's own phone and email in a buyer-side read. The seller stub carries the Investorlift tracking number, or null. * The live inventory as a bulk feed. A daily deal budget counts every deal row a buyer token gets. * Any God Mode field. ## How it differs from the God Mode API | | God Mode API | Marketplace API | | -------------- | ----------------------------------------------- | -------------------------------------------------------------------------------------- | | Base URL | `https://api.investorlift.com/v1` | `https://api.investorlift.com/marketplace/v1` | | What a deal is | A deed-recorded transaction from public records | A live deal on the Investorlift marketplace, Mogul | | Writes | None. Every route reads | Drafts, publish, status, offers, inquiries, leads, webhooks | | Credential | A `zpka_` key from the developer console | An OAuth token for your Investorlift account | | Price | Credits per deal, investor or parcel | No credits. Included in the Mogul plan for sellers, free for verified buyers | | Who acts | Your key | A person, with the organization, the role and the designations loaded on every request | The God Mode `/v1/deals` route keeps its name and serves deed records. The Marketplace API takes no `zpka_` key. The two APIs share the gateway, this site and the shape of a problem body, and nothing else. ## The private beta The API answers only for accounts Investorlift has enabled. [Access](/marketplace/access) says how to ask, what a personal client and a registered application get, and what the beta costs. Investorlift plans a sandbox, and none is available yet, so every call in the beta reaches production data for the signed-in account. The route shapes on these pages come from the OpenAPI document of the origin, and the reference renders that document. A shape can change before the beta ends. The [changelog](/changelog) records every change. ## Where to go next Who can ask, the one email that gets an account enabled, and what a personal client and a registered application get. Create a draft, add a photo and the contract, publish, register a webhook and read the events feed. Search the deals you see, read one, preview an offer, submit it and follow the counter. The OAuth flow at the Investorlift issuer, the scopes, the roles and the token lifetime. The Marketplace API Terms you accept on the consent page. ## Related topics - [Marketplace API Terms](/marketplace/terms.md) - [What the API returns](/marketplace/concepts/what-the-api-returns.md) - [Authentication](/marketplace/authentication.md) - [Errors](/marketplace/concepts/errors.md) - [Identifiers and the envelope](/marketplace/concepts/identifiers-and-envelope.md)