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 Objects API

The Objects API from Flume Health — 5 operation(s) for objects.

Flume Health Objects 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 Objects. 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 10 operations across 5 paths, and defines 15 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/.

10 operations 5 paths 15 schemas 1 DELETE4 GET2 PATCH3 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 Objects API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2Implicit) using the implicit flow, exposing 3 scopes.

Paths & Operations 10

Across 5 paths, the API surfaces 10 operations — 1 DELETE, 4 GET, 2 PATCH, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Objects 10
GET
/api/v1/objects
List Objects
listObjects 6 params → 200400500default
POST
/api/v1/objects
Create Object
createObject 1 param body → 201400500default
GET
/api/v1/objects/{id}
Get Object
getObject 2 params → 200400404500default
DELETE
/api/v1/objects/{id}
Delete Object
deleteObject 2 params → 200500default
PATCH
/api/v1/objects/{id}
Update Object
updateObject 2 params body → 200400404500default
GET
/api/v1/objects/{objId}/instances
List Instances
listInstances 8 params → 200400500default
POST
/api/v1/objects/{objId}/instances
Create Instance
createInstance 2 params body → 201400500default
GET
/api/v1/objects/{objId}/instances/{id}
Get Instance
getInstance 3 params → 200400404500default
PATCH
/api/v1/objects/{objId}/instances/{id}
Update Instance
updateInstance 3 params body → 200400404500default
POST
/api/v1/objects/{objId}/instances:bulk
Create Bulk Instances
createBulkInstances 2 params body → 201400500default

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are objectinstance.ReadModel (7 properties), objectinstance.UpdateModel (5 properties), objectinstance.WriteModel (5 properties), object.ReadModel (4 properties). Each schema is shown below with its type and property counts.

objectinstance.ObjectSummary
object
2 properties
objectinstance.ReadModel
object
7 properties 4 required
endpoint.DataType
string
objectinstance.CustomValue
object
2 properties
objectinstance.BulkWriteModel
object
1 property
object.UpdateModel
object
2 properties
object.CanonicalColumn
object
2 properties 2 required
objectinstance.CustomValuesByConnection
object
objectinstance.WriteModel
object
5 properties 4 required
objectinstance.UpdateModel
object
5 properties
responses.ErrorResponse
object
3 properties
object.ReadModel
object
4 properties 2 required
object.ListResponse
object
2 properties
objectinstance.ListResponse
object
2 properties
object.WriteModel
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

flume-health-objects-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 Discovery 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
Where this information came from

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