IDX API with Antonio
Download as PPTX, PDF0 likes330 views
The IDX Broker API has transitioned from a SOAP-based model to a RESTful design, allowing for efficient data manipulation via simple HTTP requests. This API provides over 50 endpoints for accessing MLS data, managing leads, and integrating with various platforms, including customizable features for developers. New documentation and code examples support developers in leveraging the API for diverse applications, enhancing efficiency and functionality.
IDX API with Antonio
- 2. Where we started in Original 17 endpoints SOAP and WSDL XML Schema No Examples Used by few
- 4. Pretty much everything. What changed?
- 5. An API built RESTfully The key principles of REST involve separating the API into logical resources. This means resources are manipulated using HTTP requests where the method (GET, POST, PUT, DELETE) has specific meaning.
- 6. IDX Broker Application Programming Interface Allowed via API Not Allowed via API Called RESTfully Get all the raw MLS data Creation of time saving tools (examples shown later) Query the raw MLS data Get aggregated calls. Data across your clients in one call Submission of properties to a MLS data set Pull featured listings for accounts Pull lead data from client accounts Add/modify non MLS data in accounts Build custom integrations
- 7. An API meant to be used by everyone
- 8. Simple API endpoints Give me all the Leads Give me all the featured listings $url = 'https://api.idxbroker.com/clients/featured'; $url = 'https://api.idxbroker.com/leads/leads';
- 9. Easy to use sample code // headers (required and optional) $headers = array( 'Content-Type: application/x-www-form-urlencoded', // required 'accesskey: abcdefghijklmnopqrstuvwx', 'outputtype: json'); // set up cURL $handle = curl_init(); curl_setopt($handle, CURLOPT_URL, $url); curl_setopt($handle, CURLOPT_HTTPHEADER, $headers); curl_setopt($handle, CURLOPT_RETURNTRANSFER, true); curl_setopt($handle, CURLOPT_SSL_VERIFYHOST, false); curl_setopt($handle, CURLOPT_SSL_VERIFYPEER, false); $response = curl_exec($handle);
- 10. Today's API More than 50 API endpoints New components for Developer Partners only More hourly API calls avaiabale for Developer Partners System and MLS information returned Your choice of JSON or XML New documentation with code examples Versioning Active new development API support, well ok it's mostly me and Nick
- 11. Power Themes and Plugins • Bring Featured Listings into your theme • Create search widgets • Create or display Supplemental listings
- 12. Power CRMs • Poll the API for New Leads • Update Existing Leads • Get and analyze Lead Traffic Data • Create Saved Searches for Leads
- 13. Power Mobile Apps • Import Featured Listings • Add Saved Lead Properties
- 15. Showcasing CRMs
Editor's Notes
- #3: SOAP and WSDL interface. Just the passing of transient XML docs. Most developers didn't develop on the V1 SOAP interface.
- #4: Docs were provided, but minimal
- #5: APIs changed, the need for more data changed, our focus on exposing data in way that was a better fit for us and the consumers of this data
- #6: API settings right in the dashbaord
- #8: API settings right in the dashbaord
- #9: No more SOAP and WSDL. Simple easy endpoints.
- #12: Themes and plugins can make use of many API methods to display or control data in IDX Broker accounts.
- #13: CRMs want more data beyond Lead names and emails.
- #14: Native mobile applications are still apart of today's internet. Even with the ubiquity or mobile responsive sites apps still have their place.