API releases
Follow the evolution of the MyCRM API: new integration capabilities, changes to data models and compatibility details for existing clients.
Latest release — 30 September 2026
Custom deal statuses and deal structure updates
- Read your organisation’s custom pipeline statuses and change the custom status of a deal.
- Update deal names and rationale fields to keep information aligned with your integration.
- Create and update deal structures, including loan amounts, rates, repayments and lenders mortgage insurance details.
Read the full release notes, including compatibility changes →
Browse by year
| Year | Highlights |
|---|---|
| 2026 | Custom deal statuses, deal structure updates, tasks, contact categories and expanded writes |
| 2025 | Deal securities, marital status, liability sub-types and enquiry-source details |
| 2024 | Lead matching, deal naming, referral context and deal note authorship |
| 2023 | Write operation availability, enquiry-source lookups and referrer models |
| 2022 | Initial reference, richer structured leads, asset lookups and external integration references |
About this history
This history covers 29 entries from 9 February 2022 to 30 September 2026. Historical releases are reconstructed from the published OpenAPI Specification on the documentation repository’s main branch, using its commit dates. New release dates are confirmed during review of the specification update. Each entry includes the corresponding operation and schema changes.
Merged changes are compared with the preceding main-branch snapshot, so intermediate work on feature branches does not appear as separate releases. The earliest available snapshot is the baseline. Small naming and description refinements are retained alongside capability changes to keep the record complete.
An operation is an HTTP method and path pair; GET and HEAD count separately. “Updated” includes changes to descriptions and shared path settings. Schema changes are listed separately because a field can change without its endpoint definition changing. A supporting schema’s presence does not by itself mean an operation is available.
For a detailed comparison, download the complete history. It contains every captured JSON change after the baseline, using JSON Pointer locations, exact before and after values, commit identifiers and SHA-256 hashes of the original OpenAPI Specification files. Formatting and object-key ordering are ignored.
Download complete release history (JSON) ↓Compatibility and beta
Review removed operations, field constraints and response shapes before updating an existing integration or regenerating a client. Use the current API reference for the contract documented by this portal; historical examples and operation lists belong to their dated release.
Endpoints marked Beta can change while being refined. A documented temporary 423 Locked response belongs to the beta availability phase. Check the published contract when an endpoint graduates; no graduation date is implied by these notes.
Known reference gaps
The current source specification refers to two response schemas that it does not define: the asset-finance and commercial-finance deal documents on related task endpoints. Those reference pages explicitly mark the missing schema details. Confirm the response shape with LMG before depending on it.
For questions about an integration or access, contact Ask LMG through your usual support channel with the environment and a sanitised example.