Veracross Integration
Manage1to1 connects to Veracross to roster students, staff, and guardians automatically, so you don't have to export and upload files by hand. Veracross publishes its roster through its OneRoster API (part of API Plus for Academics), and Manage1to1 reads it directly through the Standard OneRoster provider with a built-in Veracross preset.
To configure this integration in Manage1to1 you need the Manage Settings permission. To create API credentials in Veracross you need access to the Veracross Partner Portal.
What You'll Need From Veracross
Gather these from the Veracross Partner Portal (or from your Veracross administrator) before you start.
| Item | Where it comes from | Example |
|---|---|---|
| School route | Shown for your school in the Partner Portal. It's the short identifier in your Veracross URLs. | myschool |
| Client ID | Created when you add an API client for Manage1to1. | — |
| Client Secret | Shown once when you create the API client — copy it right away. | — |
The two web addresses below use your school route in place of {school route}:
| Field in Manage1to1 | Value |
|---|---|
| Base URL | https://oneroster.veracross.com/{school route}/ims/oneroster/v1p1/ |
| Token URL | https://accounts.veracross.com/{school route}/oneroster/oauth/token |
| OAuth Scope | https://purl.imsglobal.org/spec/or/v1p1/scope/roster-core.readonly |
| OneRoster Version | 1.1 |
When you choose Veracross from the SIS Vendor dropdown in Manage1to1, the OneRoster Version and Scope above are filled in for you. You only paste in the two web addresses and your credentials.
Step 1: Create API Credentials in Veracross
- Sign in to the Veracross Partner Portal.
- Create a new API client for Manage1to1 and grant it roster read access (the
roster-core.readonlyscope shown above). - Copy the Client ID and Client Secret. Keep the secret somewhere safe — Veracross shows it only once.
- Note your school route (shown for your school in the portal).
Step 2: Configure the Integration in Manage1to1
- Go to Settings → Integrations → User Rostering.
- Set the provider to Standard OneRoster and open its configuration.
- From the SIS Vendor dropdown, choose Veracross. This pre-fills the OneRoster Version and Scope.
- Fill in the remaining fields, substituting your school route:
- Base URL:
https://oneroster.veracross.com/{school route}/ims/oneroster/v1p1/ - Token URL:
https://accounts.veracross.com/{school route}/oneroster/oauth/token - Client ID and Client Secret from Step 1.
- Base URL:
- Click Test Connection. A successful test confirms the addresses, credentials, and scope all line up and unlocks Save.
- Save the configuration.
Veracross's OneRoster API is version 1.1. If the OneRoster Version is set to anything else, rostering won't read your buildings correctly — leave it on 1.1 (the Veracross preset sets this for you).
Step 3: Align Buildings
After the connection is saved, use the building preview to match your Veracross schools to Manage1to1 buildings. This makes sure each rostered person lands in the right building. Review the matches before running a full sync.
Step 4: Run the First Sync
Start a user sync from the User Rostering section. Progress is shown live as students and staff are brought in. After the first run completes, Manage1to1 keeps up with enrollment changes on its regular sync schedule.
Troubleshooting
| Message | What it usually means |
|---|---|
| Insufficient scope | The API client in Veracross wasn't granted roster read access, or the Scope field is blank. Re-select the Veracross preset and confirm the client's permissions in the Partner Portal. |
| Endpoint not found | The Base URL or school route is off, or the OneRoster Version isn't 1.1. Double-check the school route in both web addresses. |
| Authentication failed | The Client ID or Secret is wrong, or the Token URL is missing the /oneroster/ segment. Confirm the Token URL is https://accounts.veracross.com/{school route}/oneroster/oauth/token. |