How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Commure Auth API

The auth API from Commure — 6 operation(s) for auth.

Commure Auth API is one of 2 APIs that Commure publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Authentication. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, authentication docs, and rate-limit docs.

This API exposes 6 operations across 6 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://api-{tenant-id}.developer.commure.com.

6 operations 6 paths 1 schemas 5 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api-{tenant-id}.developer.commure.com
Authentication
OAuth 2.0, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Commure Auth API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (SMARTonFHIR) using the authorizationCode and clientCredentials flows, exposing 5 scopes. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • SMARTonFHIR — OpenID Connect / SMART App Launch. Supports the authorization code (with PKCE), implicit, hybrid, client credentials and refresh token grants.
  • bearerAuth — Access token issued by the Commure Authentication API, presented as a bearer token (tokens are prefixed "Sec-").

Paths & Operations 6

Across 6 paths, the API surfaces 6 operations — 5 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

auth 6
GET
/auth/authorize
Authorization Endpoint
authorizationEndpoint 10 params → 303400
POST
/auth/token
Token Endpoint
tokenEndpoint body → 200400401
GET
/auth/jwks
Public Keys
publicKeys → 200
GET
/auth/.well-known/openid-configuration
OpenID Connect Provider Metadata
openIDConnectProviderMetadata → 200
GET
/auth/userinfo
UserInfo
userInfo → 200401
GET
/auth/logout
Logout
logout → 200401

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is OperationOutcome (2 properties). Each schema is shown below with its type and property counts.

OperationOutcome
object
HL7 FHIR OperationOutcome - the standard FHIR error envelope returned on 4xx/5xx.
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

commure-auth-api-openapi.yml Raw ↑

Other APIs Commure publishes across the network.

Commure FHIR API
Where this information came from

This is an independent, third-party profile of Commure Auth API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.