| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Community Apps Dependencies | Show |
| Lines of code | 3231 |
| Technical Name |
do_school_mobile_api |
| License | OPL-1 |
| Website | http://doincredible.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Community Apps Dependencies | Show |
| Lines of code | 3231 |
| Technical Name |
do_school_mobile_api |
| License | OPL-1 |
| Website | http://doincredible.com |
School ERP — Mobile API
Versioned JSON-RPC API powering mobile & PWA clients with the same security as the web UI.
JSON-RPC API
Versioned
Same Security
Mobile / PWA
One backend, one security model, every device
The Mobile API module exposes the School ERP suite to mobile apps and progressive web apps through a clean, versioned JSON-RPC API. Every endpoint runs in the authenticated user's environment, so the exact same access rights and record rules that protect the web UI also protect the API — there is no parallel permission model to build or maintain.
Endpoints live under a stable /api/do/v1 namespace and return lean, mobile-shaped payloads. The module is country-neutral and forms the foundation for parent and student mobile experiences, ready to be wrapped by JWT or OAuth2 whenever stronger authentication is required.
Key Features
Versioned Namespace
All endpoints live under /api/do/v1 for stable, evolvable contracts that protect clients from breaking changes.
Current User Endpoint
/me returns the logged-in user and the students they are allowed to access.
Children Endpoint
/me/children returns the logged-in parent's children for a focused family view.
Paginated Student Listing
/students provides a paginated, rule-scoped student list with limit and offset controls.
Compact Payloads
Lean student payloads (admission number, name, level, section, status) keep mobile apps fast and data-efficient.
Security by Design
Handlers execute in the user environment, inheriting the suite's record rules and UI-level permissions.
See It In Action
How It Works
User Roles
| Role | Access |
|---|---|
| Authenticated user (parent / student) | Calls /me and /me/children for their own and their children's data. |
| Authorized staff | Calls /students; results are automatically scoped by the user's record rules. |
No new security groups are introduced — the API reuses the exact access model already enforced by the School ERP web UI.
Integration
Builds directly on do_school_parent, serving the same student data exposed in the portal over JSON-RPC.
Relies on the suite's record rules for access — there is no separate ACL to maintain.
Designed to be wrapped by an authentication layer (JWT / OAuth2) as a pluggable front door when needed.
Technical Information
Odoo Version: 19.0 (Community)
Models: No new models — JSON-RPC controllers over do.student
Dependencies: do_school_parent
License: LGPL-3
Part of the School Management ERP Suite · Odoo 19 Community · by DO Incredible
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module