Authenticate to the Suprema BioStar 2 API and retrieve a session for subsequent user/device calls
domain: bs2api.biostar2.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Call POST /api/login on your BioStar 2 server with a JSON body of the form {"User": {"login_id": "...", "password": "..."}}
On a successful response, read the bs-session-id value from the response headers rather than the body
Attach that value as the bs-session-id header on every subsequent API call (e.g. GET /users to list users, or credential/device endpoints) to authorize the request
Use standard HTTP verbs (GET/POST/PUT/DELETE) against BioStar 2's JSON REST resources such as /users for user creation and management
Re-authenticate via /api/login again once the session expires or calls start returning auth errors
Known gotchas
The session identifier lives in a response header (bs-session-id), not in the JSON body — integrations that only parse the body will miss it
BioStar 2 servers commonly run with self-signed TLS certificates by default, which breaks strict certificate validation in many HTTP clients unless explicitly handled
This is the on-prem/local BioStar 2 server API — Suprema's newer BioStar X cloud platform uses a different G-SDK/API surface, so don't mix documentation between the two products
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?