IO Reports
IO Reports is a dynamic ecosystem of reports designed to give you a full view of lifestyle and market trends. Featuring two reports — Neighborhood Lifestyle Report and Neighborhood Market Report — IO Reports enables you to provide clients and prospects with a comprehensive view of a community’s character and real estate market dynamics.
While IO Reports are available for the Neighborhood Lifestyle Report report in the U.S. and Canada, at this time Neighborhood Market Report is only available in the U.S.
These reports are packed with top-tier insights to give you a better understanding of any neighborhood and, in the US, a clear view of local real estate conditions, including real-time data on active listings, median pricing, days on market, and other key metrics.
The reports also support branding and agent customization, including color schemes, logos, headshots, links, and biographies to align the report experience with the look and feel of your online presence and to highlight your local expertise.
Implementation of IO Reports
IO Reports via API
IO Reports are supported via API-based implementation. The IO Reports API allows brokerages, MLSs, real estate platforms, and adjacent industries to trigger personalized Neighborhood Lifestyle Report or Market Trends Reports from any system automatically.
Whether embedded in an existing lead form, email campaign, CRM workflow, or internal dashboard, the API makes it easy to integrate Local Logic’s high-value insights into your user journey.
Implementation Requirements
In order to implement IO Reports via API, you will need developer resources who can prepare and send the request(s) necessary to get an IO Report URL when needed. For example, this could be on form submission or as part of CRM campaigns to email buyer or seller leads, or when generating a flyer in order to embed a QR code link.
The two types of authorization flows supported are via Bearer Token, or leveraging custom JWTs. For more information, please check out the details here.
Single Sign-On (SSO) Flow
IO Reports can be seamlessly integrated with Single Sign-On (SSO), making it easy to provide your agents with secure access to any report. We support both OpenID Connect (OIDC) and Security Assertion Markup Language (SAML) SSO for flexible and secure authentication. The Service Provider initiated sign-in flow is the only one supported.
Only the Service Provider initiated sign-in flow is supported at this time. If at login, errors related to RelayState occur, you may be using the Identity Provider initiated sign-in flow, which is unsupported.
Implementation Requirements
In order to implement IO Reports via Single Sign On within your own platform or dashboard, you will need to
- support an SP-initiated OIDC or SAML SSO flow so that Local Logic's IO Reports application can initiate authentication with your identity provider
- build a tile or link inside your application that directs signed-in users to a link provided by the Local Logic team
This flow requires having a system where an IO Report tile or link could be added for logged in users, and it requires that all configuration match between your identity provider and Local Logic for the SSO to function. Local Logic's IO Reports does not support IdP-initiated SSO.
The link to trigger IO Reports access via a hyperlink or tile will be of the following format: https://neighborhoodintel.locallogic.co/sso/<ORG>
OpenID Connect (OIDC) SSO
To use OIDC, we will need a Client ID, a Client Secret and an Issuer URL. If your issuer URL is not the same URL that hosts your well-known configuration, you will need to provide us with endpoints for authorization, JWKs, token and user info. For example, if Google Workspace is your identity provider, https://accounts.google.com is the issuer and the well-known configuration is located at https://accounts.google.com/.well-known/openid-configuration.
In addition to the credentials and endpoints, we will work to map these attributes (at minimum):
- email (required)
- first name
- last name
Lastly, you will need a redirect URL for successful signins: https://reports-sso-prod.auth.us-east-1.amazoncognito.com/oauth2/idpresponse
Security Assertion Markup Language (SAML) SSO
To use SAML, you will need to provide us with your metadata XML file. In addition, you will need to configure the following Service Provider details based on Local Logic's specifics:
- Entity ID (
urn:amazon:cognito:sp:us-east-1_4cyxyA0TL) - ACS (Assertion Consumer Service) URL (
https://reports-sso-prod.auth.us-east-1.amazoncognito.com/saml2/idpresponse)
In addition to the credentials and endpoints, we will work to map these attributes (at minimum):
- email (required)
- first name
- last name
Frequently asked questions
What are IO Reports?
IO Reports are branded, shareable neighborhood reports that give clients and prospects a full picture of a community's lifestyle and real estate market. They come in two types (below), and are branded to both the brokerage and the individual agent — colors, logos, headshots, links, and bios.
What's the difference between the two IO Reports?
There are two report types. The Neighborhood Lifestyle Report describes a community's character and lifestyle — Location Scores, nearby amenities, and what it's like to live there — and is available across the US and Canada. The Neighborhood Market Report adds local real estate market data such as active listings, median pricing, and days on market, and is available in the US only. Many customers use the two together for a combined lifestyle-plus-market picture.
Is the Neighborhood Market Report available in Canada?
The Neighborhood Lifestyle Report is available in both the United States and Canada; the Neighborhood Market Report is currently available in the United States only.
How can IO Reports be integrated?
IO Reports can be generated two ways: via the IO Reports API (trigger a personalized report URL from a lead form, email campaign, CRM workflow, or internal dashboard), or via Single Sign-On so agents reach reports directly from your platform. SSO supports OpenID Connect (OIDC) and SAML.
Which SSO flows are supported?
IO Reports supports Service Provider (SP)-initiated SSO only, via OIDC or SAML. Identity Provider (IdP)-initiated SSO is not supported; a RelayState error at login usually indicates an IdP-initiated flow was attempted.