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

Flume Health Context Discovery API

The Context Discovery API from Flume Health — 17 operation(s) for context discovery.

Flume Health Context Discovery API is one of 20 APIs that Flume Health publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 23 operations across 17 paths, and defines 31 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://console.flumehealth.com/, http://console.flumehealth.com/.

23 operations 17 paths 31 schemas 1 DELETE8 GET1 PATCH13 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://console.flumehealth.com/
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Flume Health Context Discovery API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2Implicit) using the implicit flow, exposing 3 scopes.

Paths & Operations 23

Across 17 paths, the API surfaces 23 operations — 1 DELETE, 8 GET, 1 PATCH, 13 POST. Each is listed below with its method, path, parameters, and response codes.

Context Discovery 23
GET
/api/v1/context/discovery/approvers
List Discovery Approvers
listDiscoveryApprovers 5 params → 200403500default
POST
/api/v1/context/discovery/approvers
Create Discovery Approver
createDiscoveryApprover 1 param body → 201400403500default
GET
/api/v1/context/discovery/approvers/{id}
Get Discovery Approver
getDiscoveryApprover 2 params → 200403404500default
POST
/api/v1/context/discovery/approvers/{id}:revoke
Revoke Discovery Approver
revokeDiscoveryApprover 2 params body → 200400403404500default
GET
/api/v1/context/discovery/connections
List Discovery Connections
listDiscoveryConnections 6 params → 200500default
POST
/api/v1/context/discovery/connections
Create Discovery Connection
createDiscoveryConnection 1 param body → 201400403409500default
GET
/api/v1/context/discovery/connections/{id}
Get Discovery Connection
getDiscoveryConnection 2 params → 200404500default
DELETE
/api/v1/context/discovery/connections/{id}
Delete Discovery Connection
deleteDiscoveryConnection 2 params → 204403404500default
PATCH
/api/v1/context/discovery/connections/{id}
Update Discovery Connection
updateDiscoveryConnection 2 params body → 200400403404409500default
POST
/api/v1/context/discovery/connections/{id}:test
Test Discovery Connection
testDiscoveryConnection 2 params → 200404500default
GET
/api/v1/context/discovery/extractions
List Extractions
listDiscoveryExtractions 6 params → 200500default
POST
/api/v1/context/discovery/extractions
Execute Extraction
executeDiscoveryExtraction 1 param body → 201400403422500default
GET
/api/v1/context/discovery/extractions/{id}
Get Extraction
getDiscoveryExtraction 2 params → 200404500default
GET
/api/v1/context/discovery/sessions
List Discovery Sessions
listDiscoverySessions 6 params → 200403500default
POST
/api/v1/context/discovery/sessions
Request Discovery Session
createDiscoverySession 1 param body → 201400500default
GET
/api/v1/context/discovery/sessions/{id}
Get Discovery Session
getDiscoverySession 2 params → 200404500default
POST
/api/v1/context/discovery/sessions/{id}/launches
Record Subscription Session Launch
launchDiscoverySession 2 params body → 201400404500default
POST
/api/v1/context/discovery/sessions/{id}:approve
Approve Discovery Session
approveDiscoverySession 2 params body → 200400404500default
POST
/api/v1/context/discovery/sessions/{id}:cancel
Cancel Discovery Session
cancelDiscoverySession 2 params body → 200400404500default
POST
/api/v1/context/discovery/sessions/{id}:deny
Deny Discovery Session
denyDiscoverySession 2 params body → 200400404500default
POST
/api/v1/context/discovery/sessions/{id}:extend
Extend Discovery Session
extendDiscoverySession 2 params body → 200400404500default
POST
/api/v1/context/discovery/sessions/{id}:revoke
Revoke Discovery Session
revokeDiscoverySession 2 params body → 200400404500default
POST
/api/v1/context/discovery/sessions:grant
Grant Discovery Session (approver-only)
grantDiscoverySession 1 param body → 201400403500default

Schemas 31

The contract defines 31 schemas that model the data the API accepts and returns. The most detailed are discovery.SessionReadModel (19 properties), discovery.ExtractionResultModel (17 properties), discovery.ExtractionReadModel (15 properties), discovery.ConnectionReadModel (14 properties). Each schema is shown below with its type and property counts.

discovery.ExtractionStatus
string
discovery.SessionCancelRequest
object
1 property
discovery.ApproverCreateRequest
object
4 properties 1 required
discovery.ConnectionType
string
discovery.SessionLaunchRequest
object
Record of a single AI CLI tool launch under a subscriptionaccess session.
3 properties
discovery.ConnectionTestResult
object
3 properties
discovery.ExtractionResultModel
object
17 properties
discovery.ApproverRevokeRequest
object
1 property
discovery.SessionExtendRequest
object
2 properties 2 required
discovery.SessionStatus
string
discovery.ExtractionListResponse
object
2 properties
discovery.SessionGrantReadModel
object
2 properties
discovery.ExtractionCreateRequest
object
5 properties 3 required
discovery.ApproverListResponse
object
2 properties
discovery.SessionDenyRequest
object
1 property 1 required
discovery.SessionLaunchResponse
object
A recorded AI CLI tool launch under a subscriptionaccess session.
6 properties
discovery.ApproverReadModel
object
13 properties
discovery.ConnectionPatchModel
object
9 properties
discovery.GrantType
string
discovery.ConnectionWriteModel
object
9 properties 3 required
discovery.ExtractionReadModel
object
15 properties
discovery.SessionGrantRequest
object
Approver creates a pre-approved PAM session for another user.
5 properties 3 required
discovery.SessionListResponse
object
2 properties
discovery.SessionRevokeRequest
object
1 property
discovery.ConnectionReadModel
object
14 properties
responses.ErrorResponse
object
3 properties
discovery.ConnectionListResponse
object
2 properties
discovery.SessionApproveRequest
object
1 property
discovery.SessionCreateRequest
object
Request to create a PAM session for database access or approver delegation.
7 properties 2 required
discovery.SessionReadModel
object
PAM session granting time-limited access to database connections.
19 properties
discovery.ExtractionType
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

flume-health-context-discovery-api-openapi.yml Raw ↑

Other APIs Flume Health publishes across the network.

Flume Context MCP Server
Flume Health Account Contracts API
Flume Health Accounts API
Flume Health Automap Jobs API
Flume Health Connections API
Flume Health Context Graph API
Flume Health Context Knowledge API
Flume Health Endpoint Maps API
Flume Health Endpoints API
Flume Health Flags API
Flume Health Jobs v2 API
Flume Health Objects API
Where this information came from

This is an independent, third-party profile of Flume Health Context Discovery 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.