API releases — 2024
All API releases · How to read this history
15 November 2024 — Existing contact matching for leads
- Lead input gains
contactMatchExistingto select how an existing contact is matched. - The available matching combinations are email; email and mobile; email and name; email, mobile and name; email and date of birth; or email, date of birth and name.
306 operations after this release · 0 added · 0 removed · 0 updated. Schema changes are counted separately below.
Schema details — 1 added, 0 removed, 1 updated
Added schemas
ExistingContactCheck
Updated schemas and changed locations
LeadAttributes:/properties/contactMatchExisting
11 November 2024 — Lead naming and referral context
- Lead and structured lead inputs gain
dealNameandsourceReferrerId. - Referrer identifiers no longer carry the numeric-only constraint. Organisations gain the read-only
isBrokerSearchVisiblefield. - Supporting geometry enum values change, including
Point,Surface,False,ZandM.
Compatibility: Treat referrer identifiers as opaque strings. Review generated enum mappings if your client exposes geometry schemas.
306 operations after this release · 0 added · 0 removed · 150 updated. Schema changes are counted separately below.
Endpoint details
Updated definitions
GET /jsonapi/referrers/{id}HEAD /jsonapi/adviser-detailsHEAD /jsonapi/adviser-details/{id}HEAD /jsonapi/adviser-details/{id}/adviserHEAD /jsonapi/adviser-details/{id}/relationships/adviserHEAD /jsonapi/advisersHEAD /jsonapi/advisers/{id}HEAD /jsonapi/advisers/{id}/addressesHEAD /jsonapi/advisers/{id}/adviserDetailsHEAD /jsonapi/advisers/{id}/agreementHoldersHEAD /jsonapi/advisers/{id}/contactGroupsHEAD /jsonapi/advisers/{id}/organisationHEAD /jsonapi/advisers/{id}/relationships/addressesHEAD /jsonapi/advisers/{id}/relationships/adviserDetailsHEAD /jsonapi/advisers/{id}/relationships/agreementHoldersHEAD /jsonapi/advisers/{id}/relationships/contactGroupsHEAD /jsonapi/advisers/{id}/relationships/organisationHEAD /jsonapi/asset-categoriesHEAD /jsonapi/asset-categories/{id}HEAD /jsonapi/asset-sub-typesHEAD /jsonapi/asset-sub-types/{id}HEAD /jsonapi/asset-typesHEAD /jsonapi/asset-types/{id}HEAD /jsonapi/assetsHEAD /jsonapi/assets/{id}HEAD /jsonapi/assets/{id}/addressesHEAD /jsonapi/assets/{id}/ownershipHEAD /jsonapi/assets/{id}/relationships/addressesHEAD /jsonapi/assets/{id}/relationships/ownershipHEAD /jsonapi/contact-external-referencesHEAD /jsonapi/contact-external-references/{id}HEAD /jsonapi/contact-external-references/{id}/contactHEAD /jsonapi/contact-external-references/{id}/integrationHEAD /jsonapi/contact-external-references/{id}/relationships/contactHEAD /jsonapi/contact-external-references/{id}/relationships/integrationHEAD /jsonapi/contact-groupsHEAD /jsonapi/contact-groups/{id}HEAD /jsonapi/contact-groups/{id}/adviserHEAD /jsonapi/contact-groups/{id}/businessesHEAD /jsonapi/contact-groups/{id}/contactsHEAD /jsonapi/contact-groups/{id}/referrerHEAD /jsonapi/contact-groups/{id}/referrerOrganisationHEAD /jsonapi/contact-groups/{id}/relationships/adviserHEAD /jsonapi/contact-groups/{id}/relationships/businessesHEAD /jsonapi/contact-groups/{id}/relationships/contactsHEAD /jsonapi/contact-groups/{id}/relationships/referrerHEAD /jsonapi/contact-groups/{id}/relationships/referrerOrganisationHEAD /jsonapi/contactsHEAD /jsonapi/contacts/{id}HEAD /jsonapi/contacts/{id}/contactAddressHEAD /jsonapi/contacts/{id}/contactGroupHEAD /jsonapi/contacts/{id}/dealsHEAD /jsonapi/contacts/{id}/externalReferencesHEAD /jsonapi/contacts/{id}/ownershipHEAD /jsonapi/contacts/{id}/relationships/contactAddressHEAD /jsonapi/contacts/{id}/relationships/contactGroupHEAD /jsonapi/contacts/{id}/relationships/dealsHEAD /jsonapi/contacts/{id}/relationships/externalReferencesHEAD /jsonapi/contacts/{id}/relationships/ownershipHEAD /jsonapi/deal-external-referencesHEAD /jsonapi/deal-external-references/{id}HEAD /jsonapi/deal-external-references/{id}/dealHEAD /jsonapi/deal-external-references/{id}/integrationHEAD /jsonapi/deal-external-references/{id}/relationships/dealHEAD /jsonapi/deal-external-references/{id}/relationships/integrationHEAD /jsonapi/deal-notes/{id}HEAD /jsonapi/deal-notes/{id}/dealHEAD /jsonapi/deal-notes/{id}/relationships/dealHEAD /jsonapi/deal-participantsHEAD /jsonapi/deal-participants/{id}HEAD /jsonapi/deal-participants/{id}/contactHEAD /jsonapi/deal-participants/{id}/dealHEAD /jsonapi/deal-participants/{id}/relationships/contactHEAD /jsonapi/deal-participants/{id}/relationships/dealHEAD /jsonapi/dealsHEAD /jsonapi/deals/{id}HEAD /jsonapi/deals/{id}/adviserHEAD /jsonapi/deals/{id}/contactsHEAD /jsonapi/deals/{id}/dealNotesHEAD /jsonapi/deals/{id}/dealScenarioHEAD /jsonapi/deals/{id}/dealStructuresHEAD /jsonapi/deals/{id}/externalReferencesHEAD /jsonapi/deals/{id}/importantDatesHEAD /jsonapi/deals/{id}/participantsHEAD /jsonapi/deals/{id}/relationships/adviserHEAD /jsonapi/deals/{id}/relationships/contactsHEAD /jsonapi/deals/{id}/relationships/dealNotesHEAD /jsonapi/deals/{id}/relationships/dealScenarioHEAD /jsonapi/deals/{id}/relationships/dealStructuresHEAD /jsonapi/deals/{id}/relationships/externalReferencesHEAD /jsonapi/deals/{id}/relationships/importantDatesHEAD /jsonapi/deals/{id}/relationships/participantsHEAD /jsonapi/enquiry-sourcesHEAD /jsonapi/enquiry-sources/{id}HEAD /jsonapi/expense-categoriesHEAD /jsonapi/expense-categories/{id}HEAD /jsonapi/expense-categories/{id}/expenseTypesHEAD /jsonapi/expense-categories/{id}/relationships/expenseTypesHEAD /jsonapi/expense-typesHEAD /jsonapi/expense-types/{id}HEAD /jsonapi/expense-types/{id}/expenseCategoryHEAD /jsonapi/expense-types/{id}/relationships/expenseCategoryHEAD /jsonapi/expensesHEAD /jsonapi/expenses/{id}HEAD /jsonapi/expenses/{id}/ownershipHEAD /jsonapi/expenses/{id}/relationships/ownershipHEAD /jsonapi/income-categoriesHEAD /jsonapi/income-categories/{id}HEAD /jsonapi/income-categories/{id}/incomeTypesHEAD /jsonapi/income-categories/{id}/relationships/incomeTypesHEAD /jsonapi/income-typesHEAD /jsonapi/income-types/{id}HEAD /jsonapi/income-types/{id}/incomeCategoryHEAD /jsonapi/income-types/{id}/relationships/incomeCategoryHEAD /jsonapi/incomesHEAD /jsonapi/incomes/{id}HEAD /jsonapi/incomes/{id}/linkedAssetHEAD /jsonapi/incomes/{id}/ownershipHEAD /jsonapi/incomes/{id}/relationships/linkedAssetHEAD /jsonapi/incomes/{id}/relationships/ownershipHEAD /jsonapi/integrationsHEAD /jsonapi/integrations/{id}HEAD /jsonapi/integrations/{id}/contactExternalReferencesHEAD /jsonapi/integrations/{id}/dealExternalReferencesHEAD /jsonapi/integrations/{id}/relationships/contactExternalReferencesHEAD /jsonapi/integrations/{id}/relationships/dealExternalReferencesHEAD /jsonapi/liabilitiesHEAD /jsonapi/liabilities/{id}HEAD /jsonapi/liabilities/{id}/linkedAssetHEAD /jsonapi/liabilities/{id}/ownershipHEAD /jsonapi/liabilities/{id}/relationships/linkedAssetHEAD /jsonapi/liabilities/{id}/relationships/ownershipHEAD /jsonapi/liability-categoriesHEAD /jsonapi/liability-categories/{id}HEAD /jsonapi/liability-categories/{id}/liabilityTypesHEAD /jsonapi/liability-categories/{id}/relationships/liabilityTypesHEAD /jsonapi/liability-typesHEAD /jsonapi/liability-types/{id}HEAD /jsonapi/liability-types/{id}/liabilityCategoryHEAD /jsonapi/liability-types/{id}/relationships/liabilityCategoryHEAD /jsonapi/organisationsHEAD /jsonapi/organisations/{id}HEAD /jsonapi/organisations/{id}/addressesHEAD /jsonapi/organisations/{id}/relationships/addressesHEAD /jsonapi/property-typesHEAD /jsonapi/property-types/{id}HEAD /jsonapi/referrersHEAD /jsonapi/referrers/{id}PATCH /jsonapi/deal-notes/{id}/relationships/dealPOST /jsonapi/deal-notes/{id}/relationships/deal
Schema details — 0 added, 0 removed, 6 updated
Updated schemas and changed locations
Dimension:/enumLeadAttributes:/properties/dealName,/properties/sourceReferrerIdOrdinates:/enumOrganisationAttributes:/properties/isBrokerSearchVisibleReferrer:/properties/id/patternStructuredLeadAttributes:/properties/dealName,/properties/sourceReferrerId
18 January 2024 — Deal note authorship
- Deal notes gain the read-only
writtenByfield, supporting up to 500 characters. - Removes collection-level GET and HEAD operations for
/jsonapi/deal-notes. - Refreshes supporting schemas, including geometry types and the agreement-holder organisation relationship.
Compatibility: Use the available related-resource or individual-note operations instead of relying on the removed collection routes.
306 operations after this release · 0 added · 2 removed · 12 updated. Schema changes are counted separately below.
Endpoint details
Removed
GET /jsonapi/deal-notesHEAD /jsonapi/deal-notes
Updated definitions
DELETE /jsonapi/deal-notes/{id}DELETE /jsonapi/deal-notes/{id}/relationships/dealGET /jsonapi/deal-notes/{id}GET /jsonapi/deal-notes/{id}/dealGET /jsonapi/deal-notes/{id}/relationships/dealHEAD /jsonapi/deal-notes/{id}HEAD /jsonapi/deal-notes/{id}/dealHEAD /jsonapi/deal-notes/{id}/relationships/dealPATCH /jsonapi/deal-notes/{id}PATCH /jsonapi/deal-notes/{id}/relationships/dealPOST /jsonapi/deal-notesPOST /jsonapi/deal-notes/{id}/relationships/deal
Schema details — 15 added, 1 removed, 2 updated
Added schemas
CoordinateCoordinateEqualityComparerCoordinateSequenceCoordinateSequenceFactoryDimensionEnvelopeGeometryGeometryFactoryGeometryOverlayNtsGeometryServicesOgcGeometryTypeOrdinatesPointPrecisionModelPrecisionModels
Removed schemas
WorkbenchLogType
Updated schemas and changed locations
AgreementHolderRelationships:/properties/organisationDealNoteAttributes:/properties/writtenBy