Noolingo

OAuth integration guide

OAuth lets a third-party application call Noolingo's existing REST API within permissions you approve, without obtaining your account API key. It does not depend on a ChatGPT plugin or directory verification.

Authorize an application

Start connecting from the application, sign in on Noolingo, then check the registered application name, your account and every requested permission. Permanent deletion receives a specific warning. Allow to return to the application or cancel instead.

Revoke at any time under Connected apps. Grants last at most 30 days. Revocation stops future access but does not delete saved notes or recall third-party copies. Trust the application and review its privacy policy before consenting.

Developer integration

Public clients are registered by a maintainer. Contact [email protected] with your application name, HTTPS callback URIs and required scopes. Production rejects unregistered clients; dynamic registration and wildcard callbacks are unsupported.

Use authorization code + PKCE S256, with resource https://api.noolingo.com/api. Scopes are notes:read, notes:create, notes:update, notes:delete and profile:read. Request only what you need. Reading notes does not require profile access, which includes email and phone.

GET https://api.noolingo.com/oauth/authorize
  ?response_type=code
  &client_id=YOUR_REGISTERED_CLIENT_ID
  &redirect_uri=YOUR_EXACT_REGISTERED_REDIRECT_URI
  &resource=https%3A%2F%2Fapi.noolingo.com%2Fapi
  &scope=notes%3Aread%20notes%3Acreate
  &state=YOUR_RANDOM_CSRF_STATE
  &code_challenge=BASE64URL_SHA256_OF_VERIFIER
  &code_challenge_method=S256

Store the random state and 43–128 character code_verifier on the client. Validate state and iss on callback before exchanging the code. Never log these credentials. Example client values do not represent an active production registration.

POST application/x-www-form-urlencoded requests to the token endpoint. Codes expire after five minutes and are single-use. Access tokens last one hour. Refresh tokens rotate: serialize refresh requests and retain the new credentials. Replaying a consumed refresh token revokes the grant. Never expose credentials in URLs.

See API documentation for parameters, scope mappings, idempotent creation and errors. A 403 indicates insufficient permission; a 401 requires renewed user authorization when the grant is invalid or revoked. Do not ask users to paste API keys as a fallback.