Clarifymedical Auth API

The Auth API from Clarifymedical — 1 operation(s) for auth.

Operations 1

GET /auth/cli Get CLI sign-in settings #

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/clarifymedical:clarifymedical-auth-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

clarifymedical-auth-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Clarify Auth API
  description: The Clarify API OpenAPI documentation
  version: '0.1'
  contact: {}
servers:
- url: https://api.clarify.ai/v1
security:
- apiKey: []
- bearer: []
tags:
- name: Auth
paths:
  /auth/cli:
    get:
      description: Returns the OAuth 2.0 device flow settings a command-line client uses to sign a user in. The response is plain JSON, not a JSON:API document, and the endpoint needs no authentication.
      operationId: getCliAuthConfig
      parameters: []
      responses:
        '200':
          description: The device flow settings.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CliAuthConfigResponseDto'
              example:
                client_id: client_01HXYZACMEEXAMPLE0000000000
                device_authorization_endpoint: https://api.workos.com/user_management/authorize/device
                token_endpoint: https://api.workos.com/user_management/authenticate
      security: []
      summary: Get CLI sign-in settings
      tags:
      - Auth
components:
  schemas:
    CliAuthConfigResponseDto:
      type: object
      properties:
        client_id:
          type: string
          description: The WorkOS client ID the CLI sends with its device authorization and token requests.
        device_authorization_endpoint:
          type: string
          format: uri
          description: The URL that starts the OAuth 2.0 device authorization flow and returns a user code.
        token_endpoint:
          type: string
          format: uri
          description: The URL that exchanges a device code or refresh token for an access token.
      required:
      - client_id
      - device_authorization_endpoint
      - token_endpoint
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: Authorization
      description: 'API key authentication. Send your key in the Authorization header as: `api-key <your-api-key>`.'
    bearer:
      type: http
      scheme: bearer
      description: 'User access token authentication. Every endpoint accepts it, and endpoints that act as a person accept only it. Send a WorkOS access token in the Authorization header as: `Bearer <token>`.'