Property & Compliance Management

Understand no generic Real Estate REST API

Do not expect a documented external REST API from the supplied module.

Reviewed 27 October 2026Merged module 2.1.3
Where to goTechnical reference → supplied controllers/routes

Before you start

Use the account and administrative authority appropriate to the data. Retention and legal holds are separate from routine record editing.

Follow these steps

  1. Identify the account, record type and evidence affected by this task.
  2. Do not expect a documented external REST API from the supplied module.
  3. The controllers are CRM/web routes, not a generic versioned REST API.
  4. The relevant access, retention or evidence control has a verified result.

Fields, rules and limits

  • The controllers are CRM/web routes, not a generic versioned REST API.

Check it worked

The relevant access, retention or evidence control has a verified result.

If something does not look right

If the expected result is missing, check the saved record, the current workspace and the action’s permissions. Record the exact validation message; do not repeat a state-changing action until you know whether the first attempt saved.

Questions and answers

What should I verify for this task?

The controllers are CRM/web routes, not a generic versioned REST API.

Why is the record or action unavailable?

Use the account and administrative authority appropriate to the data. Retention and legal holds are separate from routine record editing. Check the current company and record relationship before requesting additional access.