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

Flowable History API

The History API from Flowable — 17 operation(s) for history.

Flowable History API is one of 64 APIs that Flowable publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include History. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 17 operations across 17 paths, and defines 18 schemas. It is described by OpenAPI 3.0.0, at version v1.

Requests are made against a single base URL, /flowable-rest/service.

17 operations 17 paths 18 schemas 12 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
v1
Base URL
https://your-server/process-api
Authentication
HTTP Basic
Contact
License
Resource Areas
1

Authentication & Security 1

Flowable History API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth).

Paths & Operations 17

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

History 17
GET
/history/historic-activity-instances
List historic activity instances
listHistoricActivityInstances 14 params → 200400
GET
/history/historic-detail
Get historic detail
listHistoricDetails 7 params → 200400
GET
/history/historic-detail/{detailId}/data
Get the binary data for a historic detail variable
getHistoricDetailVariableData 1 param → 200404
GET
/history/historic-task-instances/{taskId}/variables/{variableName}/data
Get the binary data for a historic task instance variable
getHistoricTaskInstanceVariableData 3 params → 200404
GET
/history/historic-variable-instances
List of historic variable instances
listHistoricVariableInstances 9 params body → 200400
GET
/history/historic-variable-instances/{varInstanceId}/data
Get the binary data for a historic task instance variable
getHistoricInstanceVariableData 1 param → 200404
POST
/query/historic-activity-instances
Query for historic activity instances
queryActivityInstances body → 200400
POST
/query/historic-detail
Query for historic details
queryHistoricDetail body → 200400
POST
/query/historic-variable-instances
Query for historic variable instances
queryVariableInstances body → 200400
POST
/query/variable-instances
Query for variable instances
queryVariableInstances body → 200400
GET
/runtime/activity-instances
List activity instances
listActivityInstances 17 params → 200400
GET
/runtime/variable-instances
List of variable instances
listVariableInstances 10 params → 200400
GET
/cmmn-history/historic-task-instances/{taskId}/variables/{variableName}/data
Get the binary data for a historic task instance variable
getHistoricTaskInstanceVariableData 3 params → 200404
GET
/cmmn-history/historic-variable-instances
List of historic variable instances
listHistoricVariableInstances 10 params → 200400
GET
/cmmn-history/historic-variable-instances/{varInstanceId}/data
Get the binary data for a historic task instance variable
getHistoricInstanceVariableData 1 param → 200404
POST
/cmmn-query/historic-variable-instances
Query for historic variable instances
queryVariableInstances 1 param body → 200400
GET
/cmmn-runtime/variable-instances
List of variable instances
listVariableInstances 10 params → 200400

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are HistoricActivityInstanceQueryRequest (18 properties), HistoricActivityInstanceResponse (16 properties), ActivityInstanceResponse (16 properties), HistoricDetailResponse (13 properties). Each schema is shown below with its type and property counts.

HistoricVariableInstanceResponse
object
6 properties
DataResponseHistoricActivityInstanceResponse
object
6 properties
HistoricActivityInstanceQueryRequest
object
18 properties
DataResponseVariableInstanceResponse
object
6 properties
HistoricVariableInstanceQueryRequest
object
12 properties
HistoricActivityInstanceResponse
object
16 properties
ActivityInstanceResponse
object
16 properties
HistoricVariableInstanceQueryRequest_2
object
12 properties
HistoricDetailQueryRequest
object
11 properties
DataResponseHistoricVariableInstanceResponse
object
6 properties
RestVariable
object
5 properties
VariableInstanceQueryRequest
object
12 properties
DataResponseActivityInstanceResponse
object
6 properties
DataResponseHistoricDetailResponse
object
6 properties
HistoricDetailResponse
object
13 properties
QueryVariable
object
4 properties
HistoricVariableInstanceCollectionResource
object
VariableInstanceResponse
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

flowable-history-api-openapi.yml Raw ↑

Other APIs Flowable publishes across the network.

Flowable Access Tokens API
Flowable Accounts API
Flowable Acquire and Execute API
Flowable Batch parts API
Flowable Batches API
Flowable Case Definitions API
Flowable Case Instance Identity Links API
Flowable Case Instance Variables API
Flowable Case Instances API
Flowable Cmmn Engine API
Flowable Contact Filters API
Flowable Content item API
Where this information came from

This is an independent, third-party profile of Flowable History 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.