Veracross integration details

Finalsite's integration with Veracross utilizes Veracross's REST API. An hourly sync updates data in Finalsite based on changes in Veracross data. The integration is one-way, from Veracross to Finalsite. Changes made to data in Finalsite do not update Veracross.

This article explains how a Veracross integration works with the Finalsite platform and has been updated to reflect the new 2025 Veracross API guidelines, including changes to data structure and integration processes.

In this Article

• Data Mapping
• Constituent Data
  • Can we get admissions data from Veracross?
• Relationships
• Class and Roster Data
• Athletics Data
  • Teams
  • Events
• Authentication

Data Mapping

This document details the default mapping of the data from Veracross when it’s brought into Finalsite. Please note that this is very flexible, so specific modifications can usually be handled during your deployment process.

Constituent Data

Finalsite can target the Veracross constituent endpoints to facilitate feeds for:

• Faculty
• Students
• Parents
• Alumni

Can we get admissions data from Veracross?

Not at this time, the integration will not support admissions data.

Relationships

The integration will also set relationships between users. You can specify which relationship types you would like it to set, but it is typically Student-Parent relationship types that are set by default. Also by default, we will respect the parent_portal_access flag in Veracross and use that value to determine if the relationship should enable "Portal Access" in Finalsite. This means that a parent would be able to see information about the relative when logged into Finalsite. This can be customized per your request if you choose not to respect that flag in Finalsite for some reason.

Class and Roster Data

Classes and Rosters can be created based on Veracross data. Schools can populate academic class data automatically via integration with Veracross that can then be used in Finalsite's Chat feature to create chat rooms. Veracross groups can also be used to target bulk emails.

Athletics Data

Finalsite offers an Athletics integration with Veracross, which pulls data into Finalsite’s Athletics Manager module.  The specific datapoints and default mappings are detailed in this document.

Teams

• Teams created in Veracross will be pulled into Finalsite as teams in Athletics Manager.
• After the initial creation of the team in Finalsite, the team’s properties will not update.
• Some data from Veracross does not correlate exactly with data in Athletics Manager, requiring independent edits in Finalsite.
• Once a team’s information is created in the initial setup in Finalsite, any changes made there will stay and won’t be overwritten by future syncs.
• Admins should ensure default seasons, levels, and sports are set appropriately for all teams to ensure smooth team creation.
• The teams synchronization can optionally populate coaches in Finalsite if coaches are populated via a constituent feed.
• The Description field is used to “match” teams, so it should remain consistent year-to-year.
  
  • If the Description value changes, contact Finalsite support to update the corresponding ImportID.
• Team rosters can be populated based on data from Veracross. In order for this feature to work, you MUST be using the Finalsite-Veracross constituent integration.

Events

• By default, the sync will pull 6 months forward and 2 months back for athletics events. This can be adjusted to fit specific needs.
• Events will be created and updated in Finalsite every hour to ensure prompt updates for cancellations and other status changes.
• Events in Finalsite must be associated with a specific team. Events in Veracross not tied to a team will not be imported.
• The sync will not delete events. Marking the event as “Cancelled” is recommended to reflect the status change in Finalsite. Ensure events are only published in Veracross after confirmation and finalization to minimize corrections. 
• Veracross allows creation of single events spanning multiple days, but these are presented as unique events in the data. They will be created as individual instances in Finalsite. It is recommended to create multi-day events as unique individual events in Veracross for better results when synced to Finalsite.
• For additional information on how this is handled in Athletics Manager, check out the article, "Managing Event Status in Athletics Manager", especially on the difference between Canceling and Deleting events.

Authentication

We offer an option that will allow your users to log into Finalsite via Veracross. This is a redirect authentication that will send users in roles set to use Veracross Authentication to Veracross to log in, and then redirect back to Finalsite.

To use this option, you will need to configure an OAuth application in Veracross (detailed steps can be provided at time of deployment). We will also need to enable staggered login in Finalsite. “Staggered,” meaning that the username and password fields are on separate screens rather than having both fields displayed together and submitted with a single “log in” button.