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:

  1. You are accessing PiSignage from a new location
  2. MFA is enabled in the account

Login steps

  1. Send a POST request to the session endpoint with email, password and getToken in the request body. The response is 401 Unauthorised and an OTP is sent to the registered email.
  2. Send a POST request to the same endpoint with email, password, getToken and the OTP you received as code. The response is 200 OK with 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.