property-turnover

Scope a property turnover (rendered as html)

Same body as the operation. Runs it, then renders the result as text/html; charset=utf-8. The artifact itself is not stored. Rate limited more tightly than the JSON endpoint.

post/v1/property-turnover/scope/render/html

Request

  • Base URL: https://tektolo.com (the document declares no server; this is the origin it was published from)
  • URL: https://tektolo.com/v1/property-turnover/scope/render/html
  • Auth: none declared

Headers

Tektolo-Rulesetstring nullable

Optional. The ruleset version you built against, as results carry it in provenance.ruleset_version (e.g. 'sd-2026.11.14'), or its sha256: hash. If the rules have changed since, the call fails (nothing computed, nothing charged) and says what is in force now, so you upgrade on your own schedule. Leave it out to answer under the current rules.

Tektolo-Ruleset-Modestring nullable

Optional, with Tektolo-Ruleset. 'serve' asks us to answer under the ruleset version you named even when the rules have changed since, from that version's signed bundle. The answer says so (run.served_from_bundle and the Tektolo-Ruleset-Served header). We refuse (412, with a reason) a version older than 12 months, one a later correction or law change replaced for your state, or one we have no bundle for. Leave it out to be refused whenever the rules have changed.

Request body

client_refsobject nullable

Your own reference ids (e.g. unit_id, job_id). Echoed back, never used.

trade_vendorsobject

Vendor (name, contact) to put on each trade's lines.

read'parser' | 'ai'

parser (default): descriptions are read by the deterministic parser and matcher only; what they cannot place comes back as a manual-quote line with suggested codes. ai: what the parser cannot place is then read by an AI model; the answer is a draft (review.status) and echoes the reading, whose findings you confirm and send back for a verified answer (contract 0.12.0).

retainboolean

Optional (contract 0.5.0). false: keep none of this request's text. By default the finding descriptions are kept with contact details and access codes removed, to improve matching; the estimate is the same either way.

detail'summary' | 'full'

summary: totals, trade scopes, every line tied to a finding (capped at 40) plus the largest must-fix/refer-out lines, a one-line note on the routine lines left out, notes, and only findings needing attention (small). full: every line, finding and source.

Response

Successful Response

Changes

No recorded changes to this operation across all 1 revision of this API.