1

Endpoint Changes

CourseUnit

New Scopes:

• course_unit_read
• course_unit_write

New Endpoints:

• GET / GETBYID / POST / PUT / PATCH

Credentials

Updated Endpoints:

• GET / GETBYID

Training Agreements

New Scopes:

• training_agreement_read
• training_agreement_write

New Endpoints:

• GET / GETBYID / POST / PUT / PATCH

Event Management

New Scopes:

• event_session_read
• event_session_write
• event_enrolment_read
• event_enrolment_write

New Endpoints Coming

Link to API documentation: https://api-docs.wisenet.co/iae/index.html

2

Offer Unification

The Problem

Enrolments into Unit Offers are restricted to those sitting under specific Course Offers.

This creates unnecessary duplication when the same Unit is delivered across multiple Course Offers. Leading to:

• Multiple unit offers
• Inconsistent capacity tracking
• Complex access for trainers 
• Not reflecting actual delivery

The Approach

• Unit offers will be unified across course offers
• Course enrolments can enrol into any unit offer
• Still supports default unit offers per course offer
• Still supports course offer–specific values cascade
• Minimal process change on roll out required
• API & data warehouse will be affected

3

AI in Cases

Controlled by you

We’ve built the AI integration to be fully opt-in.

You control when it activates, what data it uses, and how it assists.

Nothing runs automatically.

Your account

The AI connection uses your own OpenAI API key.

This means:

• You retain control over your data
• You control your spend
• You have access to usage dashboards.
• You benefit from any cross-context learning if used in other environments.
• No shared models and no shared billing.

AI agnostic

We’ve built our AI layer to be provider-agnostic.

While we currently integrate with OpenAI, the framework supports expansion.

Learn more about using AI in Cases