Developers & API
The foundation for building on EDUMOVIA. This early overview describes the REST API and webhook model. Programmatic access is offered on Professional and Enterprise plans; contact us to enable it for your organisation.
How access works
EDUMOVIA exposes a REST API over HTTPS. Every request is authenticated with an organisation-scoped API token that you generate from your workspace settings once programmatic access is enabled.
Read access to core records is available on the Professional plan. Read-write access, higher rate limits and webhook delivery are part of the Enterprise plan. This keeps automated integrations aligned with your entitlement.
Authentication
Send your token in the Authorization header as a Bearer credential. Tokens are scoped to a single organisation and can be rotated at any time without downtime.
Never embed a token in client-side code. All API calls should originate from your own server.
Webhooks
Instead of polling, subscribe to events and receive a signed HTTP POST when something changes — for example a new lead, an application status change or a document upload.
Each delivery is signed so your endpoint can verify it genuinely came from EDUMOVIA. Failed deliveries are retried with backoff.
Channels & integrations
The communication channels described on the Integrations page share the same token model. As each channel moves from setup-required to ready, its API surface becomes available under the same authentication.
This is an early foundation document, not a full API reference. Endpoint details are shared under a technical onboarding once access is enabled for your organisation.