The developer role is for connecting apps your company builds to Manabu2. It lets learners sign in with their Manabu2 ID and password from your mobile app or internal tool and work with courses, lessons and quizzes there.
- Registering apps and managing their client IDs
- Setting redirect URIs
- Choosing the scopes (the range of actions) each app is allowed
- Issuing and revoking API keys for server-to-server integrations
- Deactivating apps that are no longer used
The developer role is separate from the organization admin role. If you hand someone admin rights just so they can connect an app, they also get the ability to view and edit employee information. The developer role exists so you don't have to do that.
Where to find the management screens
Open My Page, and the card for your organization shows an Applications button. It appears if you have the developer role or are an organization admin.
/{language}/{organization ID}/developer/apps. Your organization ID is part of the URL whenever you have a management screen open.
How it fits together
Register the app
Decide its name, client ID, scopes and redirect URIs.
Implement sign-in
Send users to the Manabu2 sign-in screen, then exchange the code that comes back for a token.
Call the API
Use the access token you received to fetch courses and lessons.
Articles in this guide
Technical specifications
This guide explains what to set up and why. Technical details such as the list of endpoints, request and response formats, and error codes are in the API documentation.
