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

The History Case API from Flowable — 6 operation(s) for history case.

Flowable History Case 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 Case. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

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

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

7 operations 6 paths 7 schemas 1 DELETE4 GET2 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 Case API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth).

Paths & Operations 7

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

History Case 7
GET
/cmmn-history/historic-case-instances
List of historic case instances
listHistoricCaseInstances 48 params → 200400
GET
/cmmn-history/historic-case-instances/{caseInstanceId}
Get a historic case instance
getHistoricCaseInstance 1 param → 200404
DELETE
/cmmn-history/historic-case-instances/{caseInstanceId}
Delete a historic case instance
deleteHistoricCaseInstance 1 param → 204404
GET
/cmmn-history/historic-case-instances/{caseInstanceId}/identitylinks
List identity links of a historic case instance
listHistoricCaseInstanceIdentityLinks 1 param → 200404
POST
/cmmn-history/historic-case-instances/{caseInstanceId}/migrate
Migrate historic case instance
migrateHistoricCaseInstance 1 param body → 200404
GET
/cmmn-history/historic-case-instances/{caseInstanceId}/stage-overview
Get a stage overview of historic case instance
getHistoricStageOverview 1 param → 200204404
POST
/cmmn-query/historic-case-instances
Query for historic case instances
queryHistoricCaseInstance body → 200400

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are HistoricCaseInstanceQueryRequest (60 properties), HistoricCaseInstanceResponse (21 properties), HistoricIdentityLinkResponse (7 properties), DataResponseHistoricCaseInstanceResponse (6 properties). Each schema is shown below with its type and property counts.

StageResponse
object
5 properties
HistoricIdentityLinkResponse
object
7 properties
HistoricCaseInstanceQueryRequest
object
60 properties
RestVariable
object
5 properties
DataResponseHistoricCaseInstanceResponse
object
6 properties
HistoricCaseInstanceResponse
object
21 properties
QueryVariable
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

flowable-history-case-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 Case 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.