API Connect - Resident Portal Employee FAQ

API Connect - Resident Portal Employee FAQ

  1. What is API Connect - Resident Portal?
    • API Connect - Resident Portal is a gateway for 3rd party vendor partners to access FullCount's resident information displayed on Resident Portal
      • Our partners will be able to pull resident account balances and transaction history
      • Partners will not be able to push online ordering or reservation information
  2. We offer Resident Portal, why don’t our communities use that?
    • These partnered vendors offer their own resident engagement portals that display a wide variety of information that our resident portal does not display (examples being weather, community specific news, calendars and more)
    •  Many of FullCount’s customers are currently using vendors that provide these resident engagement portals
  3. Is API Connect – Resident Portal safe and secure?
    • The FullCount Development team created a set of application programming interfaces (APIs) which allow validated vendors to request information from FullCount
    • In order to have access to FullCount’s APIs, the vendors worked with FullCount’s Development team to set up the proper permissions to pull data from FullCount. The FullCount development team has also validated that the information in these 3rd party application is displayed correctly.
    • The data vendors can pull is restricted and must be authorized by the community the data is coming from
  4. What are the requirements for communities to use API Connect – Resident Portal?
    • Communities must be centrally hosted
      • If a community is remotely hosted, they will need to migrate to our cloud hosted solution
    • Communities will need to have FullCount’s resident portal licensed before being able to purchase API Connect – Resident Portal
  5. How much does API Connect – Resident Portal cost?
    • For all pricing information please contact FullCount’s Sales department for further information
  6. What are the steps for FullCount Support and Implementation staff?
    • Once the work order for API Connect – Resident Portal is completed, a Redmine task will need to be created
      • There is a Template in Redmine, API Connect and/or SSO Resident Portal Integration, for this integration process that should be used
      • This will give the Data Import team a signal to begin the integration process for API Connect – Resident Portal and the community that purchased it
    • If a community has purchased API Connect – Resident Portal and does not currently have a Resident Portal Instance set up, Resident Portal will need to be set up.
  7. Does this change how other FullCount applications work?
    • When a community is integrated with API Connect – Resident Portal there will be changes to how FullCount’s Backoffice application works
      • During the integration process the Data Import team may work with support/implementation on loading customer email addresses for the community into the Backoffice
      • A new message will appear when entering new customers/residents into the Backoffice application after the integration is complete
      • When adding new residents into the Backoffice application an email address will now be required
  8. Why do we need our customer emails?
    • 3rd party vendors use email as a way to establish a mapping between residents in their system and residents in FullCount. This allows the correct balance and transaction information to be displayed in the 3rd party vendor’s system.
  9. If a community is having issues related to the 3rd party vendor partner, then the community needs to contact that 3rd party vendor’s support.

                      
Current Integration Matrix:

3RD Party Resident Engagement Platform

API Connect – Resident Portal

FC Resident Portal SSO

Notes

Icon (Formerly Caremerge)

Ready

Ready

 

Sentrics (fka Connected Living)

Evaluating

Evaluating

 

Cubigo

 

Ready

 

K4 Connect

Ready

Ready

 

Touchtown

Ready

Ready

 

Viibrant (Senior Portal)

Ready

In Progress

 

Wellzesta

 

Ready

 

Exolet

 

In Progress

 

 


    • Related Articles

    • API Connect - Resident Portal Customer FAQ

      API Connect - Resident Portal Customer FAQ What is API Connect - Resident Portal? API Connect - Resident Portal is FullCount's read-only API suite for sharing real-time meal and charge account balances and transactions. The data included is identical ...

    • API Connect - Resident Portal Implementation

      Assumptions: 3rd party vendor has been validated. Implementation steps: Signed contract/agreement from the mutual customer(s). Contract/agreement provides license and permission to share customer data with the 3rd party. Identify and populate 3rd ...

    • API Connect/Customer Portal SSO Email Template

      API Connect/Customer Portal SSO Email Template Email Template: Subject: <Community Name> - FullCount <> <Partner> integration Body: Hi <Community Contact>/<Partner> team, We have enabled the <API Connect AND/OR Single-Sign-On> integration between ...

    • New Resident Portal Setup & Communication

      The creation of our new Resident Portal is to be completed by the Implementer/Support representative assigned to the task. This process no longer requres an additional task or scheduled deliverables from our development team. Below are the steps ...

    • Resident Portal Email Registration Process

      Intent: This document should only be used for defining the process and programatic approach used to implent an email registration process for known users. This article aims to outline the business logic decisions that were made, why, and how they ...