Download the PHP package timitek/getrets-laravel without Composer
On this page you can find all versions of the php package timitek/getrets-laravel. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download timitek/getrets-laravel
More information about timitek/getrets-laravel
Files in timitek/getrets-laravel
Package getrets-laravel
Short Description A laravel package for the GetRETS API from timitek (http://www.timitek.com). GetRETS is a product / service developed by timitek that makes it possible to quickly build real estate related applications for pulling listing data from several MLS's without having to know anything about RETS or IDX or worry about the pains of mapping and storing listing data from these various sources.
License MIT
Homepage https://github.com/timitek/getrets-laravel
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package getrets-laravel
# getrets-laravel
A laravel package for the GetRETS® API from timitek (http://www.timitek.com).
Based on the PHP SDK found at (https://github.com/timitek/getrets-php-sdk).
GetRETS® is a product / service developed by timitek that makes it possible to quickly build real estate related applications for pulling listing data from several MLS's without having to know anything about RETS or IDX or worry about the pains of mapping and storing listing data from these various sources.
GetRETS® as a service provides a RESTful API endpoint for consuming the data, and although it's not limited to only being used in PHP applications, and users aren't required to use our SDK, we have provided a simple PHP SDK for the API and set of documentation for it's use.
Table of Contents
- Setup
- Compatibility Guide
- Install
- View Example Pages
- Listing
- searchByKeyword
- search
- details
- imageUrl
- RETSListing
- searchByKeyword
- search
- details
- imageUrl
- executeDMQL
- getListingsByDMQL
- Geocoding
- parseGoogleResults
- googleGeocode
- Helper Functions
- Further Reading
Setup
Compatibility Guide
| Laravel Version | Package Tag |
|---|---|
| 5.5.x | 1.1.x |
| 5.4.x | 1.0.x |
Install
To add to an existing Laravel application run the following command.
Note: For Laravel 5.4 and older it is necessary to add the following to the providers section within config/app.php.
Publish the config file to config/getrets.php with the following command.
You may now add the customer key provided to you by timitek.com by either modifying the config/getrets.php or by adding the following to your .env file.
View Example Pages
A sample view have been provided to help you get started.
To test the installation enable the examples, start the project, and browse to /getrets/example.
To enable the sampe code set the GETRETS_ENABLE_EXAMPLE to true in your .env file.
Serve the application on the PHP development server by running;
View the project examples by browsing too
http://localhost:8000/getrets/example
To disable the sampe code set the GETRETS_ENABLE_EXAMPLE to false in your .env file.
Listing
The main controller for working with the listings using the pre-fetched / cached data.
This is the main entry point for retrieving cached listings. Using this entry point will pull listing data that has been pre-fetched from your MLS.
Advantages
- Faster retrieval of data (The retrieval of data does not have to be negotiated and translated with your MLS RETS provider)
- More advanced searching (Since it's pre-fetched data we aren't limited to DMQL queries or other limitations by the RETS provider)
- Works even when the MLS is down for maintenance
Disadvantages
- Data is not 100% live (We are constantly polling the MLS for new data but it could be an hour or so before new listings show up, and we refresh each listing every 24 hours)
searchByKeyword
Search for listings by keyword
A simple search that will retrieve listings by a keyword search.
Parameters
keyword - Keywords to search on
Returns
An array of CondensedListing's
search
Advanced search
A more advanced search that retrieves listings constrained by the optional parameters.
Parameters
keyword - Keywords to search on
extra - (optional) Comma seperated list of extra terms to search for (golf, lake, etc...)
maxPrice - (optional) The maximum listing price
minPrice - (optional) The minimum listing price
beds - (optional) The minimum number of beds to require
baths - (optional) The minimum number of baths to require
includeResidential - (optional) Include residential listings
includeLand - (optional) Include land listings
includeCommercial - (optional) Include commercial listings
Note - If you don't set any of the include parameters, all will be assumed as set.
Returns
An array of CondensedListing's
details
Get details for a specific listing
Retrieves the more specific / non condensed details for a listing. You will typically use the values returned from search functions as the parameters.
Parameters
listingSource - A string representation of the MLS listing source (see FeedsModels.Models.enumListingSource)
listingType - A string representation of the listing type such as residential, land etc.. (see FeedsModels.Models.enumListingType)
listingId - The unique ID for the listing to retrieve the listing for
Returns
A single Listing
imageUrl
Get URL to use for displaying an image
Retrieves an image(s) associated with a specific listing.
Special Note - While the width and height parameters are optional, using them to specify an appropriate image size will increase the speed in which your site renders by lowering the need to download a full size image.
Also, fetching the first photo ($photoId = 0) is a suggested strategy for displaying a thumbnail image.
Parameters
listingSource - A string representation of the MLS listing source (see FeedsModels.Models.enumListingSource)
listingType - A string representation of the listing type such as residential, land etc.. (see FeedsModels.Models.enumListingType)
listingId - The unique ID for the listing to retrieve the listing for
photoId - A zero based index for the photo to retrieve (see the photoCount that is returned in the listing details).
width - The width to be used for resizing the photo
height - The height to be used for resizing the photo
Returns
A URL for the image specified
RETSListing
The main controller for working with the listings using the the live data contained at the MLS using RETS.
This is the main entry point for retrieving live listing data from the MLS via RETS.
Advantages
- The data is queried immediately from the MLS RETS server
Disadvantages
- A bit slower than the cached method. (The data has be translated to DMQL and retreived from a 3rd party server).
- Keyword searches have less "fuzzy logic" applied to them as we are limited to only searching via the available DMQL classes as defined by the MLS.
- If your MLS is down for maintenance, results can not be retrieved.
Special Note - All of the same functions used for fetching data from the cached data (see listing controller functions above) are applicable to this API controller as well, as the exist with the same signatures, only they will go directly to the RETS server.
searchByKeyword
Search for listings by keyword
A simple search that will retrieve listings by a keyword search.
Parameters
keyword - Keywords to search on
Returns
An array of CondensedListing's
search
Advanced search
A more advanced search that retrieves listings constrained by the optional parameters.
Parameters
keyword - Keywords to search on
extra - (optional) Comma seperated list of extra terms to search for (golf, lake, etc...)
maxPrice - (optional) The maximum listing price
minPrice - (optional) The minimum listing price
beds - (optional) The minimum number of beds to require
baths - (optional) The minimum number of baths to require
includeResidential - (optional) Include residential listings
includeLand - (optional) Include land listings
includeCommercial - (optional) Include commercial listings
Note - If you don't set any of the include parameters, all will be assumed as set.
Returns
An array of CondensedListing's
details
Get details for a specific listing
Retrieves the more specific / non condensed details for a listing. You will typically use the values returned from search functions as the parameters.
Parameters
listingSource - A string representation of the MLS listing source (see FeedsModels.Models.enumListingSource)
listingType - A string representation of the listing type such as residential, land etc.. (see FeedsModels.Models.enumListingType)
listingId - The unique ID for the listing to retrieve the listing for
Returns
A single Listing
imageUrl
Get URL to use for displaying an image
Retrieves an image(s) associated with a specific listing.
Special Note - While the width and height parameters are optional, using them to specify an appropriate image size will increase the speed in which your site renders by lowering the need to download a full size image.
Also, fetching the first photo ($photoId = 0) is a suggested strategy for displaying a thumbnail image.
Parameters
listingSource - A string representation of the MLS listing source (see FeedsModels.Models.enumListingSource)
listingType - A string representation of the listing type such as residential, land etc.. (see FeedsModels.Models.enumListingType)
listingId - The unique ID for the listing to retrieve the listing for
photoId - A zero based index for the photo to retrieve (see the photoCount that is returned in the listing details).
width - The width to be used for resizing the photo
height - The height to be used for resizing the photo
Returns
A URL for the image specified
executeDMQL
Return MLS results via a DMQL query
This is a powerful function that will execute raw DMQL against the RETS MLS server and will return the results as a serialized object.
Special Note - These results will not be returned in a translated fashion similiar to the other listing detail searches. These results are in the format as returned from the MLS RETS server. If you wish to retrieve listings in a translated format use getListingsByDMQL.
Parameters
query - The DMQL to be executed against the MLS RETS server
feedName - The name of the feed to run the query against
listingType - A string representation of the listing type such as residential, land etc.. (see FeedsModels.Models.enumListingType)
Returns
An enveloped response with the success or failure of the query, as well as the raw serialized results that were fetched. These serialized results will be different for each feedName and listingType.
getListingsByDMQL
Get translated listings by DMQL query
This is a powerful function that will execute raw DMQL against the RETS MLS server and will return the results as a serialized object. It is similar to executeDMQL, however this function will translate data to be in the same format as returned by other methods that retrieve listing details.
Parameters
query - The DMQL to be executed against the MLS RETS server
feedName - The name of the feed to run the query against
listingType - A string representation of the listing type such as residential, land etc.. (see FeedsModels.Models.enumListingType)
Returns
An enveloped response with the success or failure of the query, as well as the raw serialized results that were fetched.
Geocoding
The main controller for working with addresses
This controller is a planned area of growth to provide more advanced geo-spatial style searching for listing data. For the time being, it is used for parsing keywords into more geocoded data to be used for searching.
If you provide a google geocode key to be associated with your account, you can use these methods.
parseGoogleResults
Translates results returned by Google
This function will parse the results returned from Google's service and translate them into a consistent format more suitable for searching the listing data.
Parameters
googleResults - Results from Google's geocoder.geocode
Returns
Data translated as AddressDetail's.
googleGeocode
Geocode address entered as free-form text
This function will take a keyword and run it through Google's geocoding service and return the translated results.
Parameters
address - A free form text to geocode (The expectation is that this is a possible address)
Returns
Data translated as AddressDetail's.
Helper Functions
The following methods aren't API endpoints but are available in the SDK for assistance with the functionality.
setSortBy / setReverseSort
Used for sorting / ordering the results that are returned
setSortBy
This property is used to set column by which the data is sorted.
setReverseSort
This property is used to set the order (ascending / descending) by which the sortBy column will ordered by. (Default is false meaning ascending)
By default listings will be sorted by the price from low to high. If you want to change the defaults, you can modify these lines.
If you want to sort listings manually within any other portion of the app, you can use the setSortBy and setReverseSort methods as in the following syntax.
Further Reading
More information on the API itself can be found at the Swagger UI (http://getrets.net/swagger/).
