AI Alarm — Mopita Integration

All four flows (Login / Logout / Register / Cancel) use POST forms pointing at the Mopita portal. After redirect, Mopita returns to this page so you can inspect the returned params below.

Resource ID (ci): Environment:

Changes here are local to this page and update all form parameters in real time.

Redirect user to Mopita login portal. After successful login, Mopita redirects back to this page with logincat appended.

After login, Mopita returns to nl with ?logincat=…

Logout POST

Clears Mopita-domain cookies and session. Redirects back to this page after completion.

https://devwww.mopita.com/cp/logout

nl —

cl —

Mopita clears iai_mtisess / iai_mtisess_secure cookies.

Monthly Registration act=reg

Subscribe to the monthly plan. Requires an approved Resource ID (ci). User confirms billing in Mopita portal, then Mopita calls your callback URL.

https://devwww.mopita.com/cp/regist

ci * —

act * reg

nl —

cl —

fl —

Mopita will POST to your callback URL with ci, uid, cs, act=reg.

Cancel Subscription act=rel

Cancels (releases) the monthly plan. Same endpoint as registration but with act=rel.

https://devwww.mopita.com/cp/regist

ci * —

act * rel

nl —

cl —

fl —

Mopita will POST to your callback URL with act=rel.

⚙ DEV — Cookie & URL Parameter Inspector

URL Query Params (returned by Mopita)

none

After login Mopita appends: logincat=…
After register/cancel: logincat=… may also appear.

document.cookie (this domain)

none

Note: Mopita session cookies (iai_mtisess, iai_mtisess_secure) are set on .mopita.com and are NOT accessible from this domain — by design. Only cookies issued by THIS site appear here.

Current Page URL