Features Archives - EDMISS

EDMISS API Version 2: Built for Humans. Ready for AI.

Ryan Lee — Tue, 21 Jul 2026 02:25:49 +0000

We’re excited to announce the release of EDMISS API Version 2, a major milestone in the evolution of the EDMISS Next Generation Platform.

Built from the ground up, API Version 2 has been designed for a world where systems need to connect faster, workflows need to automate more intelligently, and AI applications need secure, structured, and reliable access to business data.

Whether you’re building integrations, automating business processes, or developing or using AI solutions, API Version 2 provides the foundation to make it happen.

A New Foundation for Connected Systems

API Version 2 is more than a technical upgrade. It is a core platform capability designed to help institutions, partners, and technology teams build smarter connections with EDMISS.

Whether you’re integrating with finance systems, CRM platforms, document management systems, custom applications, or AI-powered assistants, the new API provides a secure and flexible foundation for automation and seamless data exchange.

This is just the beginning. API Version 2 establishes the foundation for future integrations, expanded automation capabilities, and a growing ecosystem of connected solutions around EDMISS.

Security and Governance Designed for Integration

API Version 2 introduces new authentication and governance capabilities that give organisations greater control over how integrations access EDMISS.

The new API introduces dedicated integration users, allowing organisations to separate system access from standard staff access. Each integration user has its own roles and permissions, making it easy to grant only the access required for each integration.

Every API request is performed on behalf of a specific integration user, creating a clear audit trail. Organisations can easily identify whether a change was made by a staff member, a third-party application, a vendor integration, or an AI solution, improving accountability and governance.

Authentication is managed through access tokens issued specifically for dedicated integration users. Each integration, vendor, service, or AI solution can have its own token, allowing access to be managed independently. Administrators can revoke individual tokens at any time without affecting other integrations, providing precise control over API access.

API Version 2 also introduces tenant-level rate limits across both short and long time windows. Daily request monitoring provides visibility into API usage, helping organisations understand adoption, monitor activity, and manage integrations with confidence.

Powerful New API Capabilities

API Version 2 introduces a range of new endpoints and capabilities designed to make integrations simpler, more flexible, and AI-ready. This is just the beginning, and we will continue to expand the API with new capabilities and endpoints over time.

Current highlights include:

Document upload endpoints to automate document collection and storage.
Customisable search endpoints that support API-driven reporting and data retrieval by allowing you to:
- Select only the fields you need, reducing payload size and improving performance.
- Apply custom filters to retrieve precisely the data required.
Custom field support across the API, including filtering and sorting in search endpoints, enabling integrations to work seamlessly with your organisation’s configured data.
Utility endpoints that expose the available fields for each object, including their name, description, and data type, making integrations easier to build and maintain.
Picklist endpoints that return valid values for supported fields, allowing applications and AI solutions to validate and process data more reliably.
Default product values when creating offers. Products can automatically use their configured default pricing and duration, while still allowing integrations to override these values when required.

Interactive API Documentation

API Version 2 includes comprehensive, interactive documentation designed to help developers get up and running quickly.

Developers can explore endpoints, review request parameters, inspect sample requests and responses, understand response structures, and test API calls directly from the browser without needing a separate API client.

For teams using their own development tools, the documentation can also be exported as an OpenAPI specification and imported into popular platforms such as Postman, Insomnia, Swagger, and other OpenAPI-compatible tools. This helps developers and integration partners accelerate development, validate requests, and start building with confidence.

Ready for AI

One of the most exciting aspects of API Version 2 is how well it supports the next generation of AI-powered applications and autonomous agents.

AI solutions require APIs that are secure, well documented, predictable, discoverable, and capable of describing their own data structures. API Version 2 has been designed with these requirements in mind.

With metadata endpoints, picklist values, custom search capabilities, support for custom fields, meaningful validation errors, dedicated integration users, revocable access tokens, and API usage monitoring, the platform provides the context, security, and governance that both AI solutions and integration teams need to operate safely and effectively.

API Version 1 Compatibility

We know many customers and partners rely on API Version 1 for their existing integrations. That’s why API Version 1 will continue to be supported, allowing current integrations to keep running without interruption.

As we move forward, our development efforts will focus on expanding API Version 2 by bringing across existing capabilities and introducing new features designed for modern integrations, automation, and AI-powered solutions.

Customers can use API Version 1 and API Version 2 side by side, making it easy to adopt the new API at their own pace. Each API version has its own usage limits, so organisations should plan their integrations accordingly.

What Comes Next

API Version 2 marks the beginning of a new chapter for integrations, automation, and AI across the EDMISS platform.

Over the coming releases, we will continue expanding the API with new endpoints, additional workflows, and enhanced capabilities that help organisations connect EDMISS with the systems, services, and AI solutions they rely on.

Customer feedback will play an important role in shaping what comes next. Whether you’re looking to automate a specific process, integrate with a third-party platform, or enable new AI-powered experiences, we’d love to hear about your requirements and help prioritise the capabilities that will deliver the greatest value.

As more organisations begin building with API Version 2, we’ll also be sharing practical use cases, implementation examples, and ideas to demonstrate what’s possible and inspire new ways to automate and extend EDMISS.

API Version 2 is currently available on an invitation basis. If you’d like to explore how it can support your organisation, we’d be happy to discuss your integration requirements and enable access.

FAQs

Is API Version 2 replacing API Version 1?

Not yet. API Version 1 will continue to be supported for existing integrations.

Should new integrations use API Version 2?

Yes. Our development efforts are focused on expanding API Version 2, so we recommend using Version 2 for new integrations wherever possible.

Do I need to migrate my existing integrations?

No. Existing integrations can continue using API Version 1. You can adopt API Version 2 whenever you’re ready and migrate at your own pace.

Can we use API Version 1 and API Version 2 at the same time?

Yes. Both versions can be used simultaneously. This allows existing integrations to continue on Version 1 while new integrations are developed using Version 2.

Each API version has its own usage limits. Organisations should consider these limits when designing integrations and automation workflows.

Is there any cost to use API Version 2?

No. If you already have access to API Version 1, you can also use API Version 2 at no additional cost.

Can I build AI solutions with API Version 2?

Yes. API Version 2 has been designed with AI in mind, providing secure access, comprehensive documentation, metadata endpoints, and other capabilities that make it easier to build AI-powered applications and autonomous agents.

All use of the API, including AI-powered solutions, must comply with the EDMISS Customer Terms of Service.

Where can I find the API documentation?

For more information about API Version 2, including how to access the technical API Reference, visit our Support Centre: https://support.equatorit.com/nextgen/published/edmiss/equator-api-v2

How do I get access to API Version 2?

API Version 2 is being rolled out gradually to customers. If you would like early access or have an integration project you are planning, please contact our Support team. We’ll be happy to discuss your requirements and help you get started.

The post EDMISS API Version 2: Built for Humans. Ready for AI. appeared first on EDMISS.

Introducing the EDMISS + Flywire Integration: Smarter Student Payments Made Simple

Ryan Lee — Wed, 24 Sep 2025 02:25:03 +0000

Student payments should be simple and secure. That’s why we’ve partnered with Flywire, a global leader in education payments.

Together, we’re making it easier than ever for institutions to receive, process, and reconcile both international and domestic payments, while giving students and families a smoother, more transparent experience.

Powered by Flywire’s global payment network and 24/7 multilingual support, this integration streamlines the entire payment journey from start to finish

Why This Matters

Schools face real challenges when handling payments:

Unidentified transactions that cause manual reconciliation headaches
Short balances or overpayments due to unexpected fees or errors
Fraud risks when bank details are publicly displayed
Students frustrated by hidden costs, unclear instructions, or lack of support
Delays in receiving funds, especially for international payments

The EDMISS + Flywire integration solves all of this in one seamless solution—helping schools save time, reduce risk, and improve the overall student experience.

Benefits for Your Institution

With the new integration, your school can:

Accept payments in 140+ currencies across 240+ countries and territories
Offer a best price guarantee on local currency transfers
Eliminate short balances and overpayments with pre-filled payment amounts
Automatically link payments to the correct student record
Capture all required student details to avoid unidentified payments
Enhance fraud protection by removing the need to publish bank details

A Better Experience for Students & Families

Students will enjoy:

Flexible, convenient payment options with no hidden costs
Real-time payment tracking via email, SMS, or the Flywire app
24/7 multilingual support (chat, phone, email, and WeChat)
Secure transactions in their local currency with upfront pricing
Peace of mind knowing their payments are safe and transparent.

How It Works

You can offer payments through Flywire in two ways:

Option 1: School-Initiated Payment Requests

Schools create templates with a Flywire bookmark to request payments against offers, enrolments, and invoices.
When sending emails, SMS, or merged documents from EDMISS, a unique and secure payment link (or QR code) is generated with the amount due.
Students click or scan to make their payment via Flywire’s secure portal.
Payments are automatically recorded in EDMISS for fast reconciliation.

Payments can be requested for students, offers, enrolments and invoices.

Option 2: Student-Initiated Payments

Students log in to their EDMISS portal.
Go to the Invoices page and select invoices to pay.
Choose Flywire as the payment option.
Pay via bank transfer, card, or other local methods—with no hidden fees.
Track payments in real time with instant updates from Flywire.
Payments post automatically in EDMISS for easy reconciliation.

Start simplifying payments with EDMISS + Flywire. Contact us today.

The post Introducing the EDMISS + Flywire Integration: Smarter Student Payments Made Simple appeared first on EDMISS.

Introducing Agent Contracts

Ryan Lee — Thu, 28 Aug 2025 23:49:33 +0000

We’re excited to introduce Agent Contracts (available from the August 2025 release). This powerful new feature is designed to help colleges better manage and streamline their relationships with agents.

(more…)

The post Introducing Agent Contracts appeared first on EDMISS.

Introducing Automated Invoice Reminders

Ryan Lee — Tue, 24 Jun 2025 23:33:02 +0000

Let’s face it—chasing overdue invoices is nobody’s idea of a good time. It’s tedious, awkward, and it takes you away from the work that really matters. That’s why we’ve added a new time-saving feature to eBECAS/EDMISS Next Generation: Automated Invoice Reminders.

Get Paid Faster—Without Lifting a Finger

With Automated Invoice Reminders, EDMISS NextGen can now send email or SMS nudges to students (or whoever’s footing the bill) before or after the due date—no manual follow-up required. Just set your reminder rules once and let the system handle the rest.

Whether it’s a polite “your invoice is due soon” or a firmer “you’re overdue,” your reminders go out like clockwork every day.

Here’s Why You’ll Love It

Fully Automated: Daily batch processing means reminders go out while you’re sleeping (or sipping coffee).
Flexible Messaging: Create multiple reminders with different triggers, tones, and timing.
Multi-Channel Delivery: Send reminders via email or SMS, depending on your audience and urgency.
Attach Documents: Include files like invoices directly in the email for added clarity.
Automatic Diary Entries: All messages sent are logged in the Student Diary for complete visibility.
Custom Sender Options: Choose to send emails from an individual user account or a college-wide address—your choice
Track Everything: Stay on top of your reminders with detailed logs that show the status, when each message was sent, whether it was successful, and why it failed if not.
Full Visibility: Preview which invoices will get reminders using your regular invoice search filters.

Smart Rules, Smarter Cash Flow

Setting up reminders is easy—and powerful. You can fine-tune who gets what, and when, using flexible filters such as:

Number of days before or after the due date — schedule early nudges or overdue prompts with precision
Minimum invoice amount — avoid sending reminders for low-value invoices
Payer/Student type — target exactly the right group

Combine these filters to match your collections strategy and create as many reminders as your plan allows. The result? More control, less chasing.

Built-In Efficiency, Designed for You

Whether you’re handling tuition fees, enrolment charges, or any other payments, this feature keeps your cash flow moving and your inbox quieter. Best of all? It’s built into NextGen and works straight from your existing workflows.

No awkward follow-ups. No lost invoices.

The post Introducing Automated Invoice Reminders appeared first on EDMISS.

Introducing Multi-Factor Authentication and Enhanced Password Policies

Ryan Lee — Tue, 23 Jul 2024 00:36:03 +0000

In today’s digital age, security is more important than ever, especially when it comes to managing your sensitive data. That’s why we’re excited to introduce two powerful new features to EDMISS: Multi-Factor Authentication (MFA) and Enhanced Password Policies.

These additions are designed to provide an extra layer of protection for your system data, ensuring that only authorized users have access.

Multi-Factor Authentication

Multi-Factor Authentication (MFA) is a security mechanism that requires users to provide two or more verification factors when they log in. One factor is something the user knows, such as their username and password. Other factors include something the user has such as an authenticator app on a mobile phone or a security code on their email or phone.

By adding additional factors to verify the users’ identity, MFA makes it harder for common threats to succeed.

Why is MFA Important?

Passwords alone are no longer enough to protect against the sophisticated cyber threats we face today. MFA significantly reduces the risk of unauthorized access, even if a password is compromised. By requiring a second form of verification, MFA ensures that the access to your data remains secure.

How Does MFA Work in EDMISS?

Implementing MFA in our Student Management System is straightforward and user-friendly.

Here’s how it works:

Login Attempt: When a user logs in, they will enter their username and password as usual.
Verification Prompt: After entering the correct password, the system will prompt the user for a second form of authentication. This could be a code sent to their email or a code from an Authenticator app installed on their mobile phones.
Access Granted: Once the second form of authentication is successfully completed, the user is granted access to the system.

What MFA Methods are Available?

We understand that convenience and accessibility are crucial when implementing new security measures. That’s why we offer two methods for Multi-Factor Authentication (MFA): Email Verification and an Authenticator App:

Email Verification (available in EDMISS Classic and Next Generation): After users enter their username and password, they will receive a short-lived code sent to their email address. They must enter this code before it expires to complete the authentication process.
When this method is enabled, MFA will be enforced for the entire organization (users cannot opt-out individually).

Authenticator App (only available in EDMISS Next Generation): With this method, after users successfully enter their username and password, users need to get a code from their authentication app of preference and enter it to complete the authentication process.
This is an opt-in method that users need to enable and set up individually.
When enabled, this method takes preference over the email verification method (if enabled).

At this first phase, MFA is not available for the teacher and student portals.

Trusted Devices

To enhance user convenience while maintaining security, when MFA is enabled (email verification) users can mark their devices as “trusted.” This means that once a device is trusted, users can skip the MFA process on that device for a period defined by the system administrator.

Enhanced Password Policies

Alongside Multi-Factor Authentication, we are also introducing enhanced password policies to further safeguard your data.

These policies include:

Minimum Length Requirements: Ensures that all user passwords meet a required length
Password Complexity Requirements: Mandates the use of varied character types in user passwords
Password Expiration: Enforces regular changes to user passwords after a specified period

These policies can now be customized by the system administrator to better align with their organization’s specific needs.

These policies apply to all administrative users and teachers using EDMISS Classic, EDMISS Next Generation and EDMISS Teacher Portal.

Getting Started with MFA and Enhanced Password Policies

Setting up these new security features is easy, follow these links for the details.

If you have started using EDMISS Next Generation (currently in BETA), you can make changes in either system, and they will apply to both.

EDMISS Classic (Desktop version)

EDMISS Next Generation (web version)

Preparing your Users for Multi-Factor Authentication

If you are enforcing MFA (email verification), ensure all your users have a valid email address that they can access during their login process. If they do not have a valid email address or cannot access it during the log in process, they will be unable to complete the authentication process.

Please note that these features are available from version 12.1.0.0.

We’ve started rolling out these features and they will be available to all colleges in the next weeks.

The post Introducing Multi-Factor Authentication and Enhanced Password Policies appeared first on EDMISS.