Skip to main content
The Marketplace API is in a private beta. It answers only for accounts Investorlift has enabled. 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 serves each party its own data and the match Mogul makes for it. It serves nobody the live inventory as a feed, the buyer network, or the private figures of another party. This page is the developer’s statement of that boundary, and the Terms bind it. Every schema is an allowlist: a field appears because the contract names it, never because a table holds it.

​
What a seller reads

  • Own drafts and deals, every field, the private figures included. purchase_price, repair_estimate_min and repair_estimate_max are fields of the sell side only, and they reach no buyer.
  • The offers, inquiries, address requests and leads on own deals, each with the buyer’s name, entity_name and buyer_id.
  • The buyer’s email, phone and phone_type on those rows and on their events, under contacts:read. That scope belongs to an owner or an admin, and the daily contact-bearing row cap bounds it (Trust and limits).
  • One engaged buyer at GET /sell/buyers/{buyer_id}: the trust tier, the verification facts, and the organization’s own deals the buyer acted on. The read also carries the strike the organization filed, or null. Only a buyer with a lead, an offer, an inquiry or an address request on one of the organization’s deals answers. Any other id is 404 not_found.
  • Own reviews, with the response, the reviewer anonymous.

​
What a buyer reads

  • The deals Mogul shows this buyer, under the same visibility rule, 25 a page, inside the daily deal budget of the tier. A buyer with no attached or verified legal entity reads the first 50 deals only.
  • One deal: the public fields, the media, verification.status, the seller stub and the address block. The read also carries the buyer’s own offers and requests on the deal.
  • The address block of that deal. address.status reads hidden, requested, approved or declined, and the street stays absent until it reads approved. address.agreement carries the id, the url and the accepted flag of the Non-Circumvention Agreement.
  • Own offers as a list, and one offer with its chain. Own inquiries, each address request with its address_state: requested, approved or declined. An approved request carries the address.
  • One seller profile at a time: the company name, the handle, the member-since date, deals_sold as a band, and the rating summary Mogul shows. On a deal read, seller.phone is the Investorlift tracking number of the deal manager, or null. Investorlift owns that number and rotates it.
  • One seller’s reviews at a time, the reviewer anonymous. Each review carries the rating, the text, the month, verified_transaction, the seller’s response, and the city and state of the deal.
  • Own buy boxes and own proof of funds.

​
What the API never returns, at any scope

  • Another buyer’s offers, the count of offers on a deal, or the high offer on a deal.
  • The contract price or the spread of a deal you do not own. No buyer-side schema carries a purchase price or an assignment fee.
  • A buyer who did not act on your own deal. No endpoint lists buyers.
  • The score, the rank, the breakdown, the channels or the God Mode provenance of a recommended lead.
  • The seller’s own phone and email. The one phone on the buy side is the tracking number.
  • A cross-seller review table or ranking, or the identity of a reviewer.
  • Any God Mode field. The two APIs share the gateway, this site and the shape of a problem body, and nothing else. God Mode’s GET /v1/deals serves deed-recorded transactions, and a marketplace deal is a listing on Mogul.
  • The live inventory as a feed. The deal budget of the tier caps the deal rows a day. At any tier, one account reads at most one fifth of the live inventory in a day.
Mogul suggests buyers for a deal and shows them to the seller in the app before the person acts. The API is stricter. A lead Mogul suggested comes back as origin: "recommended" with buyer: null. The buyer block appears once the person acts on the deal: an inquiry, an offer, an address request, or an interaction Mogul records. It also appears once you move the lead out of new in the app. lead.created fires at that first act, not at the suggestion. The history of such a lead never shows a cause from the recommendation engine.

​
The cache rule

Keep a deal read for 24 hours, then read it again. Keep no copy of deals, offers, leads or reviews outside the systems of the connected organization. Show attribution to Investorlift where you show a deal outside Mogul. Use the contact a lead carries for that deal only. On a buyer.redacted event, delete the buyer’s contact within 10 business days and keep the id as a tombstone. The Terms state each rule in full, with the notice Investorlift gives before it removes a route, a field or an event type. Authentication has the scopes. Webhooks and events has what an event carries about a buyer.