What’s New
We are constantly working to improve your experience with the Platform. Have a look to see what new features and fixes have been released.
The latitude and longitude are now populated under ‘geolocation’ for offices in the Offices API:
Example Sandbox Office
We have added a new view ‘PROPERTY_STATUS_CHANGES’, to the Analytics Schema to expose a simple view of property status changes. The new view includes the following fields:
- ID
- PROPERTY_ID
- PROPERTY_CODE
- OLD_STATUS
- NEW_STATUS
- CHANGED_AT
- _CUSTOMER_ID
- _LAST_SYNCH_AT
Property Status Changes View
Property Manager field in AgencyCloud is now exposed under '‘LETTINGS_PRIMARY_PROPERTY_MANAGER_NEGOTIATOR_I’ in the Analytics Schema.
We have extended both the POST and PATCH tenancies endpoint to support Letting Fee (
lettingFee) and Management Fees (managementFee):
Letting & Management Fee fields (POST)
Next Call (nextCall) and Last Call (lastCall) are now exposed in the properties API:
Last and Next call fields
A new endpoint has been added to support updating existing enquiries:
New Enquires endpoint
If enabled, Rental Insurance information is now available under the ‘PropertyLettingModel’:
Rent Insurance Model
This also includes a new configuration endpoint to surface Cancellation Reasons:
Configuration Endpoint to support Rental Insurance
Property Licensing Data is now available on the properties endpoint, displayed under the ‘PropertyLettingModel’:
Licencing Model
In addition to this, we have added a new documentation type ‘LIC/Licensing’ to the document type configuration endpoint:
New Documentation Type
You now have the ability to embed ‘relationships’ via the companies endpoint:
Embed options on the Companies API
We now support tenancy renewal options (Tenancy Agreement Clauses) in the Tenancies API:
Renewal Options Model
This also includes 2 new configuration endpoints to support the tenancy renewal options and renewal optional conditions:
Tenancy Renewal Options Configuration Endpoint
Tenancy Renewal Option Conditions Configuration Endpoint
In addition, we have also included a ‘lettertext’ field in the TenancyAllowanceModel (/tenancies/{id}/allowances endpoint) & the TenancyResponsibilityModel (/tenancies/{id}/responsibilities):
Tenancies Allowances Endpoint
Tenancies Responsibilities Endpoint
3 new fields have been added under the Tenancy Break Clauses endpoint (/tenancies/{id}/breakClauses) to surface Break From (breakFrom), Required Notice (noticeRequired) and Letter Text (letterText):
Tenancies Break Clauses Endpoint
It is now possible to set the default window size of your app when it launches in AgencyCloud. Currently, all apps are launched based on the default configuration set by the customer. The standard configuration is set as Width 950 x Height 700.
Within the ‘AgencyCloud Integration’ section on your app, you will be able to adjust the size in which your app is presented in AgencyCloud:
Please note that only apps with a desktop integration type can modify the app size. If you do not have a desktop integration type, you will not be able to edit the default sizes.
Floor Level (
floorLevel), Property Internal Floors (internalFloors) & Total Building Floors (totalFloors) are now available both read and write:
Property Attributes in AgencyCloud
Example payload
We have added the field ‘checkTypeId’ to the POST /tenancies/{ID}/checks endpoint:
Example payload showing 'checkTypeId' field
It is now possible to view more information about an office group installation through the DeveloperPortal.
If your app is installed by an office group, you will receive an email and a webhook (if configured) with the customer ID, for example XXX-XXXX. The first 3 characters represent the organisation, the remaining 4 characters represent the office group ID. For more information on office groups please visit: https://foundations-documentation.reapit.cloud/faqs#what-are-office-groups
To see which offices are within that group, open your app in the developer portal and navigate to ‘Installations’:
'Installations' section on an App
This will display all active installations for your app. If you have an office group installation, for example RES-GRTA:
Example customer installation
You will have the option under the dropdown menu to ‘Show installed offices’:
Example office group installation information
This will provide you the name of the office group ‘Office Name’ and the office ID’s that form that group. From the example above, only office ‘BCK’ is in the office group ‘Market Town’.
To retrieve further information about an office, you can use the ‘ID’ in conjunction with the ‘Offices’ endpoint.
Related services: Applicants, Landlords, Tenancies, Offers & Vendors
AgencyCloud provides the option of a free text field to record additional contact information, such as ‘Wife’s Mobile’ in addition to the core fields such as Mobile, Home & E-mail.
By default, we will now return those additional contact details under the ‘additionalContactDetails’ array on the above related services.
Example AgencyCloud Applicant Record
Example core fields on the Applicants API
Example 'additionalContactDetails' array on the Applicants API
The ‘Details/Notes’ field is now available on a tenancy under ‘feeNotes’:
Details/Notes field in AgencyCloud
Example 'feeNotes' field
A new POST /bulk endpoint has been added to allow a creation of multiple journal entries:
POST endpoint for Journal Entries
We have added a new configuration endpoint ‘terminology’ to help developers understand customer specific terminology.
For example, some customers prefer to use 'Sold STC' instead of 'Under Offer' or 'Market Appraisal' instead of 'Valuation'.
Using the new configuration endpoint, this will make it easier to understand for each customer. Please see example for our Sandbox configuration:
Example 'Terminology' payload
It is now possible to filter by ‘Active’ status and by ‘OfficeIDs’ on the
/preTenancyCheckTypes and /renewalCheckTypes configuration endpoints:
New filtering options
It is now possible to both read and write to the ‘Repeat’ field on appointments:
Example 'Repeat' field in AgencyCloud
By default, the property payload will now return the name of the local authority ‘localAuthorityCompanyName’. Previously, it only returned the ID:
Local Authority field in AgencyCloud
'localAuthorityCompanyName' field
Added Authentication Security: By default, the ‘Authentication Client Secret’ will now be hidden and only accessible by an ‘Admin’:
Client Secret - Admin only
Non Admin users will see the following:
Client Secret - Non Admins
As an Admin, you can check or change the role of a user within your organisation by simply navigating to the ‘Members’ area.
We now support the option for 'Four Weekly' rent frequency on Applicants:
Rent frequency in AgencyCloud
Rent frequency example
Agreement signed is now available under the Property Letting Model:
Agreement Signed field in AgencyCloud
Other Agent information has now been added to appointments
otherAgent with the otheragentId available in the _links collectionThe list of allowed journal entry types has been expanded to now include ON (offerNote):
Example offer note
Two new filters have been applied to the Applicants endpoint to allow filtering by ‘Last Call’ (
hasLastCall) and ‘Next Call’ (hasNextCall):
'Next Call' section in AgencyCloud
Filtering options
We have added additional information on the ‘preTenancyCheckTypes’ configuration endpoint to surface if a check is ‘active or inactive’ and which offices the check applies to e.g. OXF, MKN:
Example payload showing 'active' and 'officeIds' fields
Management Fee information (percentage & amount) is now available in the Analytics Schema under the Tenancy Renewal table:
Fields available in the Analytics Schema
The Developer Edition has been upgraded to 12.160 which now includes a new desktop integration type of ‘Renewal Negotiation Check’
‘Renewal Negotiation Check’ can be given to an application that will replace the checks section on a Renewal Negotiation screen in AgencyCloud.
Checks section in AgencyCloud
Also coming soon, the ability to launch apps from the images section in AgencyCloud.
The property images endpoint now respects the maximum dimensions that are set in a customer's configuration.
When a tenancy is in an arranging status, we now expose the contacts associated to the attached applicant in the
related collection. Company information is now returned on a contact under the company link.
Converted room dimensions are now returned on a property under ‘
dimensionsAlt’. 
Property Rooms and Accommodation screen in AgencyCloud
Example 'dimensionsAlt'
Release 4.0.0
.png?alt=media&token=6ef5304c-f0ef-4dba-b3fd-784fdaae9b7b)
New Features
- Visual Language has been revamped with detailed rules for icons, fresh new icons and improved styling for better visual consistency.
- Iconography (Visual Language section) has been reorganised into new categories.
- Product Brand Imagery (Visual Language section): a full set of illustrations was added to the collection.
- Mobile navigation has been added to UI Elements
Bug Fixes
- Reapit and ReapitConnect logo sizes have been adjusted
- ReapitConnect logo is now a vectorial image
- One Choice Chips (Segmented Control) has been renamed to Toggle Button. Its width size changed from static to dynamic.
- Desktop - Full Options Expansion Panel style has been changed (shadow and outline)
Custom applicant attributes that are usually captured on the requirements screen under ‘Must Have’ or ‘Special/Special Requirements’, are now surfaced for applicants under ‘specialFeatures’:
Applicant Requirements screen in AgencyCloud
Example Special Features Data
The ‘Renting Position’ is now surfaced on an applicant under ‘
renting.positionId’:
Applicant status screen in AgencyCloud
Example 'positionId'
Note: The renting position list is configurable and can be cross referenced against a new sub-resource under the Configuration endpoint ‘GET /configuration/rentingPositions’.
You can now create pending supplier invoices using the new sub-resource under the Transactions endpoint ‘POST /transactions/supplierInvoices’:
For the full specification, validation, and behaviours, please review ticket https://github.com/reapit/foundations/issues/7764 in conjunction with the swagger documentation.
‘Tenancy Alterations’ data is now included in the Analytics Schema:
Analytics Schema
It is now possible to set an applicant as a Potential Client (
potentialClient):
Applicant Status screen showing the 'Potential Client' field In AgencyCloud
Potential Client field
We are now surfacing remaining lease (
leaseRemaining) information on Applicants:
Applicant Requirements screen showing the 'Remaining Lease' fields in AgencyCloud
Reaming Lease field
'Pre Instruction Checks' data is now included in the Analytics Schema:
We now support the option to POST to the Journals endpoint the following letter types:
Arrears Letter (AL),
Notice to Quit Letter (NQ),
Tenancy Renewal Letter (TR),
Letter Sent (LE)
Please note: In the case of AL/NQ/TR the associated type MUST be ‘tenancy’.
The ‘Text’ field (
urlcaption) is now both read and write:
Marketing Screen showing the 'Text' field in AgencyCloud
Text field
'Referral' data is now available within the Analytics Schema:
It is now possible to update the ‘marketingConsent’ field on an archived contact record:
Please note: Only the Marketing Consent field on an archived record can be updated.
As you may have already seen, on Wednesday 26th, we launched the latest version of the AppMarket. The updated AppMarket includes and now supports, app name & developer searching, new categories and filter options plus featured apps and app collections:
Part of the redesign will now allow customers on Rackspace, to view apps that were previously hidden due to the compatibility with AWS. Whilst they still will not be able to install or enable integrations that use data Webhooks, they will now be able to enquire about the app/integration, view the marketing materials and videos.
The new AppMarket now also includes the ability for Developers to add videos to their app listings. ‘Getting Started’ & a ‘Why’ video. For information on how to add a video to your app listing, please click here.
Applicant Tenure information is now available in the Applicants ‘Buying’ modal:
We now support filtering on the Companies endpoint by Office Groups.
For more information on office groups, please visit https://foundations-documentation.reapit.cloud/faqs#what-are-office-groups
‘Allowances’ can now be created and updated:
‘Break Clauses’ can also be created and updated:
And also for ‘Responsibilities’:
It is now possible to patch nested objects in the Metadata API
We have exposed the
ValuationDate & AgreementExpiry dates under the property selling modelVideos
Applistings now support the ability to add video URL's. Under the section 'AppMarket Listing', you'll see 2 new fields:
The video's will then be rendered in the AppMarket:
Please note: We recommend strongly that if you do upload videos, to use the online streaming site YouTube.
App Deletion
To prevent accidental data loss, we have added an additional layer of protection for apps. On each app, under the section ‘AppMarket Listing’, you will now see the following check box:
If you should then accidentally select ‘Delete’, you’ll be prompted the following message and will need to disable the additional protection before you can delete the app:
Please Note: The app data protection check box is not selected by default so, to ensure your apps and its associated data are protected, please review your app listing.
Unmapped attributes:
Property and Applicant attributes/requirements (department data) is completely customisable for each agent and subsequently it can be difficult to understand how to interpret this data as it comes out of the various APIs that expose it.
As the Platform APIs are standardised across all our customers, Department data has also been standardised where possible using a mapping mechanism to map the customisable values from our CRM into standard values in the API.
Any options that do not have a corresponding mapping and are selected on a Property or Applicant entity will be included in the
unmappedAttributes and unmappedRequirements collections in their respective APIs. Additionally, the Special attributes column in the CRM is mapped explicitly.Example payload:
Fields:
To view the latest version of the mappings, please visit: https://foundations-documentation.reapit.cloud/platform-glossary#interpreting-department-data
The Properties API now displays the Maximum Reception/Bathroom ranges:
It is now possible to create a Works Orders journal entry:
Note: TypeID must be set to 'WO' when passing worksOrder
We now support filtering on the Companies endpoint by Negotiator and Office:
Applicant ReasonID and SellingPosition now available using POST and PATCH methods:
New ‘Diary’ desktop integration type now available from version 12.152.3. App’s that have selected ‘Dairy’ as the integration type will be launched from an existing appointment. For more information, please click here.
It is now possible to read deposit and deposit holder information via the tenancies API. This information can also be written back up to a certain status:
It is now possible to filter tenancy checks by type:
Market Appraisal (valuation) price now available:
Pre-Instruction checks can now be managed via /properties/{id}/checks:
It is now possible to find applicants by phone number (and any other contact detail):
Webhook transactions can now be filtered much more granularly to allow you to find transactions more easily (Topic name, Entity ID & Event ID):
The validation has been updated to more closely match the contacts API
The Referrals API has now been enhanced to support updating (PATCH) and the ability to store metadata:
It is now possible to see the Id’s of disabled portals set against a property:
The ID’s are stored on the configuration endpoint for portalTypes.
You can now filter properties by AreaId:
Our multi currency support milestone has been completed. It will be most beneficial for UK customers that advertise international properties. For more information, please review our milestone here.
When creating a new enquiry (which is visible on the Internet Registration panel in AgencyCloud) you can now pass price/bedroom requirements for sales and lettings applicant enquiries:
We have added support to allow retrieval of ‘tenancy’ journal entries.
Rural property data is now exposed with certain fields writeable under the ‘rural’ section on a property:
Lettings management fees, type and amount now available under the ‘managementFee’ section:
Number of units (numberOfUnits) in a development now available:
Minimum tenancy term (minimumTerm) now available for lettings properties:
‘smallHolding’, ‘estate’ & ‘developmentOpportunity’ property types are now available via the Properties, Departments & Applicants endpoints. Please note, the additional types are only available in some customer's systems. The 'Departments' endpoint should be used to understand the configuration of a specific customer.
Contact categories can now be retrieved using the ‘Configuration’ endpoint ‘contactCategories/{id} and can also be set on a ‘Contact’:
Public brochure URLs (publicBrochureUrl) are now available in the Properties API under either the ‘Selling’ or ‘Letting’ object:
A works order note (worksOrderNote) can now be added at the property level which will cascade down to any works order for that property in Agency Cloud:
Office status can now be obtained from the Offices API so you can understand whether an office is open or closed based on the field type ‘active’:
Last week, we released the first phase of the ‘Referrals’ endpoint which includes the following:
The second phase will include the ability to write to the endpoint, metadata & associated webhooks. You can track the phase 2 milestone here
Journal Entries: You can now store a journal entry of Match (MA) against a property or applicant record
Bedroom Range: The ‘Max’ bedroom range is now exposed in the Properties API – this is most useful for marketing of property developments.
Properties: We have added support for Juliette Balcony (property situation), Studio (property style) and Villa (property type).
Companies: Additional contact information is now available for companies. The additional information is available in ‘additionalContactDetails' object:
Transactions: It is now possible to filter transactions by ‘Outstanding’ amount.
The latest release of the Developer Portal (v3.0.5) included the re design of the following pages…
Settings: We have updated the UI within the settings section in accordance with our design system and the other pages within the portal. The options available to you when accessing settings will be dependent on your user level:
Admins of an organisation can set the level of users (members) on the ‘Members’ page.
Analytics: We have separated the features and information available to you in specific sections: ‘API Usage’, ‘Costs’ & ‘Installations’.
You can use the filters on the left-hand side to set the data results for each page.
In the latest release of our Design System Figma file, we introduced new button states and a new component. We have also fixed a few bugs and revised/added additional documentation for buttons.
New Features
- Disable and hover states for desktop buttons
- Disable state for mobile buttons
- New medium size infographic icon (Manage App Listing)
- File Upload component
- Measurements: misspelling on the red static button; it was 38px, now it’s 40px
- Measurements: misspelling on the ‘One Choice Chips’ component - active state, selected chip, padding was 4px and now it’s 3x, margins were 3px and now it’s 4px
- Documentation about button types was added to all components that use them
- Static button with icon has been documented
- Static button width size for mobile has been increased to 120px
- Guidelines for static and dynamic buttons have been revised
- Desktop - Full Options Expansion Panel: button margins and distance between buttons and content have been revised
We are pleased to confirm, the Properties API has been updated to provide the following information ahead of the Material Information requirement by the end of May 2022. Related information here.
The following fields are available:
- Council Tax Band (
councilTax) - Local Authority (
localAuthorityCompanyId) - Ground rent for leasehold properties (
groundRent&groundRentComment) - Maintenance charges for leasehold properties (
serviceCharge&serviceChargeComment) - Leasehold length (
tenure.expiry)
Last week, we updated our Webhook functionality to increase throughput and to reduce latency. We have seen a significant improvement already. We have enhanced the way in which we process webhook events. Nothing has changed for you in how you create or manage your webhooks but the background service has been re developed to better increase the rate in which they are emitted.
Deposit Data (Type & Amount) is now available inside the Lettings object on Properties API under ‘deposit’:
Properties by Negotiator ID(s)
Properties by Country ID:
To better help us identify the company you are associated to and help with triaging tickets that are raised via GitHub, you can now save your GitHub username on your ‘Profile’ page in the DeveloperPortal:
This week, we have released a new version of the Developer Portal, specifically an updated version of the app creation flow and app edit pages.
The new design has been developed to improve the UI (now using Elements V3) and to improve the user experience. We’ve also added a very helpful new feature. Read below to find out more.
To better help you navigate the app creation process, we have included a helpful app creation wizard. The wizard is designed to make creating an app as straightforward as possible by preselecting/populating certain fields based on your use case.
You can select the type of integration from the list below:
Or if none of the above suit your requirements, simply scroll down and select either a Client-side app or Server-side Integration:
With every selection, we will present the associated documentation on the right-hand side to help you with the process.
You’ll find helpful links for more information or on certain selections, a short video.
When you have completed the wizard, you’ll be directed to the ‘App Details’ page. This page will contain all the information you need to get started developing right away, such as the Client ID and or Client Secret:
The app name will be pre-populated based on your company name. You can change this at any stage.
To edit your app, simply click ‘Edit App’ from the left-hand navigation.
Depending on what type of app you have selected from the wizard, you’ll be presented with various tabs. The first tab for all types is the ‘About Listings’.
On the ‘Edit App’ page is where we have introduced a new feature ‘Check Status’.
The check status button is a very quick and easy way to see the current status of your app, what information is missing, your AppMarket status and to see if have any changes that require saving.
The process for submitting your app for review is the same as before. Simply check the status of your app and once all checks have been completed (see example below):
A button on the left-hand side will appear ‘Submit Review’. This will create a revision to our Admin team.
Once your app has been approved (please click here for more information on the reviewal process) the button will change to present the option to ‘Delist’ your app.
The additional tabs, as mentioned previously, will depend on your app type but in all cases, you will have an ‘AppMarket Listing’ and a ‘Permissions’ tab.
The ‘AppMarket Listing’ tab captures the app listing content for the AppMarket and will need to be completed before submitting your app. Images, description, contact information etc.
The ‘Permissions’ tab will relate to the endpoints and data sets you wish to interact with and the visibility of your app (either public or private).
For other types of integrations, you will see the tabs for AgencyCloud Integration and Authentication.
We will be continuing to update the Developer Portal in the coming months to further enhance the user experience and features available to you.
You can now interact and launch with the native works orders screen and pre populate certain search criteria using the newly added AgencyCloud scheme:
agencycloud://worksorders/{id}
The category of Match Output would enable an application to be used to export the details of a match either from an applicant to a property or a property to an applicant.
An app with the integration type 'Match Output' will be visible by selecting 'Print' after running a match:
We are now returning (when manually entered) the Property URL, which is accessible from the 'Marketing' screen:
Properties Endpoint
Marketing Screen in AgencyCloud
Please note: The URL will only be returned when it has been explicitly set. Default URLs' will not be available.
The featured property image (featuredImageUrl) is now being returned in the properties object, without the need to embed or make an additional call to the property images endpoint. This will be mostly beneficial for website integrations for property results.
We are now returning the Property Manager ID (propertyManagerId) within the lettings object on a property.
We have now added the ability for users to request additional extras fields for Works Orders and Landlords.
Also, you can now filter by ‘QuoteAccepted’ on Works Orders.
We have now updated our code generation mechanism to now support office specific referencing.
We have recently updated our Development Request documentation to now include a FAQ’s section.
Part of the update to the documentation includes a detailed description on each label, column and board.
Please take the time to review the updated documentation and ensure you understand how feature requests and bugs are triaged via the Platform.
In addition to the updated documentation, we will shortly be implementing a ‘GitBot’. The GitBot is designed to auto reply to specific issues raised, when issues are moved to certain columns, assigned specific project boards or certain labels added.
Essentially, an automated comment to will be added to the issue which will help explain the reason a specific label was added, why it was moved to a certain column and the time frame in which we expect the work to be completed by. The automated email will be sent the person that raised the issue or anyone that has subscribed.
If you would like to receive a notification (email) to an issue you are following but have not raised, please make sure you are subscribed, using the ‘Subscribe’ option from the right-hand navigation.
Please do not contact our service desk, customer success managers or any other channels within Reapit with regard to the status or timeline of an issue. Please first refer to the documentation and communicate with developers directly in GitHub.
The documentation is intended to provide guidance to our Developers when building apps and integrations through the Developer Portal.
Currently, it offers support on the following topics:
We will continue to add and update this section but don’t forget, we also have a dedicated page for FAQ's, which can be found here.
Remember, if you are having an issue not covered in the documentation or you have discovered a bug, please raise an issue on our public board by clicking here.
The email address you entered when registering for the Developer Portal, is used by default to receive email notifications,. For example, when your app is installed from the AppMarket, you will receive an email with the details (see more information here)
As you cannot change the email address that registered your organisation, we have now provided the ability to supply an alternative ‘Notifications Email’.
Please note: Only an Admin will have the correct permissions to update this information.
We are pleased to announce have added new endpoints to the Properties endpoint to now allow for reading and writing of ‘Certificates’.
In conjunction with the new entities, we have also added to our Configuration endpoint, the ability to surface CertificateTypes.
We have now included a ‘Transactions Logs’ section on the ‘Webhooks’ page, to allow you to filter your transactional Webhook history by date and app.
To view your webhook transaction logs, simply navigate to the ‘Webhooks’ page inside of the Developer Portal, select a date range (will default to the last 7 days) and select an app:
From each log item, you will be able to see the URL, the selected topic, status and the option to ‘Download’.
Selecting ‘Download’ will save a copy of the specific payload as a JSON file.
We have added the following new Webhook topics:
appointments.cancelled
appointments.confirmed
contacts.optedout
enquiries.accepted
enquiries.rejected
offers.rejected
offers.withdrawn
offers.accepted
properties.selling.askingpricechanged
properties.selling.completed
properties.selling.exchanged
properties.selling.withdrawn
properties.selling.instructed
properties.selling.lostinstruction
properties.selling.underoffer
worksorders.cancelled
worksorders.complete
worksorders.raised
If you wish to setup subscriptions to any of the new the topics listed above, you will need to have selected the associated scopes.
For more information on the required scopes, please visit the associated documentation here.
We have introduced a new REST Hooks Endpoint. This functionality allows you to programmatically set up webhook notifications for your application rather than needing to do this manually using the ‘Webhooks’ page in the developer portal which can help you automate onboarding of customers.
We continue to develop new features and products on the Foundations Platform and have updated our Terms and Conditions to reflect these changes.
From 25th June, when you next login to the Developer Portal, you will be presented with the latest updated terms and will need to accept before continuing to use the Developer Portal.
Our current and revised terms can be accessed through the Developer Portal documentation under ‘Developer Terms and Conditions’.
Our desktop integration types have been extended to now include the following communication types included in AgencyCloud from version 12.130.1 :
- Outbound – Email
- Outbound – Landline
- Outbound – Mobile
On each communication type, the Desktop API will provide a 'cntCode' and relevant communication information, either email, landline number or mobile number.
App that’s have any of the above desktop integration types will be visible in AgencyCloud when right clicking on the relevant icon, please see example below:
The Developer Edition of AgencyCloud has automatically been updated to include the new communication types.
It is now possible to set or clear default property brochures when updating existing properties, using the PATCH method on /properties/{id}
Updating the ‘brochureId’ field on the ‘Selling’ and/or ‘Lettings’ models with a document ID, will set a PDF as the predefined property details. Please see an example in the Property Details screen from within AgencyCloud (Desktop CRM) below:
To ensure data viability and security, we have made a change to the way 'Sandbox only' Webhooks are handled.
Webhooks that have been setup specifically for Sandbox testing (SBOX) and have been unmodified for 14 days, will automatically be deactivated.
Should you wish to continue using Webhooks for Sandbox testing, you can reactivate it again by selecting the check box ‘Active’ when editing. 
We have added additional support for uploading files over 6MB (Up to 30MB) to the Property Images and Documents endpoints via the use of pre-signed URL's
We are excited to announce today, the Developer Portal, Reapit AppMarket and AppMarket Apps UI have been updated in conjunction with the release of our Elements UI library version 2. The functionality of all apps remain the same but with UI enhancements to your user experience.
The visual changes you see are the first step towards a universal design language we have been working over the first part of the year. In the coming months you will see continued incremental updates as pages and flows are re-worked for better UI consistency, polish and UX. In keeping with our open source commitment, in the coming months we plan to make available publicly the design language, sample layouts and designs so that Reapit Developers can leverage our design resource to build better user experience into their own AppMarket apps.
Because we ask that all AppMarket Apps use our UI for visual consistency, we wanted to give the style guide a lift to ensure it best showcases of our development partner's work. This is the core of the Elements v2 release - it is a subtle evolution of the library, including a new font, typography, colour pallet, form inputs, notifications, dialogue boxes and much more.
Care has been taken to avoid breaking changes both to React Components and CSS Classes so that upgrading for all developers should be trivial and painless. We will also offer ongoing long term support in terms of security and bug fixes for the v2.x.x release. You can see the updates to the React Storybook here: https://elements.reapit.cloud/?path=/docs/
This however is just the start and we are now looking ahead to version 3 of Elements. Version 3 will be a ground up re-write of the library, both implementing fully the new design language and responding to both internal and external developer feedback. The version will focus on three core areas of improvement:
- Visual UI refinement and consistency, fewer components and clearer design patterns to implement.
- Better documentation for both React and non-React users, including suggested use cases and composed components for off-the-shelf UI / UX flows.
- Much smaller library with very little required JavaScript and very few dependencies. Elements will be about the visual presentation with developers free to make their own choices as to how to implement behaviours. This will mean a far better developer experience, especially for non-React users and a much more flexible, less opinionated library.
For more information about the latest release and news about Elements 3.0 (coming soon) please click here.
A new configuration option is now available when editing existing/creating new webhooks.
By default, webhooks will not be emitted when only the entity's eTag and modified timestamp has changed.
If you would prefer to receive notifications in this situation, please use the 'Ignore notifications where only the eTag has been modified' toggle option when configuring your webhook. See example below:
Adding a New Webhook
Existing webhooks will remain as they are and you can edit your webhooks at any stage from the 'Webhooks' page in the Developers Portal