APIs and webhooks in school software: how to connect school management with your website, your app and your accounts
What an API and a webhook are, explained for leadership and IT teams, ten useful integrations for a school or academy and what to demand from your management software's API.
Ena by Edena | 7 min read In almost every school there is someone copying data from one place to another: enquiries from the website form into the admissions program, new students into the learning platform, invoices into the spreadsheet sent to the accountant, absences into a report for leadership. That work exists because programs do not talk to each other. The way to make them talk is called an API, and its partner is the webhook.
This article explains what they are, with examples from a school, a nursery or an academy; ten integrations that really save time; how an integration is built step by step; and what your management software's API should offer before anyone writes the first line of code.
What an API is
An API is a set of operations that one program offers to others: "give me the list of students in Year 2B", "create this enrolment application", "mark this bill as paid". Whoever uses it sends a request with a key that identifies them and receives a response with the data, usually in JSON format.
Three ideas to understand it without technical jargon:
- It does the same as the screens, but from another program. If you can register a student in the management software, your website or system can do it too through the API.
- Each key has permissions. A key created with the manager role reaches exactly what a person with that role can, no more and no less.
- It is documented. A serious API publishes what operations it has, what data each one takes, what it returns and what errors it can give.
What a webhook is
A webhook is the reverse path: instead of your system asking, the management software tells you. When something happens (a new enrolment, a paid invoice, a register with absences), it sends a message to the address you have given, with the details of the change.
Three things make a webhook reliable:
- It is signed, so your system can check the notice really comes from the management software.
- It is retried if your system does not respond, for hours or days, so no events are lost.
- It can be looked up later, in case your system was down and you need to recover what happened.
Ten useful integrations for a school
- Website form to admissions. Each enquiry from the form goes into the admissions CRM with its source, without copying anything by hand.
- Confirmed enrolment to the learning platform. When a student enrols, a webhook notifies your system, which creates their account on whatever learning platform you use.
- Paid invoices to accounting. Each payment reaches your accounting program or accountant with its invoice, as we explain in the article on integrating with your accountant.
- Attendance to a leadership dashboard. Each day's attendance data feeds your own dashboard in whatever analytics tool the school uses.
- Today's absences to the canteen or transport. Who is not in today, to adjust meals or routes.
- Your own app for families. With end-user tokens, your app shows each family their children, their bills and their announcements, and nothing else.
- Calendar and activities on the public website. Events and after-school activities with places available are published automatically on the school's site.
- A consolidated dashboard for a group of schools. If each school has its own account, the group's team can read each one's data with its key and build its own report for the whole network.
- Data for the academic system. Prepare, in the format your academic system needs, data already held in the management software, without retyping it.
- Alerts for staff in their work tool. A new enrolment application or a returned direct debit appears in the channel the team already uses.
You do not need to build them all. Start with the one that forces someone to copy data every week today.
How an integration is built, step by step
- Define the goal. Which data goes from where to where, how often and who needs it.
- Work in a test environment. A sandbox is an empty copy of the school where you can test without touching real data or sending anything to families.
- Create a key with the minimum role. If the integration only reads attendance, it does not need to be able to issue invoices.
- Code the calls and webhooks following the documentation, and handle errors and retries.
- Test with real cases: a student with two families, a returned direct debit, a mid-year withdrawal.
- Go live with a new key for real data, stored on the server.
- Watch the log of requests and webhook deliveries during the first weeks.
What to demand from your management software's API
Before commissioning an integration, check that the provider's API meets these points:
- Public, complete documentation, ideally in OpenAPI format, with what each operation takes and returns.
- Coverage of every module, not just students and families. If something is done on screen and not through the API, sooner or later you will have to copy it by hand.
- Webhooks for important changes, signed and with retries.
- A test environment from which nothing reaches the real world.
- Keys by role, revocable at once and with a limit on active keys.
- Documented request limits, with headers that say how much margin is left.
- Errors with a stable key, so your code can decide what to do in each case.
- Safe retries: being able to repeat a write without it happening twice.
- A request log that shows what happened and when.
- Tokens for third-party apps that act as a specific family without exposing the school's key.
An API like that is also your guarantee of portability: if you ever switch provider, you will be able to take your data out in an orderly way. We explain it in the article on interoperability and portability.
Security and data protection
- The key never goes in the browser or the app. It is stored on the server; the app uses end-user tokens.
- Minimum role for each integration, and a different key for each one, so you can revoke it without affecting the others.
- A processing agreement with the agency or developer working with real data.
- Test data in the sandbox, never copies of real student data.
- Regular review of active keys and of who has access to the developer console.
Coding with AI on the school's API
Coding agents such as Claude Code, Codex or Gemini CLI have changed who can build an integration. If the API has a public reference, the agent reads it, understands which operations exist and writes the code. For it to go well:
- Always work in the sandbox, with test keys.
- Give it the official documentation, do not let it guess field names.
- Review the code before going live, especially anything that writes data.
- Do not give real-data keys to an agent working on your computer.
If what you want is to look up the school's data from your assistant without coding, what you need is an MCP connector. We explain it in what MCP is and what it is for in a school.
Edena's API
- More than 800 operations covering every module: students, families, invoices, payments, attendance, CRM, timetables and the rest. Every screen has its operation.
- 240 event types by webhook, signed with HMAC-SHA256 and retried for about three days if your system does not respond. Events from the last 30 days can be looked up.
- Sandbox: an empty copy of the school with its own keys, from which no emails, family notifications, live VeriFactu submissions or card payments go out.
- Keys by role (administrator or manager, with its subrole), up to 25 active per organisation and revocable at once.
- End-user tokens so your app can act as each family.
- Public OpenAPI reference in Spanish, Catalan and English, errors with a stable key and Idempotency-Key to repeat writes without duplicating them.
- Limits: 300 requests per minute per key and 1,200 across all of the organisation's keys.
- An open-source CLI for people and AI agents, and a 30-day log of every request and every webhook delivery.
Conclusion
A well-built API and webhooks are what stop the school's management software being an island. With them, the website, accounting, the learning platform or your own app receive the data without anyone copying it. Before commissioning an integration, check that your provider's API is documented, covers every module, has a test environment and keys with narrow permissions.
If your school already uses Edena, the console is under Developers in the app menu. If you only need the API for your own software, you can create a developer organisation with a 15-day trial. Discover Edena's developer platform or talk to the team.
Frequently asked questions
What is a school software API?
What is a webhook?
Do I need a development team to use the API?
Is it safe to open the school's data to an API?
What does Edena's API offer?
This content was generated by Ena, Edena's artificial intelligence agent. It may contain errors or inaccuracies and does not constitute legal, tax or professional advice. Edena does not warrant the accuracy, completeness or currency of the information. Consult official sources and, where appropriate, a qualified professional before taking any decision. The cover image is from Unsplash .