Overview
The Jenzabar One integration provides Room Reservations with read-only access to academic terms, course sections, class meeting schedules, and room assignments. This allows imported classes to block room availability and helps prevent conflicts between academic classes and event reservations.
This article explains what your institution must confirm, configure, and provide before Concept3D can connect to your Jenzabar One environment and validate the integration.
Room Reservations does not write changes back to Jenzabar One. Jenzabar remains the source of truth for your academic schedule.
Confirm Jenzabar One API Access
Before beginning implementation, confirm that your institution:
-
Uses J1 Web
-
Has licensed and enabled the Jenzabar One API
-
Can provide read-only API access to academic terms, course sections, and section meeting schedules
-
Can provide a dedicated service account or integration user that is not tied to an individual staff member
Your institution may also use the Jenzabar Unity Platform to expose this information. Tell Concept3D if Unity is part of your current integration architecture so the connection approach can be reviewed during implementation.
Required Participants
Implementation typically requires these participants from your institution and Concept3D:
-
A Room Reservations Platform Admin or Facilities Manager
-
A Jenzabar One administrator
-
A Jenzabar One API or application administrator who can create integration credentials and grant read access
-
A network or security administrator who can update firewall rules or other network controls
-
A Concept3D Partner Success Manager
Confirm Your Hosting and Network Configuration
Tell Concept3D whether your Jenzabar One environment is:
-
Hosted on your institution’s infrastructure
-
Hosted in Jenzabar Cloud
Provide the following:
-
J1 Web URL
-
API base URL. The API base URL is commonly the J1 Web URL followed by
/api, but your Jenzabar administrator should confirm the correct address for your environment.
Also identify any network controls that affect external API connections, including:
-
IP allowlisting
-
Firewall rules
-
VPN requirements
-
Other authentication or access policies
If your environment restricts access by IP address, allowlist the appropriate Concept3D integration IP address.
| Environment | IP address to allowlist |
|---|---|
| QA or testing | 23.20.165.255 |
| Production | 54.204.165.208 |
Allowlist only the environment being configured. If both QA and production connections will be tested, allowlist both addresses.
Create a Dedicated Integration Account
Steps:
-
Create a dedicated service account or integration user for the Room Reservations integration. Do not use an account belonging to an individual employee.
-
Grant the account read-only access to the Jenzabar One data required by the integration. The account should not be able to create, update, or delete records in Jenzabar One.
Your Jenzabar administrator should also confirm which authentication method your J1 API uses. Depending on your environment, this may include:
-
A username and password exchanged for a bearer token
-
An API client ID and client secret
-
Another authentication method supported by your Jenzabar One configuration
If your connection uses tokens, provide the following:
-
Token endpoint
-
Token lifetime
-
Process used to refresh or renew access
Required Data Access
The integration account must be able to read the information Room Reservations needs to create accurate class reservations.
Academic Terms
-
Year and term identifiers
-
Term names or titles
-
Term start and end dates
-
Information needed to distinguish current, upcoming, historical, and inactive terms
Course Sections
-
A stable section identifier used to update the same class during future imports
-
Subject, course number, section number, and title
-
Section start and end dates
-
Section status, including cancelled or inactive classes
-
Instructor and instructional-method information, when available
Section Meeting Schedules
-
A stable meeting identifier when a section has more than one meeting pattern
-
Meeting start and end dates
-
Meeting days and times
-
Campus, building, and room information
-
Stable room identifiers that can be mapped to Room Reservations spaces
Grant read-only access only. Room Reservations does not create, update, or delete records in Jenzabar One.
Information Your Institution Must Provide
Provide the following information to your Concept3D Partner Success Manager for each Jenzabar One environment being connected:
-
Whether the environment is institution-hosted or hosted in Jenzabar Cloud
-
Confirmation that J1 Web is in use
-
Confirmation that the Jenzabar One API is licensed and enabled
-
Whether your institution uses the Jenzabar Unity Platform
-
J1 Web URL
-
Jenzabar One API base URL
-
Authentication method used by the API
-
Dedicated integration-account username or API client ID, as applicable
-
Password, client secret, or other required credential, as applicable
-
Token endpoint, token lifetime, and refresh process, when applicable
-
Confirmation that the account has read-only access to academic terms, course sections, and section meeting schedules
-
Confirmation that the appropriate Concept3D IP address has been allowlisted, if required
-
Details about any VPN, firewall, or other network requirements
-
A Jenzabar technical contact for connection testing
-
An academic term that can be used for validation
If available, provide access to your J1 API documentation, such as a Swagger page. This helps Concept3D confirm the endpoints and supported filters for your institution’s environment.
Security: Share passwords, client secrets, tokens, and other credentials only through the secure credential-delivery process provided by Concept3D. Do not send credentials by email or include them in a support ticket, shared document, screenshot, or chat message.
Jenzabar Data Readiness
Before connection testing, confirm that the validation term contains representative data:
-
Active course sections
-
Stable section identifiers
-
Section subjects, course numbers, section numbers, and titles
-
Meeting schedules with valid dates, days, and times
-
Room assignments with stable location identifiers
-
A representative mix of section statuses, including a cancelled or inactive section when possible
-
A section with more than one meeting pattern, when your institution uses them
Classes without a usable meeting schedule cannot become reservations. Classes without assigned rooms are identified as unroomed and are not imported until a room is assigned in Jenzabar One.
To keep Room Reservations current after a class is cancelled, Jenzabar One must continue to make the section and its cancellation status available or otherwise provide a reliable way to identify removed classes. Confirm this behavior during connection validation.
Your Institution’s Responsibilities
-
Maintain the Jenzabar One API license and availability
-
Create and maintain the dedicated integration account
-
Grant the required read-only permissions
-
Provide environment and connection details through the approved secure process
-
Configure the network access required for Concept3D to reach the API
-
Provide a representative validation term
-
Correct inaccurate academic schedule data in Jenzabar One
-
Notify Concept3D before rotating credentials, disabling the integration account, changing API access, or making network changes that could interrupt the connection
Concept3D Responsibilities
-
Provide the QA and production IP addresses
-
Review your hosting, authentication, and network requirements
-
Configure your institution’s SIS connection
-
Store connection credentials securely
-
Validate authentication and required data access
-
Make the integration available in Room Reservations
-
Assist with the initial term and room-mapping validation
Validate the Connection
Work with Concept3D to confirm that:
-
Current and upcoming academic terms load successfully
-
Sections can be retrieved for the validation term
-
The complete set of expected classes is available
-
Stable section identifiers are present
-
Meeting days, times, and date ranges are present
-
Room assignments display recognizable campus, building, and room information
-
Stable room identifiers are available for Space Mappings
-
Cancelled or inactive sections can be identified
-
Sections with multiple meeting patterns remain distinguishable
-
Unroomed classes and classes without schedules are clearly identified without preventing other valid classes from loading
-
The connection does not return authentication, authorization, or network errors
After connection validation, continue with Map SIS Rooms to Room Reservations Spaces.
Maintain the Connection
Notify Concept3D before you:
-
Rotate or replace the integration credentials
-
Reset, disable, or replace the integration account
-
Change the account’s data permissions
-
Change your Jenzabar hosting arrangement, API base URL, or authentication method
-
Change firewall, allowlist, VPN, or other network requirements
Advance notice allows Concept3D to update and revalidate the connection without interrupting imports.
Troubleshooting
| Issue | Likely cause | Resolution |
|---|---|---|
| Connection is refused or times out | The API is not externally reachable or required firewall, allowlist, or VPN access is missing | Confirm the API base URL and network requirements; allowlist 23.20.165.255 for QA or 54.204.165.208 for production when required |
| Authentication fails | The authentication method, credentials, or token configuration is incorrect or expired | Confirm the account and token settings with your Jenzabar administrator and provide updated credentials through the approved secure process |
| Terms load but sections do not | The integration account lacks access to course-section data | Review the account’s read-only permissions |
| Sections load without meeting schedules | The integration account lacks access to section schedules or the source sections do not contain meeting information | Review data access and the affected sections in Jenzabar One |
| Expected classes are missing | Sections are outside the selected term, inactive, or missing a usable meeting schedule | Review the term, section status, and meeting information in Jenzabar One |
| Classes appear without usable rooms | Sections have no room assignment or stable room identifier | Assign rooms in Jenzabar One, then run the import again |
| Jenzabar data is incorrect in Room Reservations | The source record is incorrect in Jenzabar One | Correct the class in Jenzabar One and re-sync the term |