Sync rosters via the OneRoster 1.2 REST API

Steps

1. Obtain an OAuth 2.0 Bearer token by posting client credentials to the provider's token endpoint; OneRoster 1.2 mandates OAuth 2.0 Bearer Tokens (RFC 6750) as the only permitted authentication mechanism.
2. Discover available resources by reading the provider's base path — all OneRoster 1.2 REST paths use the prefix /ims/oneroster/rostering/v1p2 for the Rostering service; confirm the exact host and base URL from the provider's documentation.
3. Fetch orgs, courses, classes, users, and enrollments via GET on the respective endpoints (e.g., GET /ims/oneroster/rostering/v1p2/enrollments); use limit and offset query parameters for pagination.
4. For delta sync, apply the filter parameter dateLastModified>'{lastSyncTimestamp}' to retrieve only records changed since the previous run; the provider must support this filter per the spec's conformance requirements.
5. Filter on status=active to exclude soft-deleted records; records with status=tobedeleted should trigger deletion in your local system.
6. Write received records to your local data store, matching on sourcedId as the stable identifier; upsert on sourcedId to handle both creates and updates in a single pass.