Authentication

The Telisky API is served from https://mdm-api.telisky.com. The web portal uses it with a session cookie; for your own integrations, authenticate with an API access token (see Access Tokens).

Base URL

https://mdm-api.telisky.com

Resource paths are served from the root - for example /auth/me and /devices.

Authentication methods

Session cookie

A successful sign-in sets an HttpOnly session cookie used by the web portal.

POST /auth/login
Content-Type: application/json

{
  "email": "user@example.com",
  "password": "your-password"
}

Bearer token

For automation, send an API access token in the Authorization header:

curl -H "Authorization: Bearer <token>" \
  https://mdm-api.telisky.com/devices

Create and manage tokens as described in Access Tokens.

Endpoints

Method	Path	Description
POST	/auth/login	Sign in and set a session cookie
POST	/auth/logout	Sign out and clear the session
GET	/auth/me	Get the current user and organization memberships
PATCH	/auth/me/profile	Update the current user’s profile
GET	/auth/sessions	List active sessions
POST	/auth/sessions/:id/revoke	Revoke a session
POST	/auth/password/forgot	Request a password reset

Note

Older /api/auth/* paths are legacy aliases kept for backward compatibility. New integrations should use the /auth/* paths above.

Roles

Access is scoped to your organization and determined by your organization role: Owner, Admin, Member, or Viewer. See Users & Roles.

Rate limiting

Authentication routes are rate limited. When you exceed a limit, the API responds with 429 and standard RateLimit-* headers; retry after the window resets.

Error responses

Status	Meaning
400	Invalid request body or parameters
401	Missing or invalid authentication
403	Authenticated but not authorized
429	Rate limit exceeded

Error bodies include an error string and may include a more specific message.