Domain > webhooks.theliftsystem.com

More information on this domain is in AlienVault OTX

Whois

Property	Value
NameServer	NS2.PEER1.NET
Created	2013-01-23 00:00:00
Changed	2015-01-24 00:00:00
Expires	2016-01-23 00:00:00
Registrar	GODADDY.COM, LLC

DNS Resolutions

Date	IP Address
2024-07-30	3.98.174.186 (ClassC)
2026-01-17	104.18.0.43 (ClassC)

HTTP/1.1 200 OKDate: Sat, 17 Jan 2026 09:35:59 GMTContent-Type: text/html; charsetutf-8Transfer-Encoding: chunkedConnection: keep-aliveset-cookie: __cf_bmRT4TCdp7xVdZpKxJEw4zBWQV7mAkiVtKdXBHfKSiLfo-1768642559.0886896-1.0.1.1-fJIrUOR41a8EwgT9NP7x3NAJJy6tKt3lzG5r.zoGl8p4tlfJK_Is1KUhYXhh.wOupXPFEnFphrro9_LH_eej4w6f50zH_FcSILinPsP6ICSLt.fxllOAM1KvFnmPHMmG; HttpOnly; Secure; Path/; Domaintheliftsystem.com; ExpiresSat, 17 Jan 2026 10:05:59 GMTcf-cache-status: DYNAMICServer: cloudflareCF-RAY: 9bf4dd9a4b650384-PDX

!DOCTYPE html>html>head>title>LIFT Web Hooks/title>link relstylesheet hrefstyle.css>/head>body>header>div classcontainer>h1>LIFT Web Hooks/h1>/div>/header>div idcontent>div classcontainer>h1>Overview - LIFT System Web Hook Usage/h1>section classauthentication>h2>Authentication/h2>p>Use HTTPS Basic Auth with your API username and password. Please do not attempt to connect with unencrypted HTTP./p>label>Example: HTTP Header/label>code classblock>Authorization: Basic dGVzdDoxMjM/code>label>Example: Using curl/label>code classblock>curl -u user:password https://webhooks.theliftsystem.com/api/properties/test/code>/section>section classenvironments>h2>Environments/h2>p>While testing, you will be given access to our staging environment. After successful integration, youraccess will be upgraded to production./p>p>To use the staging environment, use code>staging//code> instead of code>api//code> as the first part of the pathsection of any API call./p>label>Example: URL/label>code classblock>https://webhooks.theliftsystem.com/staging/properties/test/code>/section>section classurls>h2>URL Structure/h2>p>The base URL is code>https://webhooks.theliftsystem.com/code> for any endpoint. The HTTP method determines the operation of your request./p>p>The first path component determines the environment (code>api/code> or code>staging/code>), the second componentis the resource you will be retrieving or modifying, and the third is the client key./p>label>Basic structure for all requests/label>code classblock>https://webhooks.theliftsystem.com/<api|staging>/<resource>/<client>/code>p>For some requests, you may need to specify tiers of resource IDs based on our resource hierarchy. Withcode>GET/code> requests for specific resources, you will need to specify the IDs in the URL. For other requesttypes, the IDs can be specified in the URL, but are more ideally specified in the object(s) in the body./p>p>To specify resource IDs in the URL, append them to the basic structure above along with the IDs of any parentresources they may have. Start with the highest level resource and work down to the lowest./p>label>Request structure when including resource IDs/label>code classblock>/api/resource/test/propertyId/photoId|suiteId/floorplanId/code>label>Example: Get all properties/label>code classblock>GET https://webhooks.theliftsystem.com/api/properties/test/code>label>Example: Get specific property/label>code classblock>GET https://webhooks.theliftsystem.com/api/properties/test/10/code>label>Example: Get all photos for a property (10 is property ID)/label>code classblock>GET https://webhooks.theliftsystem.com/api/photos/test/10/code>label>Example: Get all floorplans for a specific suite (10 is property ID, 100 is suite ID)/label>code classblock>GET https://webhooks.theliftsystem.com/api/floorplans/test/10/100/code>/section>section classoperations>h2>Operations/h2>h3>GET (retrieve)/h3>p>To request information about a resource, use the a normal code>GET/code> request with no body. For requests aboutspecific resources and/or requests about subresources, IDs will need to be specified in the URL (see URL Structuresection)./p>label>Example: Plain HTTP Request/label>code classblock>GET https://webhooks.theliftsystem.com/staging/properties/test br>Authorization: Basic dGVzdDoxMjM/code>h3>POST (create/update)/h3>p>To create or update a resource, always use the code>POST/code> verb and include the data in the request body./p>p>Your request payload will need to include a unique ID for your resource, which the system will useto determine if a code>POST/code> request is a create or an update./p>p>When requesting any child resource (suites, photos, floorplans), you will also need to specify the parent IDwhen the resource youre sending is to be created. The parent ID is optional for updates, but recommendedto include it for consistency./p>label>Example: POST with curl/label>code classblock>curl -u user:password -X POST -H Content-Type: application/json -d {id:10,name:Test Property}https://webhooks.theliftsystem.com/api/properties/test/code>label>Example: XML POST with curl on staging/label>code classblock>curl -u user:password -X POST -H Content-Type: text/xml-d <Property><Id>10</Id><Name>Test Property</Name></Property>https://webhooks.theliftsystem.com/staging/properties/test/code>label>Example: POST a suite belonging to property ID 10/label>code classblock>curl -u user:password -X POST -H Content-Type: application/json -d {id:100,propertyId:10,name:Studio}https://webhooks.theliftsystem.com/api/suites/test/code>h3>DELETE (remove)/h3>p>To delete a resource, use the HTTP code>DELETE/code>. You can specify the resource ID in the URL (along with anyparent IDs if its a child resource), as specified in the URL Structures section. However, you can also deletemultiple resources at a time by providing the IDs in the body instead - similar to an update, but the ID (andoptionally parent ID) are the only fields provided./p>p>You can only delete resources youve created, and all resources use soft deletion./p>label>Example: DELETE a single photo with curl (returning as XML)/label>code classblock>curl -u user:password -X DELETE -H Accept: text/xml https://webhooks.theliftsystem.com/api/properties/test/10/code>label>Example: DELETE two floorplans with curl using JSON/label>code classblock>curl -u user:password -X DELETE -H Content-Type: application/json -d {id:1000},{id:1001}https://webhooks.theliftsystem.com/staging/floorplans/test/code>/section>section classpayload>h2>Payload/h2>p>The following information applies to LIFTs default Web Hook. If youre using a custom format, pleasecontact us for specific information./p>p>Payloads for the Web Hook can be in JSON or XML format, specified by the requests code>Content-Type/code>header. The payload for a request should be a single resource, or an array of resources, which matchesthe resource specified in the request URL./p>p>When creating a new resource, a bare minimum of data must be met (see sample files), but when updating,it is only required to provide the resources code>id/code> and the data that actually needs to be changed.Also see Resources section below for some elaboration./p>p>Here are a few example files that show the breakdown of resources and the fields available for each of them./p>ul>li>a href/docs/samples/json target_blank>JSON Sample/a>/li>li>a href/docs/samples/xml target_blank>XML Sample/a>/li>li>a href/docs/samples/xsd target_blank>XSD for XML/a>/li>/ul>/section>section classresponses>h2>Response Format/h2>p>All responses will have the following properties at the top level (as an object if using JSON, or directchildren of the root node in XML). The property will be all lower-case if in JSON, or have an uppercasefirst character if its in XML./p>p>Use the code>Accept/code> header with a value of text/xml to receive the response in XML, otherwise it willdefault to JSON (or, if your request includes a payload and a code>Content-Type/code> header, it will defaultto that value instead)./p>p>If the request results in a client error, the HTTP status code will be set in the 400s, but the body willstill be returned with a status and message. However, if the request results in a server error (500s),it may not manage to serve a response body in your chosen format. If you get a server error, please contactus with the details of your request so we can fix it./p>h3>Status/h3>p>Possible string values: code>success/code> or code>error/code>/p>h3>Message/h3>p>A human-readable message depending on context./p>h3>Results/h3>p>The data result of your action, if applicable. This will always be an array in JSON, even if its an arrayof one object./p>/section>section classids>h2>Resource Identification/h2>p>Every resource and sub-resource needs to include an code>id/code>, or it will be rejected. The code>id/code>needs to be completely unique among every resource in your system, not just unique among those belongingto the parent resource. For example, a suites code>id/code> cannot be shared with any other suite, includingthose belonging to a different property./p>/section>section classresources>h2>Resources/h2>h3>Properties/h3>p>Properties are the primary resource for managing data in the LIFT System. They are at the top level of theproperty resource hierarchy, with no parent./p>p>Amenities, Utilities, Photos, and Suites are direct children of properties./p>h3>Amenities / Utilities/h3>p>Amenities and Utilities are collections that belong directly to the Property, and do not have correspondingendpoints in this API. To update the collection of amenities or utilities, perform an update of the property,with these collections specified as arrays on the property object./p>p>When updating either of these collections, please specify the entire array. Any that are not present in the listspecified by the update will be strong>removed/strong> from the collection./p>p>Any free text is accepted for amenities. If not matched to an existing amenity in LIFT, it will be createdas a custom amenity./p>p>Utilities must be one of the following:/p>ul>li>heat/li>li>water/li>li>electricity/li>/ul>h3>Photos/h3>p>Photos are children of properties, so you will need to specify the code>propertyId/code> when creating one./p>p>Actual photo data should be published to any valid HTTP(S) endpoint that this server is allowed to access.The submitted resource should include a URL, which this system will fetch and download as part of thehook process./p>h3>Suites/h3>p>Suites are children of properties, so you will need to specify the code>propertyId/code> when creating one./p>p>Floorplans are direct children of suites./p>p>Suite availability is in two parts: code>available/code> is 0 or 1 (or even -1 for waiting list only). Then,if the code>available/code> is 1, the code>availability_date/code> indicates whether its available in the future(specified date), or now (earlier or no date)./p>h3>Floorplans/h3>p>Floorplans are children of suites, so you will need to specify the code>suiteId/code> when creating one./p>p>Each floorplan can have an image, a file (preferably PDF), or both. As with photos, each image and/or fileshould be published to a valid HTTP(S) endpoint accessible from this server./p>/section>/div>/div>footer>div classcontainer>p>Copyright © 2026a hrefhttps://www.landlordwebsolutions.com target_blank>Landlord Web Solutions Inc./a>All rights reserved./p>/div>/footer>div idfoot>script typetext/javascript srcpage.js>/script>/div>script>(function(){function c(){var ba.contentDocument||a.contentWindow.document;if(b){var db.createElement(script);d.innerHTMLwindow.__CF$cv$params{r:9bf4dd9a4b650384,t:MTc2ODY0MjU1OQ};var adocument.createElement(script);a.src/cdn-cgi/challenge-platform/scripts/jsd/main.js;document.getElementsByTagName(head)0.appendChild(a);;b.getElementsByTagName(head)0.appendChild(d)}}if(document.body){var adocument.createElement(iframe);a.height1;a.width1;a.style.positionabsolute;a.style.top0;a.style.left0;a.style.bordernone;a.style.visibilityhidden;document.body.appendChild(a);if(loading!document.readyState)c();else if(window.addEventListener)document.addEventListener(DOMContentLoaded,c);else{var edocument.onreadystatechange||function(){};document.onreadystatechangefunction(b){e(b);loading!document.readyState&&(document.onreadystatechangee,c())}}}})();/script>/body>/html>

Subdomains

Date	Domain	IP
api-staging.theliftsystem.com	2024-06-28	54.237.133.81
api.theliftsystem.com	2015-03-18	54.243.125.235
cdn.theliftsystem.com	2023-12-18	18.155.202.24
admin.theliftsystem.com	2026-01-07	104.18.0.43
webhooks.theliftsystem.com	2026-01-17	104.18.0.43
www.theliftsystem.com	2025-12-13	104.18.0.43

View on OTX | View on ThreatMiner

Data with thanks to AlienVault OTX, VirusTotal, Malwr and others. [Sitemap]

Domain > webhooks.theliftsystem.com

Is this malicious?

Whois

DNS Resolutions

Port 443

Subdomains