CommsHarbor

CommsHarbor Context API

The Context API from CommsHarbor — 1 operation(s) for context.

Documentation GitHub OpenAPI

Operations 1

GET /api/context Resolve which organization and role the current credential is acting as #

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/commsharbor-context-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.

GitHub Google LinkedIn

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

OpenAPI Specification

openapi: 3.2.0
info:
  title: CommsHarbor Context API
  version: 2d690e87
  description: CommsHarbor API. Organization identity is explicit and tenant-scoped.
servers:
- url: https://commsharbor.com
tags:
- name: Context
paths:
  /api/context:
    get:
      operationId: commsharbor_context
      summary: Resolve which organization and role the current credential is acting as
      description: 'Read this before a write when you are not certain which tenant is active. Guessing is how data lands in the wrong organization.

        Returns: { kind, organizationId, userId?, email?, sessionId?, role?, organization?, apiKeyId?, scopes? }'
      security:
      - bearerAuth: []
      parameters:
      - name: X-Organization-Id
        in: header
        required: true
        schema:
          type: string
        description: Which organization to act in. Required with a human session; an API key determines its own and rejects a conflicting value.
      responses:
        '200':
          description: '{ kind, organizationId, userId?, email?, sessionId?, role?, organization?, apiKeyId?, scopes? }'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Identity'
        '401':
          description: No session, no API key, or the credential does not resolve to this organization.
        '403':
          description: The identity is valid but lacks the required role or scope for this operation.
        '404':
          description: The resource does not exist in this organization. Another tenant's ID answers the same 404 — the API never confirms that it exists elsewhere.
      tags:
      - Context
components:
  schemas:
    Identity:
      type: object
      properties:
        kind:
          type: string
          description: How the identity was resolved.
        organizationId:
          type: string
          description: The active organization.
        userId:
          type: string
          description: The person, when a session is in play.
        email:
          type: string
          description: The person's e-mail, on a session.
        sessionId:
          type: string
          description: Session identifier, on a session.
        role:
          type: string
          description: Role inside that organization; sessions only.
        organization:
          type: object
          description: '`{ id, name, slug }` of the active organization; sessions only.'
        apiKeyId:
          type: string
          description: Which key answered, on an API key.
        scopes:
          type: array
          items:
            type: string
          description: Granted scopes; present on an API key, which carries its own narrower set.
      required:
      - kind
      - organizationId
      description: Who the current credential resolves to. Read this before a write when you are not sure which organization is active.
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: Human session or scoped organization API key. Organization identity remains explicit.