Portal login, registration and password reset
Use code-backed email/password login, client registration and forgotten-password endpoints.
Proplix Secure API Gateway
Open guide →GuideLog in a client through the API
POST the master token plus valid email/password to /portal_api/login; successful authentication returns a short-lived client session.
Open guide →GuideUse POST for portal login
Other methods are rejected.
Open guide →GuideComplete login email
Use the client contact email.
Open guide →GuideComplete login password
Use the client portal password; do not log it.
Open guide →GuideSet login session expires_in
Optional 60–900 seconds, default 600.
Open guide →GuideResolve failed portal login
Check active contact, password, client account and master profile controls.
Open guide →GuideRegister a client account through the API
POST supported identity/company/contact/password fields to /portal_api/register.
Open guide →GuideUnderstand registration validation
The production model validates required data, email/account conflicts and password/consent conditions exposed by its input flow.
Open guide →GuideUnderstand registration result
Successful registration can create/authenticate the client identity and return session context.
Open guide →GuideRequest a client password reset
POST the client email to /portal_api/forgot_password.
Open guide →GuideUnderstand privacy-safe reset behaviour
Use the returned success/message without exposing whether an unrelated account exists.
Open guide →GuideUnderstand CSRF exclusions
Only server-to-server session, login, registration, forgot-password and Scroll document-upload endpoints are excluded.
Open guide →GuideUnderstand retired client endpoint
The legacy arbitrary client-ID endpoint is retired and instructs integrations to use session/me.
Open guide →GuideUnderstand retired contact endpoint
The legacy arbitrary contact-ID endpoint is retired and instructs integrations to use session/me.
Open guide →