Skip to main content


Only available in EnglishUS πŸ‡ΊπŸ‡Έ

NeighborhoodIntel provides detailed insight into the location of any U.S. address. The report is designed for flexibility, enabling agents to share it via a link, save it as a PDF, or print a hard copy. It contains information based on our API-generated neighborhood data for different categories, such as Climate, Demographics, POIs, Schools, etc.

Screenshot of NeighborhoodIntel Screenshot of NeighborhoodIntel

Single Sign-On (SSO)​

NeighborhoodIntel has the ability to do SSO so you can easily provide your customers with access to any report. We support both OpenID Connect (OIDC) and Security Assertion Markup Language (SAML) SSO.

Security Assertion Markup Language (SAML) SSO​

To use SAML, you will need to provide us with your metadata XML file. After receiving this file, we can then agree on an ID for our Service Provider in your system and one for your Identity Provider in ours. Lastly, we will provide you with a Service Provider metadata file that you'll use.

OpenID Connect (OIDC) SSO​

To use OIDC, we will need an id, a 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, is the issuer and the well-known configuration is located at You can find an example of the OpenID configuration here.

In addition to the credentials and endpoints, we will need to map these attributes:

  • email
  • first name
  • last name
  • MLS name (if applicable)
  • unique user ID (if applicable)

Lastly, you will need a redirect URL for successful signins:

Note: We currently only support passing credentials through the POST request body for token fetching in OIDC, we do not support sending the credentials through the Authorization header. This is an AWS cognito limitation.