Documentschanges-in-the-pisignage-login-api
Changes in the PiSignage login API
Logging in through the API now needs a second step when an OTP is involved
Server release 3.5.0 added a security update that allows access only from authorised locations.
If MFA is disabled, an OTP is emailed to the registered address when you log in from a new location. The OTP is not required for later login requests from that same location.
When the login API changes
The login flow below applies in two cases:
- You are accessing PiSignage from a new location
- MFA is enabled in the account
Login steps
- Send a POST request to the session endpoint with
email,passwordandgetTokenin the request body. The response is401 Unauthorisedand an OTP is sent to the registered email. - Send a POST request to the same endpoint with
email,password,getTokenand the OTP you received ascode. The response is200 OKwith the login token.
/api/session
(email, password, getToken)
(email, password, getToken, code : <received-otp-code>)
Use the token for the other API calls. API details has more on the API and API is not working helps if requests fail.
If an OTP keeps you from logging in, see Signup and Login or write to support@pisignage.com.