Skip to content

Integrations

Keep what works. Connect the rest.

DOJO's Integration API works in both directions. Send data in from the systems you already have, such as a student information system, a learning platform or your school's own website, and read it back out into your own systems and reports. So you can choose one module at a time without entering the same data twice.

  • Fortnox
  • Visma
  • Ladok & MYH Mina sidor
  • Microsoft 365 / Entra ID
  • Google Workspace
  • itslearning
  • Canvas
  • Learnpoint
  • Your website
  • DOJO

Integrations we deliver

Connected to the systems you already use

On top of the Integration API, we build and deliver integrations with common Swedish systems. They're set up for your school as part of onboarding.

Finance and accounting

  • FortnoxWe deliver

    Salaries and costs booked straight into Fortnox, with no file in between.

  • VismaWe deliver

    Accounting data from DOJO straight into Visma.

Reporting

  • Ladok & MYH Mina sidorWe deliver

    Students and study results to Ladok and MYH's Mina sidor.

Sign-in and calendar

  • Microsoft 365 / Entra IDWe deliver

    Sign in with the school's Microsoft account, with meetings in Outlook and Teams.

  • Google WorkspaceWe deliver

    Sign in with the school's Google account, with meetings in Google Calendar.

Learning platforms

  • itslearningWe deliver

    Courses, students and grades synced with itslearning.

  • CanvasWe deliver

    Courses, students and grades synced with Canvas.

  • LearnpointWe deliverVerified

    Programmes, classes, students and staff read in from the school's Learnpoint. Already done with a school's real data.

Another system?

We build custom integrations with whatever you use: finance, HR, a school portal or something else entirely. Tell us what you have, and we'll take it from there.

Talk to us about integration

Delivered integrations are set up and adapted for each school. Scope and price are part of the quote.

9 datasets in, 8 out

Each dataset belongs to the module that owns the data. Sending data in doesn't require the module, but reading it back does. Synced data is marked with its source, and lists are read page by page, up to 200 rows at a time.

Table of the Integration API datasets, in and out
DatasetEndpointScopeModule
ProgrammesPOST /integration/programsGET /integration/programsprograms:writeprograms:readFoundation
CoursesPOST /integration/coursesGET /integration/coursescourses:writecourses:readFoundation
CohortsPOST /integration/cohortsGET /integration/cohortscohorts:writecohorts:readFoundation
StudentsPOST /integration/studentsGET /integration/studentsstudents:writestudents:readFoundation
TeachersPOST /integration/teachersteachers:writeFoundation
GradesPOST /integration/gradesGET /integration/gradesgrades:writegrades:readLearning
LIA placementsPOST /integration/lia-placementsGET /integration/lia-placementslia:writelia:readCompany & LIA
ApplicationsPOST /integration/applicationsGET /integration/applicationsapplications:writeapplications:readAdmin & Compliance
LeadsPOST /integration/prospectsprospects:writeAdmin & Compliance
Attendance summary per cohortGET /integration/cohorts/{cohortId}/attendance-summaryattendance:readLearning

Built to be safe to integrate with

  • Your own keys

    A superadmin creates the keys and chooses how long they last: 3, 6, or 12 months. Each key belongs to one organisation. The secret is shown once and only stored hashed.

  • Exact permissions

    Each key reaches only the datasets it has scopes for, and the scopes can be changed later. Nothing more, and never as a person.

  • Rotation without downtime

    Replace the secret whenever you like. The old key keeps working for 7 more days, then switches itself off.

  • Safe retries

    Send an Idempotency-Key. The same request twice gives the same answer, and nothing is written twice.

  • Partial success is fine

    One bad row doesn't stop the rest. The response says what happened to every row.

  • Generous limits

    600 requests per minute per key, up to 500 rows per request.

  • Reading is its own permission

    Every dataset has a read scope that is separate from the one that writes. A key that sends applications from your website can never read students back.

  • Identity numbers only when needed

    Personal identity numbers are only included when the key has the separate students:read-sensitive scope, and never on applications.

  • Protected identities are left out

    Students with a protected identity are never included when data is read out, and neither is anything linked to them.

What a request looks like

A simple JSON request with your key. The response tells you what happened to every row.

Request
POST /api/v1/integration/grades
Authorization: Bearer dojo_sk_live_…
Idempotency-Key: 2026-06-14-grades-run-1
Content-Type: application/json

{
  "sourceSystem": "skolportal",
  "items": [
    {
      "externalId": "SIS-G1",
      "studentExternalId": "SIS-1001",
      "courseExternalId": "SIS-K1",
      "grade": "VG",
      "gradedAt": "2026-06-14T00:00:00Z",
      "attemptNumber": 1
    }
  ]
}
Response
{
  "data": {
    "dataset": "grades",
    "processed": 1,
    "created": 1,
    "updated": 0,
    "failed": 0,
    "results": [
      { "externalId": "SIS-G1", "status": "created", "code": null }
    ]
  }
}

We share the API documentation and the OpenAPI specification with your IT department or integration partner. The specification is generated from the code, and a change that would break an existing integration is stopped automatically unless it has been announced.

AI assistants

Ask DOJO through your own AI assistant

Staff can connect the AI assistant they already use, such as Claude, to DOJO through the open MCP standard. They paste in one address and sign in to DOJO. No codes to set up.

Questions staff can ask

  • Which students are below 75 % attendance in the UX cohort?
  • Which LIA placements are missing a supervisor?
  • Which MYH deadlines are coming up?

What the assistant can look up

  • Your school's programmesFoundation
  • An overview of a cohortFoundation
  • Find students by name or student numberFoundation
  • A student's progress: YH credits, grades and attendanceLearning
  • Attendance risks against CSN's 75 % and 70 % limitsLearning
  • LIA placements, for example those missing a supervisorCompany & LIA
  • Upcoming deadlines: MYH registration, form responses and steering group meetingsAdmin & Compliance

The assistant only sees the tools that belong to your school's modules.

How the assistant stays within bounds

  • The same access as the person

    The assistant sees what the signed-in person may see, with the same role and the same programmes. Nothing more.

  • Read only

    The assistant can't change, add or delete anything in DOJO.

  • Never identity numbers

    Personal identity numbers are never given to the assistant, and students with a protected identity are left out entirely.

  • Off until you switch it on

    A superadmin switches on Allow AI assistants for the organisation. Each person then approves their assistant on a page that shows the assistant's name and address.

  • Easy to disconnect

    Anyone can disconnect their assistant under Settings. If the organisation switches the feature off, every connection stops at once.

  • Every question is logged

    The audit log shows who asked, with which assistant, which tool and how many results. Never the answer itself.

Where does the data go?

What the assistant reads in DOJO is sent to the assistant's provider, for example Anthropic, so that it can answer. Your school decides whether AI assistants may be used, and each person approves their own assistant.

Example

Nordic West Academy: applications from the website

Nordic West Academy's website sends applications from its own form to DOJO's admissions. The key lives in a server-side function, not in the browser. The function checks the personal identity number, sends the application with a unique key for safe retries, and the applicant gets their application number right away.

  1. The applicant fills in the form on the school's website

  2. A server-side function checks the details and calls DOJO

  3. The application lands in the admissions flow and the applicant gets a receipt by e-mail

More connections

  • SIE4 to accounting

    Export of salaries and costs for import into Fortnox or Visma.

  • Calendar invites

    Invitations to steering-group meetings that land straight in the calendar.

  • CSV and PDF

    Export lists and reports when you need them outside DOJO.

Planning an integration?

Tell us which systems you have today, and we'll show you which datasets need to go in and out for the modules you're interested in.