wiseed

The platform

Integrations

Wise Ed talks to the systems a school already runs: its accounting program, its learning platform, its web forms and automations, its bank. Every way in goes through the same doors and rules as the office’s own screens, and personal data leaves only as far as the school allows.

  • Writes go through the modules, never around them
  • The school decides which personal data may leave
  • Health, support and accommodation records never leave

The public API

For an ERP, a bank connector, a web form or the school’s own scripts: a system with nobody to sign in gets a key. The public API is part of the licence.

The documentation comes with the key.

  • Keys the school makes itself, on the office’s “API keys” screen: named, shown once when made and stored only as a hash, and revoked from the next call.
  • Scopes per key: students, enrolments, programmes, subjects, grades, invoices, payments and CRM contacts, each to read or, where it makes sense, to write.
  • Limits per key: an expiry date, an allow-list of addresses and ranges, a limit to some campuses, and a rate limit — 120 calls a minute unless the school sets it otherwise.
  • A call log. Every call is a row the school can read, with the key that made it, and every write is in the module’s own history as “API:” and the key’s name.
  • Writes go through the modules. A student, an enrolment, a payment or a CRM contact is saved by the same code the office uses, with the same checks. A payment from accounting is matched to its invoice the way a bank statement line is.
  • Grades can be written too, onto exam records, appended and never overwritten, with a dry run that answers exactly what the real call would.
  • Verify, do not refuse — for a program. Where the office would be asked, the API answers with the same questions and saves nothing; the same call, confirmed with a reason, saves.
  • “What changed since” for every list, deletions included, so another system stays in step without reading everything again.

Zapier

For the office’s own automations: a new application into a spreadsheet, a decided request into a team chat.

  • The clerk connects as herself, with OAuth 2. The connection carries her school and her rights, re-read on every call: a clerk who loses the applications screen stops receiving applications by Zap the same minute. She can cut the connection in one click.
  • Nine events: a new application, an application’s status changed, a new enrolment, a new request, a request decided, a new grade, a diploma issued, a new CRM contact, a new invoice — each with optional filters.
  • Actions: create an application, create or update a CRM contact, add a note to a student, send a message to a student. Searches: find a student, an application, a programme or a CRM contact.
  • Available on request. Wise Ed on Zapier is a private integration for now; a school asks us for the invitation.

Webhooks

  • The same events, to the school’s own receiver — Make, n8n, Power Automate or its own server — typed in on the office’s Integrations screen.
  • Every delivery is signed with HMAC-SHA256 over a timestamp and the body, with a secret only the school holds, shown once when it is made.
  • Delivered, or tried again for most of a day; a receiver that keeps failing is paused with a note saying why. Every delivery is listed, can be opened and sent again.
  • Nothing from the past is replayed. A receiver gets what happens after it was set up.
  • Only https addresses on the internet. An address inside the school’s or our network is refused.

What may leave Wise Ed

One screen decides which personal data goes out by Zapier and webhooks, for every receiver at once.

  • Contact details and invoice lines go by default; home address, birth data and the national ID and tax numbers do not, and neither do a request’s answers, until the school switches them on.
  • Switching the national ID on is asked first, naming the data protection rules. The school decides, and the log says who.
  • A switch that is off removes the fields, rather than sending them empty, so a good e-mail address in the receiving system is never overwritten with nothing.
  • Never, and not a setting: health, support, accommodation and disciplinary records, passwords and keys. The code that builds what is sent does not read those tables at all.

The other connections

Moodle and LTI 1.3

Moodle courses and enrolments from Wise Ed, and Wise Ed inside a course in Moodle, Canvas, Brightspace or Blackboard. Grades coming back are mapped by a person.

Accounting (ERP)

Under Finance: a period’s invoices, lines, payments and open balances with the school’s accounts and cost centres, in the format its program reads.

Microsoft sign-in

Students sign in with the school’s Microsoft account where it uses one; parents with any Microsoft account whose address Microsoft confirms.

Text messages

Through a generic HTTP gateway, Twilio or Infobip, with a monthly cap and quiet hours. Off until the school switches it on; see messages.

Bank statements

Statements in camt.053 matched to invoices by the reference, an invoice number in the text, then amount and name. Payouts of aid as a SEPA payment file.

E-invoices

An invoice as an e-invoice in the country’s format — in Slovenia, e-SLOG 2.0 — downloaded as XML. Other countries’ formats are built per country.

Questions about integrations

Does the public API cost extra?

No. The public API is part of the licence. The school makes its own keys; the documentation comes with the key.

Can our accounting program send payments back?

Yes, through the API or as a file through the import. A payment is matched to its invoice the way a bank statement line is, and one already recorded is left alone.

Who can see what a Zap does?

Every call through a connection is the connecting person’s, logged under her name. The Integrations screen lists who connected, since when, and how many Zaps listen.

Is Wise Ed in Zapier’s public directory?

Not yet. It is available on request as a private integration; ask us for the invitation.

Can a key be limited to one campus?

Yes. A key limited to some campuses reads and writes the students of those campuses only, and a student outside them does not exist for that key.

See Wise Ed on your own school

Book an online presentation. We will walk through how your student office works today and show you the same job in Wise Ed — with your programmes, not a demonstration dataset.