Skip to content
More support
  • There are no suggestions because the search field is empty.

Tarion Integration (Juniper)

Integrating Tarion with Juniper ensures a seamless process for managing homeowner service requests. This integration allows owners to submit items as usual in their Tarion account, with requests automatically syncing into Juniper’s service request dashboard. This guide outlines the steps to configure and utilize this integration efficiently.

Step-by-Step Instructions:

Step 1: Access to Your Tarion Builder Portal & Create An API User

To configure the integration, we first need access to your Tarion builder portal. This step is essential for establishing the connection between Tarion and Juniper, ensuring a smooth data flow.

You will also need to create an API user. Login to your BuilderLink profile and create a user with EXTERNAL_VB_API_ONLY role. The steps are outlined in VBI Technical Guide v3.3 (screenshots below). This is a new requirement from Tarion as of March 31, 2025.

Once this API user has been created, we will need to receive the login credentials. Do not share this over email. We will give you a call to take this information securely.


Step 2: Homeowner Submission of Service Requests

Once the integration is set up, homeowners will continue submitting their service requests in their Tarion account as they normally would. 

In Juniper, you will need to make sure there is an ‘Other’ asset in each room and a room titled ‘Other’ in case the homeowner’s submission does not match the assets in Juniper. This accounts for any typos or fields left blank in Tarion.

Step 3: Automatic Syncing to Juniper

Submitted Tarion requests will be automatically added to Juniper. This is a one-way sync from Tarion to Juniper as Tarion does not allow for data to be imported into their system. These requests can be found under the ‘Service Request’ tab within each suite and the Service Request Dashboard, making tracking and managing requests more efficient. Tarion requests fall under the ‘Imported’ requests as they are taken from outside of Juniper.

Step 4: Organized Grouping of Tarion Forms

By default, service request items will be grouped within Juniper to help organize Tarion forms efficiently. This grouping streamlines the process of reviewing and addressing homeowner requests.

Form types can also be identified using the service request name. For example, an initial form will have the text ‘TAR’ representing ‘Tarion’ and ‘INT’ representing the initial form type. 

Summary of Key Steps:

  • Gain access to your Tarion builder portal to set up the integration & create an API user.
  • Homeowners submit service requests in their Tarion account as usual.
  • Requests are automatically synced into Juniper’s Service Request Dashboard.
  • Items are grouped within Juniper for easier organization and management.

Conclusion:

By following these steps, you will successfully integrate Tarion with Juniper, creating a more efficient and organized process for managing service requests. If you encounter any issues or need further assistance, please reach out to our support team.


Questions? Email us at juniper-support@spark.re and we’ll be happy to help!