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 figures on this page are the beta’s. Investorlift measures what honest sellers and buyers do during the beta, and a
figure can move before the beta ends.
GET /me prints the caps that apply to your token today.403 forbidden on its next
request. A cap you reach is not a reason for a stop.
The four tiers
The tiers are cumulative. A tier holds only when every tier under it holds, so an accepted offer never lifts an account with no verified phone.
Full search access is a separate fact. A buyer with no attached or verified legal entity reads the first 50 deals only,
the same preview Mogul shows.
GET /me names the step in trust.next_step, and prints each fact with its source in
trust.facts.
The caps per tier
The deal budget counts the deals the token gets, and one deal counts once a day. A list row counts the deal. So does a
single read, a preview, and a
deal.matched delivery on a webhook or the feed. Active chains is a live count of the
offer chains open at one time, not a daily count. Sellers a day counts GET /buy/sellers/{seller_id}. When Mogul’s identity gate for offers is on, a
T1 offer answers 403 idv_required, and verification_url carries the verification link.
The seller caps
A contact-bearing row carries
email or phone under contacts:read. A contact-bearing list reaches back to the
later of your connection date and 90 days. Rows with an active offer, or with an inquiry inside 30 days, are the
exception.
Per-deal ceilings
Whoever writes, one deal takes 20 offers an hour, and 40 inquiries and address requests an hour together. Above a ceiling, a buyer’s new offer, counter, inquiry or address request goes to the hold queue, and Investorlift tells the seller. An offer the seller logs above the ceiling answers429 cap_reached with Retry-After: 3600.
Cold start and linked accounts
An account or a client under 14 days old, or under 20 writes, is new. The API samples its first five writes into the hold queue and scores it against the population of its tier. For the caps, the API counts accounts as one actor when, in one day, they share one of these:- a phone hash
- a Plaid identity
- a payment instrument
- a device
- an egress address
T0 for API writes.
The hold queue
A held write is not a refusal. Four operations can answer202 for a held write:
POST /buy/offersPOST /buy/offers/{offer_id}/counterPOST /sell/offers/{offer_id}/counterPOST /buy/deals/{deal_id}/inquiries
202 with data: { status: "held", kind, hold_id, held_at }. kind
names the held write: offer, inquiry or address_request. The schema also lists deal, and no deal operation
answers 202 today. hold_id is the id of the hold, with the prefix hld_. held_at is the instant the queue took
the write.
The write then waits for a person at Investorlift. Staff release or refuse it within one business day. The
counterparty does not see the write until staff release it.
Both sides get offer.held and inquiry.held on the events feed and on a webhook, and the event carries the same
hold_id. The writer of the held write gets the event. The seller of the deal gets it when a per-deal ceiling holds
the write, and that event names no buyer and no terms.
Four things send a write to the queue: a per-deal ceiling, a cold start, an anomaly, and strikes. An anomaly is a burst
of 5 times your own baseline over the trailing 14 days. The baseline tracks deal rows served, write rate, decline rate,
distinct deals touched and contact fields served. Investorlift emails the account when it occurs.
Strikes
A seller files a strike against a buyer who acted on one of its deals in the last 90 days, atPOST /sell/buyers/{buyer_id}/strikes. One organization files one strike per buyer. One strike changes no cap: it marks
the buyer for Investorlift staff. The strike carries an id with the prefix stk_. A second strike against the same
buyer answers 409 strike_exists. A strike after the 90 days answers 409 strike_window_closed.
Two strikes inside 30 days from unrelated organizations drop the buyer one tier for 7
days. Three route every new write of the buyer to the hold queue. A ban needs staff. A strike from an organization
Investorlift later suspends is void, and the tier comes back. GET /me shows the two rules as the facts
strike_tier_drop and strike_hold in trust.facts.
What a seller controls
Read and change the controls atGET and PATCH /sell/settings under the scope deals:write. The API applies each
control at the offer preview and at the submit. Under refuse, the API never stores a refused offer. Under
auto_decline, the API stores the offer and declines it at once, and it appears in your offers with decline_reason.
A setting the body omits keeps what it holds.
The gateway limits
Beside the caps, the gateway atapi.investorlift.com limits requests. A person gets 60 requests a minute and 5,000 a
day. A registered app gets 600 a minute and 50,000 a day across its users. Every request counts, refused or served.
Past a limit, the gateway answers 429 rate_limited with Retry-After. A published figure you reach is not abuse.
The 429 bodies and GET /me
GET /me prints trust.tier, trust.facts, trust.next_step and one caps row per action with limit, used,
remaining and resets_at. The buy-side actions are deal_read, preview, offer, inquiry, address_request and
seller_read. The sell-side actions are draft and contact_row. Read it before a batch, and read it again after a
429. Errors has the recovery sentences.