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

  1. Call POST /api/login on your BioStar 2 server with a JSON body of the form {"User": {"login_id": "...", "password": "..."}}
  2. On a successful response, read the bs-session-id value from the response headers rather than the body
  3. 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
  4. Use standard HTTP verbs (GET/POST/PUT/DELETE) against BioStar 2's JSON REST resources such as /users for user creation and management
  5. Re-authenticate via /api/login again once the session expires or calls start returning auth errors

Known gotchas

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?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans