Ocean Health Systems Sessions API

Endpoint for creating a new user session or signing out.

Operations 3

GET /sessions Gets details about the current user, as identified by the session / security… #
POST /sessions Sign in the user using basic authentication. #
DELETE /sessions Sign out the user of the session #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/ocean-health-systems-sessions-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

ocean-health-systems-sessions-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  description: REST API for the Clinical Knowledge Manager.
  version: 1.6.0
  title: CKM REST Sessions API
  contact:
    name: CKM Support
    url: https://oceanehr.atlassian.net/servicedesk/customer/portal/15
    email: ckm@oceaninformatics.com
servers:
- url: /ckm/rest/v1
tags:
- name: Sessions
  description: Endpoint for creating a new user session or signing out.
paths:
  /sessions:
    get:
      tags:
      - Sessions
      summary: Gets details about the current user, as identified by the session / security…
      description: ''
      operationId: getCurrentUser
      security:
      - basicAuth: []
      - sessionid: []
      responses:
        '200':
          description: Successful retrieval of the main data of the user of the API.
          content:
            application/xml:
              schema:
                $ref: '#/components/schemas/User'
            application/json:
              schema:
                $ref: '#/components/schemas/User'
        '401':
          description: The supplied session is not valid or has already expired.
    post:
      tags:
      - Sessions
      summary: Sign in the user using basic authentication.
      description: ''
      operationId: signIn
      security:
      - basicAuth: []
      responses:
        '200':
          description: Successful sign-in. Session is returned as JSESSIONID cookie.
        '401':
          description: Could not authenticate the user due to incorrect details in the Authorization header.
    delete:
      tags:
      - Sessions
      summary: Sign out the user of the session
      description: ''
      operationId: signOut
      security:
      - sessionid: []
      responses:
        '204':
          description: Successful sign-out.
        '401':
          description: The supplied session is not valid or has already expired.
components:
  schemas:
    User:
      type: object
      properties:
        username:
          type: string
        sessionId:
          type: string
        roles:
          type: array
          uniqueItems: true
          items:
            type: string
        roleTypes:
          type: array
          uniqueItems: true
          items:
            type: string
        name:
          type: string
      xml:
        name: user
      description: Essential information about the user, including the session.
  securitySchemes:
    sessionid:
      description: Once the session id is known, it can be used for authentication until expired. The provided session id is used (and validated) on making an actual request.
      type: apiKey
      name: JSESSIONID
      in: header
    basicAuth:
      type: http
      scheme: basic
      description: Basic authentification using the CKM username and password. The provided credentials are used (and validated) on making an actual request.
externalDocs:
  description: Find out more about openEHR and the Clinical Knowledge Manager (CKM)
  url: http://www.openehr.org