How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Losant Authentication and Account API

Authentication and Account resources on the Losant Platform.

Losant Authentication and Account API is one of 6 APIs that Losant publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 2 JSON Schema definitions.

Tagged areas include Authentication and Account. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 2 JSON Schemas.

This API exposes 18 operations across 7 paths, and defines 23 schemas. It is described by OpenAPI 3.2.0, at version 1.29.4.

Requests are made against a single base URL, https://api.losant.com.

18 operations 7 paths 23 schemas 2 DELETE7 GET3 PATCH6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.29.4
Base URL
https://api.losant.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Losant Authentication and Account API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

  • BearerAuth — Losant uses JSON Web Tokens (JWTs) for authentication. Obtain a token via POST /auth/user, POST /auth/device, POST /applications/{applicationId}/tokens, or POS…

Paths & Operations 18

Across 7 paths, the API surfaces 18 operations — 2 DELETE, 7 GET, 3 PATCH, 6 POST. Each is listed below with its method, path, parameters, and response codes.

Authentication and Account 18

Authentication and Account resources on the Losant Platform.

POST
/auth
Authenticates a user via a SAML response.
body → 200400401
GET
/auth
Checks email domain for SSO configuration.
1 param → 200204400
GET
/me
Retrieves Pending Organization Invitations for a User
→ 200400
PATCH
/me
Moves Resources to a New Owner
body → 200400
POST
/me
Accepts or Rejects an Invitation to an Organization
1 param body → 200400404410
GET
/invites
Gets information about an invite
2 params → 200400404410
POST
/invites
Accepts/Rejects an invite
body → 200400404410
GET
/orgs/{orgId}
Returns Notebook Execution Usage by Day for the Time Range Specified for This Organization
3 params → 200400404
PATCH
/orgs/{orgId}
Moves Resources to a New Owner
1 param body → 200400404
DELETE
/orgs/{orgId}
Removes a Member from the Org
4 params → 200400404
POST
/orgs/{orgId}
Invites a Person to an Organization
1 param body → 200400404
GET
/orgs
Returns the Organizations Associated with the Current User
8 params → 200400
POST
/orgs
Create a New Organization
2 params body → 201400
GET
/me/tokens/{apiTokenId}
Retrieves Information on an API Token
1 param → 200400404
PATCH
/me/tokens/{apiTokenId}
Updates Information About an API Token
1 param body → 200400404
DELETE
/me/tokens/{apiTokenId}
Deletes an API Token
1 param → 200400404
GET
/me/tokens
Returns the API Tokens for a User
6 params → 200400
POST
/me/tokens
Create a New API Token for an User
body → 201400

Schemas 23

The contract defines 23 schemas that model the data the API accepts and returns. The most detailed are me (29 properties), org (21 properties), payloadStats (19 properties), apiToken (15 properties). Each schema is shown below with its type and property counts.

orgInviteActionUser
object
Schema for the body of a request to accept or reject an invitation
1 property 1 required
payloadStats
object
Schema for the result of a payload stats request
19 properties
apiTokenPatch
object
Schema for the body of an API Token modification request
3 properties
ssoRequest
object
SSO Request built from the SP and IDP config
2 properties 2 required
org
object
Schema for a single Organization
21 properties
orgInviteResult
object
Schema for the result of accepting/rejecting an invitation
2 properties
orgInviteInfo
object
Schema for information about an invitation
6 properties
orgPost
object
Schema for the body of an Organization creation request
7 properties 1 required
apiToken
object
Schema for a single API Token
15 properties
error
object
Schema for errors returned by the API
2 properties
success
object
Schema for reporting a successful operation
1 property
apiTokenPost
object
Schema for the body of an API Token creation request
5 properties 1 required
orgInvites
array
Schema for an array of pending invitations to an Organization
orgInvitesUser
array
Schema for an array of pending organization invitations for a user
orgInvitePost
object
Schema for the body of a request to send an invitation
5 properties 2 required
me
object
Schema for information about the currently authenticated user
29 properties
samlResponse
object
SAML Response body for login
4 properties 2 required
orgInviteResultUser
object
Schema for the result of accepting/rejecting an invitation
2 properties
notebookMinuteCounts
object
Schema for the result of a notebook minute counts request
3 properties
resourceTransfer
object
Schema for the body of a resource transfer request
5 properties 2 required
authedUser
object
Schema for the successful response when authenticating a User
4 properties 2 required
orgs
object
Schema for a collection of Organizations
9 properties
orgInviteAction
object
Schema for the body of a request to accept or reject an invitation
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

losant-authentication-and-account-api-openapi.yml Raw ↑

Other APIs Losant publishes across the network.

Losant Data and Data Tables API
Losant Edge and Embedded Compute API
Losant Enterprise Instance API
Losant Notebooks API
Losant Workflow Engine API
Where this information came from

This is an independent, third-party profile of Losant Authentication and Account API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.