Build with Motaware
Motaware for Developers lets your website or app sign people in with their Motaware Account. Over time it will also let your app use Motaware apps such as Calendar and Drive on a person's behalf, with their permission.
Available now
Sign in with Motaware
Motaware Auth is a standard OpenID Connect provider. Any OpenID Connect library can use it with the authorization code flow and PKCE. Your app can ask for these scopes:
| Scope | What your app gets |
|---|---|
openid | Sign-in, and a stable user id (sub) |
email | The person's email address, and whether it is verified |
profile | Name and profile photo |
offline_access | A refresh token, so your app can stay signed in |
The first time someone signs in to your app, Motaware asks for their consent. They can remove your app's access at any time.
Discovery document: https://auth.motaware.com/.well-known/openid-configuration
The Developer API
https://developerapi.motaware.com answers GET /v1/me (profile) and GET /v1/me/plan (Motaware plan).
Call it with an access token from Sign in with Motaware, or with an API key. See the API reference.
API keys
Keys act on your own Motaware account, for scripts and automation. A key can never reach anyone else's data. See API keys.
Coming soon
- Motaware app APIs at
developerapi.motaware.com: versioned APIs for Calendar, Contacts, Tasks, Notes, Drive and Docs. Your app calls them with a user's consent, or with your own API key. - App review: apps that want access to app data (calendar, files…) go through a short review by Motaware. Sign-in scopes need no review.
Get started
- Open the console, sign in with your Motaware Account and accept the developer terms.
- Create a project, then a client for your app.
- Follow the quickstart, or the guide for your app type: web (server), browser (SPA), desktop & mobile.