Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/bonitasoft-com:bonitasoft-com-archivedmanualtask-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Bonitasoft Com Archived Manual Task API
version: 1.0.9
license:
name: GPL-v2.0
url: http://www.gnu.org/licenses/gpl-2.0.txt
x-logo:
url: images/ofelia-logo.svg
backgroundColor: '#19465f'
altText: Bonita API
href: /
description: 'Operations tagged ArchivedManualTask across 2 of this provider''s published API definitions: bonita-java-client-openapi.yaml, bonita-java-client.yaml. Each path carries the servers of the definition it was published in.'
servers:
- description: Sample url for a local development server.
url: http://localhost:8080/bonita
security:
- bonita_auth: []
bonita_token: []
- bearer_auth: []
tags:
- description: ArchivedManualTask
name: ArchivedManualTask
x-displayName: ArchivedManualTask
paths:
/API/bpm/archivedManualTask:
get:
description: 'Finds ArchivedManualTasks with pagination params and filters
You can filter on:
* `assigned_id={user_id}`: retrieve only the human tasks assigned to the specified ID. For example, retrieve the human tasks assigned to user with id 2: `/API/bpm/archivedHumanTask?p=0&c=10&f=assigned_id%3d2`
* `state=`: retrieve only the archived user tasks with the specified state. For example, retrieve the skipped tasks: `/API/bpm/archivedHumanTask?p=0&c=10&f=state=skipped`
* `name=`: retrieve only the human tasks with the specified name. For example, retrieve the human tasks with the name "Analyse ProcessInstance": `/API/bpm/archivedHumanTask?p=0&c=10&f=name=Analyse ProcessInstance`
* `displayName=`: retrieve only the archived user tasks with the specified displayName. For example, retrieve the human tasks with the displayName "Analyse ProcessInstance": `/API/bpm/archivedHumanTask?p=0&c=10&f=displayName=Analyse ProcessInstance`'
operationId: searchArchivedManualTasks
parameters:
- description: index of the page to display
example: '0'
explode: true
in: query
name: p
required: true
schema:
default: 0
format: int32
minimum: 0
type: integer
style: form
- description: maximum number of elements to retrieve
example: '10'
explode: true
in: query
name: c
required: true
schema:
default: 20
format: int32
minimum: 1
type: integer
style: form
- description: can filter on attributes with the format f={filter\_name}={filter\_value} with the name/value pair as url encoded string.
example: abc%3d123
explode: true
in: query
name: f
required: false
schema:
items:
maxLength: 250
pattern: ^[A-Za-z0-9%]{0,250}$
type: string
type: array
style: form
- description: can order on attributes
example: myProp%20ASC
explode: true
in: query
name: o
required: false
schema:
maxLength: 250
pattern: ^[A-Za-z0-9%]{0,250}$
type: string
style: form
responses:
'200':
content:
application/json:
schema:
items:
$ref: '#/components/schemas/ArchivedManualTask'
type: array
description: 'Success '
headers:
Content-Range:
description: The total number of matching items
explode: false
schema:
format: int64
type: integer
style: simple
'400':
content:
application/json:
example:
message: Bad request
schema:
$ref: '#/components/schemas/Error'
description: Bad request.
'401':
content:
application/json:
example:
message: Unauthorized
schema:
$ref: '#/components/schemas/Error'
description: Authorization information is missing or invalid.
'403':
content:
application/json:
example:
message: Forbidden, The request contained valid data and was understood by the server, but the server is refusing action.
schema:
$ref: '#/components/schemas/Error'
description: Forbidden, The request contained valid data and was understood by the server, but the server is refusing action.
5XX:
content:
application/json:
example:
message: An unexpected error occured.
schema:
$ref: '#/components/schemas/Error'
description: Unexpected error.
summary: Finds ArchivedManualTasks
tags:
- ArchivedManualTask
x-accepts:
- application/json
servers:
- description: Sample url for a local development server.
url: http://localhost:8080/bonita
/API/bpm/archivedManualTask/{id}:
get:
description: Returns the single ArchivedManualTask for the given ID
operationId: getArchivedManualTaskById
parameters:
- description: ID of the ArchivedManualTask to return
explode: false
in: path
name: id
required: true
schema:
maxLength: 250
pattern: ^[A-Za-z0-9\_\-\.]{0,250}$
type: string
style: simple
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/ArchivedManualTask'
description: 'Success '
'400':
content:
application/json:
example:
message: Bad request
schema:
$ref: '#/components/schemas/Error'
description: Bad request.
'401':
content:
application/json:
example:
message: Unauthorized
schema:
$ref: '#/components/schemas/Error'
description: Authorization information is missing or invalid.
'403':
content:
application/json:
example:
message: Forbidden, The request contained valid data and was understood by the server, but the server is refusing action.
schema:
$ref: '#/components/schemas/Error'
description: Forbidden, The request contained valid data and was understood by the server, but the server is refusing action.
'404':
content:
application/json:
example:
message: Resource not found.
schema:
$ref: '#/components/schemas/Error'
description: The resource for the specified ID was not found.
5XX:
content:
application/json:
example:
message: An unexpected error occured.
schema:
$ref: '#/components/schemas/Error'
description: Unexpected error.
summary: Finds the ArchivedManualTask by ID
tags:
- ArchivedManualTask
x-accepts:
- application/json
servers:
- description: Sample url for a local development server.
url: http://localhost:8080/bonita
components:
schemas:
AbstractArchivedTask:
allOf:
- $ref: '#/components/schemas/AbstractTask'
- description: An Archived task is a task that has been archived
properties:
sourceObjectId:
description: the original id of the task before it was archived
maxLength: 250
pattern: ^[A-Za-z0-9\_\-\.]{0,250}$
type: string
archivedDate:
description: the date ('yyyy-MM-dd HH:mm:ss.SSS') when the current task was assigned for example '2014-10-17 16:05:42.626'
pattern: ^[0-9]{4}-(0[1-9]|1[0-2])-(0[1-9]|[1-2][0-9]|3[0-1]) (2[0-3]|[01][0-9]):[0-5][0-9]:[0-5][0-9]$
type: string
type: object
Error:
additionalProperties: true
example:
exception: exception
explanations:
- explanations
- explanations
message: message
properties:
message:
description: The error message
type: string
exception:
description: The exception type
type: string
explanations:
description: Further details on the error
items:
type: string
type: array
type: object
ArchivedManualTask:
allOf:
- $ref: '#/components/schemas/AbstractArchivedTask'
- description: Use the archivedManualTask resource to access archived process subtasks.
example:
displayDescription: this is a test
executedBySubstitute: 1
processId: 8367255255370238000
parentCaseId: 1
state: completed
rootContainerId: 1
type: MANUAL_TASK
assigned_id: 1
id: 160007
sourceObjectId: 40003
executedBy: 1
caseId: 1
priority: highest
actorId: 1
description: this is a test
name: myTest
reached_state_date: 2014-12-01 17:20:47.200000
rootCaseId: 1
archivedDate: 2014-12-01 17:20:47.217000
displayName: myTest
parentTaskId: 40001
dueDate: 2014-12-17 00:00:00
last_update_date: 2014-12-01 17:20:47.200000
type: object
example:
displayDescription: displayDescription
executedBy: executedBy
archivedDate: archivedDate
rootContainerId: rootContainerId
assigned_date: assigned_date
displayName: displayName
parentTaskId: parentTaskId
dueDate: dueDate
executedBySubstitute: executedBySubstitute
description: description
isTerminal: true
sourceObjectId: sourceObjectId
type: type
priority: priority
actorId: actorId
processId: processId
name: name
reached_state_date: reached_state_date
rootCaseId: rootCaseId
id: id
state: failed
parentCaseId: parentCaseId
last_update_date: last_update_date
assigned_id: assigned_id
AbstractTask:
example:
displayDescription: This is my subtask
executedBySubstitute: 1
processId: 8367255255370238000
parentCaseId: 1
state: ready
rootContainerId: 1
type: MANUAL_TASK
assigned_id: 1
assigned_date: 2014-12-01 17:39:53.784000
id: 40006
executedBy: 1
caseId: 1
priority: above_normal
actorId: 1
description: This is my subtask
name: My subtask
reached_state_date: 2014-12-01 17:39:53.784000
rootCaseId: 1
displayName: My subtask
parentTaskId: 40001
dueDate: 2014-12-25 00:00:00
last_update_date: 2014-12-01 17:39:53.784000
properties:
id:
description: the task id
maxLength: 250
pattern: ^[A-Za-z0-9\_\-\.]{0,250}$
type: string
type:
description: the task type
type: string
name:
description: the task technical name
type: string
displayName:
description: the human readable task name
type: string
description:
description: the task description
type: string
displayDescription:
description: the human readable task description
type: string
state:
$ref: '#/components/schemas/ActivityState'
reached_state_date:
description: the date ('yyyy-MM-dd HH:mm:ss.SSS') when this task reached the current state for example '2014-10-17 16:05:42.626'
pattern: ^[0-9]{4}-(0[1-9]|1[0-2])-(0[1-9]|[1-2][0-9]|3[0-1]) (2[0-3]|[01][0-9]):[0-5][0-9]:[0-5][0-9]$
type: string
last_update_date:
description: the date ('yyyy-MM-dd HH:mm:ss.SSS') when this task was last updated for example '2014-10-17 16:05:42.626)
pattern: ^[0-9]{4}-(0[1-9]|1[0-2])-(0[1-9]|[1-2][0-9]|3[0-1]) (2[0-3]|[01][0-9]):[0-5][0-9]:[0-5][0-9]$
type: string
dueDate:
description: the date ('yyyy-MM-dd HH:mm:ss.SSS') when this task is due for example '2014-10-17 16:05:42.626'
pattern: ^[0-9]{4}-(0[1-9]|1[0-2])-(0[1-9]|[1-2][0-9]|3[0-1]) (2[0-3]|[01][0-9]):[0-5][0-9]:[0-5][0-9]$
type: string
priority:
description: the priority (string) of the current task
type: string
processId:
description: the process definition id of the process instance which define this task
maxLength: 250
pattern: ^[A-Za-z0-9\_\-\.]{0,250}$
type: string
parentCaseId:
description: the immediate containing process instance id (case id)
maxLength: 250
pattern: ^[A-Za-z0-9\_\-\.]{0,250}$
type: string
parentTaskId:
description: the parent Task id
maxLength: 250
pattern: ^[A-Za-z0-9\_\-\.]{0,250}$
type: string
rootCaseId:
description: the top/root process instance id (case id). In case of an "event sub process" `parentCaseId` will the id of the process instance called while `rootCaseId` will be the one from the caller process instance
maxLength: 250
pattern: ^[A-Za-z0-9\_\-\.]{0,250}$
type: string
rootContainerId:
description: same as rootCaseId
maxLength: 250
pattern: ^[A-Za-z0-9\_\-\.]{0,250}$
type: string
executedBy:
description: the id of the user who performed this task. The task has to be a human task otherwise its value will be 0
maxLength: 250
pattern: ^[A-Za-z0-9\_\-\.]{0,250}$
type: string
executedBySubstitute:
description: the id of the user who did actually performed the task when it has been done in the name of someone else. Value is 0 otherwise
type: string
actorId:
description: the id of the actor that can execute this task null otherwise
maxLength: 250
pattern: ^[A-Za-z0-9\_\-\.]{0,250}$
type: string
assigned_id:
description: the user id that this task is assigned to or 0 if it is unassigned
maxLength: 250
pattern: ^[A-Za-z0-9\_\-\.]{0,250}$
type: string
assigned_date:
description: the date ('yyyy-MM-dd HH:mm:ss.SSS') when the current task was assigned for example '2014-10-17 16:05:42.626'
pattern: ^[0-9]{4}-(0[1-9]|1[0-2])-(0[1-9]|[1-2][0-9]|3[0-1]) (2[0-3]|[01][0-9]):[0-5][0-9]:[0-5][0-9]$
type: string
isTerminal:
description: True if the task is the last one in a flow
type: boolean
type: object
ActivityState:
description: the current state of the activity
enum:
- failed
- initializing
- ready
- executing
- completing
- completed
- waiting
- skipped
- cancelled
- aborted
- cancelling subtasks
- aborting activity with boundary
- completing activity with boundary
type: string
securitySchemes:
bonita_auth:
description: 'To call the REST API, you must first log on with a user registered in the Engine database. Please refer to the __[Login API](#operation/login)__ operations section.
'
in: cookie
name: JSESSIONID
type: apiKey
bonita_token:
description: 'To call the REST API, you must first log on with a user registered in the Engine database. Please refer to the __[Login API](#operation/login)__ operations section.
'
in: header
name: X-Bonita-API-Token
type: apiKey
bearer_auth:
description: '
When Bonita runtime is configured for SSO with openID Connect it is possible To call the REST API directly with a Bearer Authorization header containing the access token.
'
scheme: bearer
type: http
x-refined-from:
- bonita-java-client-openapi.yaml
- bonita-java-client.yaml
x-tagGroups:
- name: Authentication
tags:
- Authentication
- PlatformAuthentication
- name: Application
tags:
- Application
- ApplicationMenu
- ApplicationPage
- FormMapping
- name: BDM
tags:
- BDM
- BusinessDataQuery
- Business Data Operations
- BDMAccessControl
- DataRetention
- name: BPM
tags:
- Activity
- ArchivedActivity
- HumanTask
- ManualTask
- Task
- UserTask
- ArchivedHumanTask
- ArchivedManualTask
- ArchivedTask
- ArchivedUserTask
- ActivityVariable
- ArchivedActivityVariable
- ProcessInstanceVariable
- ArchivedProcessInstanceVariable
- ProcessInstanceDocument
- ArchivedProcessInstanceDocument
- Actor
- ActorMember
- ProcessInstance
- ArchivedProcessInstance
- ProcessInstanceInfo
- ProcessInstanceComment
- ArchivedProcessInstanceComment
- Process
- Diagram
- ProcessInfo
- ProcessParameter
- ProcessResolutionProblem
- ProcessSupervisor
- ProcessConnectorDependency
- ConnectorFailure
- ConnectorInstance
- ArchivedConnectorInstance
- FlowNode
- ArchivedFlowNode
- Failure
- ArchivedFailure
- TimerEventTrigger
- Message
- Signal
- Delegation
- name: Custom user info
tags:
- CustomUserDefinition
- CustomUserValue
- CustomUser
- name: Identity
tags:
- ProfessionalContactData
- Group
- Membership
- Role
- User
- Authentication
- name: Platform
tags:
- PlatformAuthentication
- Platform
- License
- Information
- name: Portal
tags:
- Page
- Profile
- ProfileEntry
- ProfileMember
- Theme
- Upload
- name: System
tags:
- I18nlocale
- I18ntranslation
- Log
- Session
- Maintenance
- name: Other
tags:
- RestAPIextensions
- name: Upload
tags:
- FormFileUpload