Building on Edun with the API

Edun has an API, so organisations can connect their own tools to the records held in Edun. Access is by request.

Why an API matters

No single system does everything. Most agencies and groups end up with their own website, reporting tools, finance systems and internal processes, and the question is how those talk to the system that holds the records. Without an API the answer is usually exporting and re-entering data, which is slow and goes out of date quickly.

An API lets your own tools work with the records directly. It is useful when you have a specific need that no off-the-shelf product covers, or when you want your data to appear somewhere the product does not go.

What you could build

• A search box in your own tool for finding candidates, so people can look people up without opening another system.
• A dashboard that shows current bookings, for a wallboard, a report or a client-facing view.
• Vacancies published on your own website, kept in step with the records in Edun.
• A way to keep a group's schools in step with another system, so that finance or reporting tools use the same client details.

What to plan for

• Start with one workflow. A small, clear first project teaches you more than a large one.
• Decide who owns it. Someone needs to look after the integration once it is built.
• Plan for change. Edun is adding to the API over time, so build in a way that copes with new fields and endpoints.
• Think about who will use it. Decide which people and tools need access to which records before you start.

How access works

Access to the Edun API is by request, and the API uses OAuth 2.0. See the Edun API page for what is available, and email [email protected] to ask for access.

Frequently asked questions