@model-match/api 3.36.0 → 3.37.0

package/dist/{src-CyZ7CTVN.mjs → src-Drg2qi1O.mjs}

@@ -29,6 +29,99 @@ var AdminNmls = class {
 		});
 	}
 };
+var AdminContactSubmissions = class {
+	/**
+	* List contact submissions (admin)
+	* Newest first. Default `status=needs_review`: pre-checked submissions waiting for a decision.
+	*/
+	static adminListContactSubmissions(options) {
+		return (options?.client ?? client).get({
+			security: [{
+				name: "x-api-key",
+				type: "apiKey"
+			}, {
+				scheme: "bearer",
+				type: "http"
+			}],
+			url: "/v1/admin/contact-submissions",
+			...options
+		});
+	}
+	/**
+	* Approved contact values for one person (admin)
+	*/
+	static adminListApprovedContacts(options) {
+		return (options.client ?? client).get({
+			security: [{
+				name: "x-api-key",
+				type: "apiKey"
+			}, {
+				scheme: "bearer",
+				type: "http"
+			}],
+			url: "/v1/admin/contact-submissions/approved",
+			...options
+		});
+	}
+	/**
+	* Revoke an approved contact value (admin)
+	* Already revoked → 200 with the row unchanged.
+	*/
+	static adminRevokeApprovedContact(options) {
+		return (options.client ?? client).post({
+			security: [{
+				name: "x-api-key",
+				type: "apiKey"
+			}, {
+				scheme: "bearer",
+				type: "http"
+			}],
+			url: "/v1/admin/contact-submissions/approved/{id}/revoke",
+			...options,
+			headers: {
+				"Content-Type": "application/json",
+				...options?.headers
+			}
+		});
+	}
+	/**
+	* One contact submission with its subject and approved values (admin)
+	*/
+	static adminGetContactSubmission(options) {
+		return (options.client ?? client).get({
+			security: [{
+				name: "x-api-key",
+				type: "apiKey"
+			}, {
+				scheme: "bearer",
+				type: "http"
+			}],
+			url: "/v1/admin/contact-submissions/{id}",
+			...options
+		});
+	}
+	/**
+	* Approve or reject items of a contact submission (admin)
+	* Approving inserts (or reuses) the live approved value; changing an approval to a rejection revokes the value it created, unless another approval still holds it. Sending a decision already recorded is a no-op. Once every item is decided the submission is `reviewed`.
+	*/
+	static adminReviewContactSubmission(options) {
+		return (options.client ?? client).post({
+			security: [{
+				name: "x-api-key",
+				type: "apiKey"
+			}, {
+				scheme: "bearer",
+				type: "http"
+			}],
+			url: "/v1/admin/contact-submissions/{id}/review",
+			...options,
+			headers: {
+				"Content-Type": "application/json",
+				...options?.headers
+			}
+		});
+	}
+};
 var AdminJobs = class {
 	/**
 	* Get a bulk job and a signed download URL (admin)
@@ -48,6 +141,45 @@ var AdminJobs = class {
 		});
 	}
 };
+var AdminLoEnrichment = class {
+	/**
+	* Enrichment Firecrawl balance (admin)
+	*/
+	static adminGetLoEnrichmentBalance(options) {
+		return (options?.client ?? client).get({
+			security: [{
+				name: "x-api-key",
+				type: "apiKey"
+			}, {
+				scheme: "bearer",
+				type: "http"
+			}],
+			url: "/v1/admin/lo-enrichment/balance",
+			...options
+		});
+	}
+	/**
+	* Launch an LO contact enrichment run (admin)
+	* Starts the `lo-enrichment` ECS task. Progress + outcome: the admin Job Runs page (job `lo-enrichment`). The run hard-stops at `creditBudget` and aborts if the enrichment Firecrawl account holds less than it.
+	*/
+	static adminLaunchLoEnrichmentRun(options) {
+		return (options.client ?? client).post({
+			security: [{
+				name: "x-api-key",
+				type: "apiKey"
+			}, {
+				scheme: "bearer",
+				type: "http"
+			}],
+			url: "/v1/admin/lo-enrichment/runs",
+			...options,
+			headers: {
+				"Content-Type": "application/json",
+				...options?.headers
+			}
+		});
+	}
+};
 var Agents = class {
 	/**
 	* Search agents with filters
@@ -195,6 +327,27 @@ var Agents = class {
 		});
 	}
 	/**
+	* Submit contact details for a real estate agent
+	* Send contact details you know for a real estate agent — a phone number, an email address, a profile link, or the company they moved to. The submission is checked and reviewed before anything appears on the profile; this call only records it and answers immediately. Sending the same details for the same person again while the first submission is still being reviewed returns the first submission's `id`.
+	*/
+	static createAgentContactSubmission(options) {
+		return (options?.client ?? client).post({
+			security: [{
+				name: "x-api-key",
+				type: "apiKey"
+			}, {
+				scheme: "bearer",
+				type: "http"
+			}],
+			url: "/v1/agents/contact-submissions",
+			...options,
+			headers: {
+				"Content-Type": "application/json",
+				...options?.headers
+			}
+		});
+	}
+	/**
 	* Count agents matching filters
 	* Return the exact number of agents matching the given filters. Accepts the same request body as `listAgents` (pagination and sort are ignored). Use this when you only need a total; to get the matching agents themselves, send the same request body to `listAgents`.
 	*/
@@ -357,7 +510,8 @@ var Agents = class {
 		});
 	}
 	/**
-	* Raw-name lenders encountered (pre-aggregated)
+	* Lenders on the agent's deals (pre-aggregated)
+	* Lenders that financed the agent's deals in the period. Each row's `id` is the lender id — pass it back as the `lender` filter on the loans routes to drill into that lender's loans — and `label` its display name. The row for deals with no lender attributed carries no `id`.
 	*/
 	static lenders(options) {
 		return (options.client ?? client).post({
@@ -377,8 +531,8 @@ var Agents = class {
 		});
 	}
 	/**
-	* Listing offices the agent has closed through
-	* Ranks the agent's CLOSED sales (MLS status sold, a real sale price — rentals and lease listings excluded, duplicate MLS records of one sale counted once) by this dimension. The same population `POST /v1/agents/{id}/sales` returns with `flatFilters.mlsStatus: "SLD"` and the agent analytics routes count. `side` narrows to the deals the agent was on that side of (`buyer` includes deals on both sides; `buyer` + `listing` = `any`).
+	* Offices the agent closed deals through (their side of each sale)
+	* Ranks the agent's CLOSED sales (MLS status sold, a real sale price — rentals and lease listings excluded, duplicate MLS records of one sale counted once) by this dimension. The same population `POST /v1/agents/{id}/sales` returns with `flatFilters.mlsStatus: "SLD"` and the agent analytics routes count. `side` narrows to the deals the agent was on that side of (`buyer` includes deals on both sides; `buyer` + `listing` = `any`). Each sale is credited to the office recorded for the agent's OWN side of it (the listing office when the agent listed it, including dual deals; the buyer's office when the agent only represented the buyer), so every sale counts at most once. A sale with no office recorded on the agent's side lands in no row, so rows can sum to less than `totals`. Office names are as recorded and not normalized: one brokerage can appear under several spellings.
 	*/
 	static offices(options) {
 		return (options.client ?? client).post({
@@ -2898,6 +3052,27 @@ var Crm = class {
 		});
 	}
 	/**
+	* Apply accepted Market-Insights updates to several list records
+	* Bulk form of `applyCrmMiUpdates` for records in one CRM list: for each record, persist ONLY the updates listed for it (copy them from `getCrmListMiUpdates` — `store`, `field` or `kind`, and the `incoming` value as `value`). Never send updates the user did not accept. Proposals on a record that were not accepted count as reviewed. Records not in the list are reported, not applied.
+	*/
+	static applyCrmListMiUpdates(options) {
+		return (options.client ?? client).post({
+			security: [{
+				name: "x-api-key",
+				type: "apiKey"
+			}, {
+				scheme: "bearer",
+				type: "http"
+			}],
+			url: "/v1/crm/lists/{id}/apply-mi-updates",
+			...options,
+			headers: {
+				"Content-Type": "application/json",
+				...options?.headers
+			}
+		});
+	}
+	/**
 	* List who can be assigned on a list (access-filtered by visibility)
 	*/
 	static listCrmListAssignees(options) {
@@ -2914,6 +3089,27 @@ var Crm = class {
 		});
 	}
 	/**
+	* Snooze Market-Insights updates on several list records
+	* Bulk form of `dismissCrmMiUpdates` for records in one CRM list: marks the updates last shown for each record as reviewed for the 31-day check window, so `getCrmListMiUpdates` stops returning them. Nothing is written to the records. A proposal that was not shown yet (new Market-Insights data) still comes back.
+	*/
+	static dismissCrmListMiUpdates(options) {
+		return (options.client ?? client).post({
+			security: [{
+				name: "x-api-key",
+				type: "apiKey"
+			}, {
+				scheme: "bearer",
+				type: "http"
+			}],
+			url: "/v1/crm/lists/{id}/dismiss-mi-updates",
+			...options,
+			headers: {
+				"Content-Type": "application/json",
+				...options?.headers
+			}
+		});
+	}
+	/**
 	* Filter a list's members by entity attributes (read)
 	*/
 	static filterCrmListMembers(options) {
@@ -3010,6 +3206,27 @@ var Crm = class {
 		});
 	}
 	/**
+	* Find the records in a CRM list that have Market-Insights updates to review
+	* Checks a CRM list's members against current Market-Insights data and returns ONLY the records that need attention, each with its proposed updates. Use this instead of calling `getCrmRecordProfile` + `getCrmMiUpdates` for every member: one call covers a page of up to 50 members, and records the user already reviewed (applied or dismissed) with nothing new since are left out. Page with `cursor` until `nextCursor` is null; a page may return no records and still have more to scan. Act on the results with `applyCrmListMiUpdates` (explicit per-record accepted updates) and `dismissCrmListMiUpdates` (snooze the rest). Each scan counts as a check of those records, exactly like `getCrmMiUpdates`.
+	*/
+	static getCrmListMiUpdates(options) {
+		return (options.client ?? client).post({
+			security: [{
+				name: "x-api-key",
+				type: "apiKey"
+			}, {
+				scheme: "bearer",
+				type: "http"
+			}],
+			url: "/v1/crm/lists/{id}/mi-updates",
+			...options,
+			headers: {
+				"Content-Type": "application/json",
+				...options?.headers
+			}
+		});
+	}
+	/**
 	* List the org members a list can be shared with (manage-gated)
 	*/
 	static listCrmListShareableMembers(options) {
@@ -4343,7 +4560,7 @@ var Crm = class {
 var Search = class {
 	/**
 	* Instant multi-entity typeahead search
-	* Fast typeahead/autocomplete search across agents, originators, companies, and offices. Returns top matches per entity type. A bare NMLS ID resolves directly to its originator, company, or branch. Use this for quick name lookups, not for filtered searches (use the entity-specific list endpoints for those). If you already have an entity ID, prefer getOriginator / getCompany / getBranch.
+	* Fast typeahead/autocomplete search across agents, originators, companies, and offices. Returns top matches per entity type. A bare NMLS ID resolves directly to its originator, company, or branch — including an originator who is in the NMLS registry with no production record yet (returned with `hasScoredData: false`). Use this for quick name lookups, not for filtered searches (use the entity-specific list endpoints for those). If you already have an entity ID, prefer getOriginator / getCompany / getBranch.
 	*/
 	static instant(options) {
 		return (options?.client ?? client).post({
@@ -5228,7 +5445,7 @@ var Offices = class {
 var Originators = class {
 	/**
 	* Search originators with filters
-	* Search and list individual loan originators (LOs — NMLS-registered mortgage loan officers) with filters — one row per originator. Filter by name, NMLS ID, location (state, city), employer/company, and production metrics (loan volume, units, product mix), with sorting and cursor pagination. LOCATION SEMANTICS: the state/city filters match an originator's PRODUCTION GEOGRAPHY — the markets where they actually originated loans in the selected period — not where their office or employer sits. An LO who lends across several markets matches a filter for ANY of those markets, while the `state`/`city` returned on each row reflect only their PRIMARY (highest-volume) market. So a search for city "Long Beach" can return an LO whose displayed location is a different city/state (e.g. their top market is in Arizona) — they still originated loans in Long Beach, it just isn't their #1 market. To rank originators by their volume within a specific market, sort by volume after filtering, or use the per-originator city/county/state breakdown endpoints. This is the per-originator record search: use it to find specific loan officers or build a filtered LO list. (For a single originator by NMLS ID use the originator detail endpoint.) If you only need how many originators match and not the records themselves, send the same request body to `countOriginators`.
+	* Search and list individual loan originators (LOs — NMLS-registered mortgage loan officers) with filters — one row per originator. Filter by name, NMLS ID, location (state, city), employer/company, and production metrics (loan volume, units, product mix), with sorting and cursor pagination. LOCATION SEMANTICS: the state/city filters match an originator's PRODUCTION GEOGRAPHY — the markets where they actually originated loans in the selected period — not where their office or employer sits. An LO who lends across several markets matches a filter for ANY of those markets, while the `state`/`city` returned on each row reflect only their PRIMARY (highest-volume) market. So a search for city "Long Beach" can return an LO whose displayed location is a different city/state (e.g. their top market is in Arizona) — they still originated loans in Long Beach, it just isn't their #1 market. To rank originators by their volume within a specific market, sort by volume after filtering, or use the per-originator city/county/state breakdown endpoints. NEWLY LICENSED / NO PRODUCTION: an originator who is in the NMLS registry but has no production record is returned only by an identity search — `nmlsId`, `name` or `namePrefix` as the ONLY filter — sent with `producersOnly: false`. Those rows come after the rows that have production, carry `hasScoredData: false`, and have `null` production fields. Under any other filter, or without `producersOnly: false`, they are not returned (use `getOriginator` for one by NMLS id). This is the per-originator record search: use it to find specific loan officers or build a filtered LO list. (For a single originator by NMLS ID use the originator detail endpoint.) If you only need how many originators match and not the records themselves, send the same request body to `countOriginators`.
 	*/
 	static list(options) {
 		return (options?.client ?? client).post({
@@ -5372,6 +5589,27 @@ var Originators = class {
 		});
 	}
 	/**
+	* Submit contact details for a loan officer
+	* Send contact details you know for a loan officer — a phone number, an email address, a profile link, or the company they moved to. The submission is checked and reviewed before anything appears on the profile; this call only records it and answers immediately. Sending the same details for the same person again while the first submission is still being reviewed returns the first submission's `id`.
+	*/
+	static createOriginatorContactSubmission(options) {
+		return (options?.client ?? client).post({
+			security: [{
+				name: "x-api-key",
+				type: "apiKey"
+			}, {
+				scheme: "bearer",
+				type: "http"
+			}],
+			url: "/v1/originators/contact-submissions",
+			...options,
+			headers: {
+				"Content-Type": "application/json",
+				...options?.headers
+			}
+		});
+	}
+	/**
 	* Count originators matching filters
 	* Return the exact number of originators matching the given filters. Accepts the same request body as `listOriginators` (pagination and sort are ignored). Use this when you only need a total; to get the matching originators themselves, send the same request body to `listOriginators`.
 	*/
@@ -5936,6 +6174,27 @@ var Properties = class {
 		});
 	}
 	/**
+	* Resolve a batch of addresses to property ids
+	* Resolve up to 2,000 postal addresses to property ids in one call — e.g. a mailing list before a bulk delivery. Free. Returns one result per input, in order, keyed by your `ref`. `matched` carries the parcel `id` and `mmPropertyId` — pass them to bulk delivery `propertyIds` or the list `flatFilters.id`, then join the rows back on `ref`. Each address is first matched on the normalized number + street + unit + zip key (suffix, directional, punctuation and case insensitive); misses fall back to a ranked search that only accepts a hit with the same house number, the same zip or city, and a near-identical street name. `ambiguous` lists `candidates`: `unit_required` (a building whose units are separate parcels — resend with the unit), `duplicate_parcels` (one address on several parcel records; usually safe to take them all), `multiple_parcels`. `not_found` gives a `reason`: `no_parcel_at_number` (no parcel at that house number in that zip/city), `low_confidence`, or an input problem (`no_house_number`, `no_street`, `no_location`).
+	*/
+	static resolve(options) {
+		return (options?.client ?? client).post({
+			security: [{
+				name: "x-api-key",
+				type: "apiKey"
+			}, {
+				scheme: "bearer",
+				type: "http"
+			}],
+			url: "/v1/properties/resolve",
+			...options,
+			headers: {
+				"Content-Type": "application/json",
+				...options?.headers
+			}
+		});
+	}
+	/**
 	* Free-text property search
 	* Find properties by a single free-text query — a full or partial address, an owner name, or a place. Results are ranked by relevance and tolerate typos, missing components, and reordered street directionals (e.g. "112 5th ave nw" and "112 nw 5th ave" both match). Returns the same property summary rows as the list endpoint. Use this for a search box; use the list endpoint for structured filtering.
 	*/
@@ -6261,4 +6520,4 @@ function createClient$1(config = {}) {
 	};
 }
 //#endregion
-export { Search as C, SavedFilters as S, Originators as _, Agents as a, Related as b, Companies as c, Lenders as d, Loans as f, Offices as g, Me as h, AdminNmls as i, Crm as l, Market as m, createClient$1 as n, Alerts as o, Locations as p, AdminJobs as r, Branches as s, createApiClient as t, Integrations as u, Properties as v, client as w, Sales as x, Realtime as y };
+export { Sales as C, client as E, Related as S, Search as T, Me as _, AdminLoEnrichment as a, Properties as b, Alerts as c, Crm as d, Integrations as f, Market as g, Locations as h, AdminJobs as i, Branches as l, Loans as m, createClient$1 as n, AdminNmls as o, Lenders as p, AdminContactSubmissions as r, Agents as s, createApiClient as t, Companies as u, Offices as v, SavedFilters as w, Realtime as x, Originators as y };