Bonitasoft Application API
Manage applications. This enables you to build a consistent functional applicative environment for users to interact with business processes and business data from one place.
Manage applications. This enables you to build a consistent functional applicative environment for users to interact with business processes and business data from one place.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
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.curl "https://apis.io/api/v1/apis/bonitasoft-com:bonitasoft-com-application-api"
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
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: 3.2.0
info:
title: Bonitasoft Com Application 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 Application 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: Manage applications. This enables you to build a consistent functional applicative environment for users to interact with business processes and business data from one place.
name: Application
x-displayName: Application
paths:
/API/living/application:
get:
description: 'Finds living applications with pagination params and filters
- can order on `id`,`creationDate`, `createdBy`, `profileId`, `token`, `displayName`, `updatedBy`, `lastUpdateDate`, `version`, `link`
- can search on `token`, `displayName`, `version`, `link`
- can filter on `token`, `displayName`, `version`, `link`, `profileId`, `creationDate`, `createdBy`, `updatedBy` , `lastUpdateDate`, `userId`'
operationId: searchApplications
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
- description: can search on attributes
explode: true
in: query
name: s
required: false
schema:
maxLength: 250
pattern: ^[A-Za-z0-9%]{0,250}$
type: string
style: form
responses:
'200':
content:
application/json:
example:
- id: '306'
link: 'true'
creationDate: '1411548289900'
icon: ''
createdBy": '1'
profileId: '2'
description: My application link description
token: myadvapp
state: ACTIVATED
displayName: My app link
updatedBy: '1'
visibility: ALL
editable: 'true'
lastUpdateDate: '1411548289900'
version: '1.0'
- id: '305'
link: 'false'
creationDate: '1411548289900'
icon: ''
createdBy": '1'
profileId: '2'
description: My application description
token: myapp
state: DEACTIVATED
displayName: My app
updatedBy: '1'
visibility: ALL
editable: 'true'
lastUpdateDate: '1411548289900'
version: '1.0'
homePageId: '26'
themeId: '1'
layoutId: '3'
schema:
items:
$ref: '#/components/schemas/Application'
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 living applications
tags:
- Application
x-accepts:
- application/json
post:
deprecated: true
description: 'Create a living application (legacy application or application link).
Warning: as of 9.0.0, creating a living application using this API is deprecated.'
operationId: createApplication
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/CreateApplicationRequest'
description: Partial living application description
required: true
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/Application'
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.
5XX:
content:
application/json:
example:
message: An unexpected error occured.
schema:
$ref: '#/components/schemas/Error'
description: Unexpected error.
summary: Create a living application
tags:
- Application
x-codegen-request-body-name: body
x-content-type: application/json
x-accepts:
- application/json
servers:
- description: Sample url for a local development server.
url: http://localhost:8080/bonita
/API/living/application/{id}:
delete:
description: Delete a single application for the given ID
operationId: deleteApplicationById
parameters:
- description: ID of application to delete
explode: false
in: path
name: id
required: true
schema:
maxLength: 250
pattern: ^[A-Za-z0-9\_\-\.]{0,250}$
type: string
style: simple
responses:
'200':
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: Delete a living application by ID
tags:
- Application
x-accepts:
- application/json
get:
description: Returns a single application for the given ID
operationId: getApplicationById
parameters:
- description: ID of application 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/Application'
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 a living application by ID
tags:
- Application
x-accepts:
- application/json
put:
deprecated: true
description: 'Update a single application for the given ID (legacy application or application link).
Warning: as of 9.0.0, updating a living application using this API is deprecated.'
operationId: updateApplicationById
parameters:
- description: ID of application to return
explode: false
in: path
name: id
required: true
schema:
maxLength: 250
pattern: ^[A-Za-z0-9\_\-\.]{0,250}$
type: string
style: simple
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/ApplicationUpdateRequest'
description: Partial living application description
required: true
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/Application'
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: Update a living application by ID
tags:
- Application
x-content-type: application/json
x-accepts:
- application/json
servers:
- description: Sample url for a local development server.
url: http://localhost:8080/bonita
/services/application/import:
post:
deprecated: true
description: 'Import a single application
Warning: as of 9.0.0, importing a living application using this service is deprecated.'
operationId: importApplication
requestBody:
content:
application/x-www-form-urlencoded:
schema:
$ref: '#/components/schemas/importApplication_request'
responses:
'200':
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: Import a living application
tags:
- Application
x-content-type: application/x-www-form-urlencoded
x-accepts:
- application/json
servers:
- description: Sample url for a local development server.
url: http://localhost:8080/bonita
/portal/applicationsUpload:
post:
deprecated: true
description: 'Upload application
Warning: as of 9.0.0, uploading a living application using the portal is deprecated.'
operationId: uploadApplication
requestBody:
content:
multipart/form-data:
schema:
$ref: '#/components/schemas/FileUploadRequest'
responses:
'200':
content:
text/plain:
schema:
example: tmp_application_data.xml
maxLength: 250
pattern: ^[A-Za-z0-9\_\-\.]{0,250}$
type: string
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.
5XX:
content:
application/json:
example:
message: An unexpected error occured.
schema:
$ref: '#/components/schemas/Error'
description: Unexpected error.
summary: Upload a living application
tags:
- Application
x-content-type: multipart/form-data
x-accepts:
- application/json
- text/plain
servers:
- description: Sample url for a local development server.
url: http://localhost:8080/bonita
/APIv2/service/install:
post:
deprecated: true
description: '!edition
Upload an application configuration file in the `bconf` format.
Warning: as of 9.0.0, uploading an application configuration file using this API is deprecated.'
operationId: uploadApplicationConfiguration
requestBody:
content:
multipart/form-data:
schema:
$ref: '#/components/schemas/uploadApplicationConfiguration_request'
responses:
'200':
content:
text/plain:
schema:
type: string
description: 'Success: the temp file name as present on the server'
'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: Upload an application configuration file
tags:
- Application
x-content-type: multipart/form-data
x-accepts:
- application/json
- text/plain
servers:
- description: Sample url for a local development server.
url: http://localhost:8080/bonita
components:
schemas:
ApplicationLink:
allOf:
- properties:
link:
description: true for an application link
type: boolean
type: object
- $ref: '#/components/schemas/AbstractApplication'
- description: Contains the meta information of a Bonita Living Application Link.
type: object
description: Contains the meta information of a Bonita Living Application Link.
example:
id: '306'
link: 'true'
creationDate: '1411548289900'
icon: ''
createdBy": '1'
profileId: '2'
description: My application link description
token: myadvapp
state: ACTIVATED
displayName: My app link
updatedBy: '1'
visibility: ALL
editable: 'true'
lastUpdateDate: '1411548289900'
version: '1.0'
title: Application Link
CreateApplicationRequest:
example:
link: 'false'
version: '1.0'
profileId: '2'
token: myapp
displayName: My app
description: My application description
properties:
link:
default: false
description: true for an application link, false for a legacy application
type: boolean
description:
description: description of the application
type: string
displayName:
description: display name of the application
type: string
profileId:
description: profile authorized to access this application
type: string
token:
description: token of the application used to build the application URL
type: string
version:
description: version of the application
type: string
type: object
Application:
oneOf:
- $ref: '#/components/schemas/ApplicationLink'
- $ref: '#/components/schemas/LegacyApplication'
x-one-of-name: Application
ApplicationUpdateRequest:
example:
version: '1.0'
profileId: '2'
token: myapp
displayName: My app
description: My application description
themeId: '2'
layoutId: '17'
properties:
description:
description: description of the application
type: string
displayName:
description: display name of the application
type: string
profileId:
description: profile authorized to access this application
type: string
token:
description: token of the application used to build the application URL
type: string
version:
description: version of the application
type: string
themeId:
description: '
theme id for the application
'
type: string
layoutId:
description: '
layout id for the application
'
type: string
type: object
FileUploadRequest:
description: The file to upload
properties:
file:
format: binary
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
importApplication_request:
properties:
applicationsDataUpload:
description: Uploaded file
type: string
importPolicy:
description: Import policy
type: string
AbstractApplication:
properties:
createdBy:
description: Author user ID
maxLength: 250
pattern: ^[A-Za-z0-9\_\-\.]{0,250}$
type: string
creationDate:
description: creation date of the application
type: string
description:
description: description of the application
type: string
displayName:
description: display name of the application
type: string
id:
description: id of the application
maxLength: 250
pattern: ^[A-Za-z0-9\_\-\.]{0,250}$
type: string
lastUpdateDate:
description: last update date of the application
type: string
profileId:
description: profile authorized to access this application
maxLength: 250
pattern: ^[A-Za-z0-9\_\-\.]{0,250}$
type: string
token:
description: token of the application used to build the application URL
type: string
updatedBy:
description: Last updating user ID
type: string
version:
description: version of the application
type: string
state:
description: application state
enum:
- ACTIVATED
- DEACTIVATED
type: string
visibility:
description: visibility of the Application. This value is purely indicative, changing it in the application object won't change the accessibility to the actual application.
enum:
- ALL
- TECHNICAL_USER
- RESTRICTED
type: string
x-enumDescriptions:
ALL: Everyone can use the application
TECHNICAL_USER: Only the technical user can use the application
RESTRICTED: Access to the application is determined by the user profile
editable:
description: Indicates whether the application can be modified
type: boolean
type: object
LegacyApplication:
allOf:
- properties:
link:
description: false for a legacy application
type: boolean
type: object
- $ref: '#/components/schemas/AbstractApplication'
- description: Contains the meta information of a legacy Bonita Living Application.
properties:
homePageId:
description: id of the application page used as the home page
maxLength: 250
pattern: ^[A-Za-z0-9\_\-\.]{0,250}$
type: string
layoutId:
description: id of the layout used by the application
maxLength: 250
pattern: ^[A-Za-z0-9\_\-\.]{0,250}$
type: string
themeId:
description: id of the theme used by the application
maxLength: 250
pattern: ^[A-Za-z0-9\_\-\.]{0,250}$
type: string
type: object
description: Contains the meta information of a legacy Bonita Living Application.
example:
id: '305'
link: 'false'
creationDate: '1411548289900'
icon: ''
createdBy": '1'
profileId: '2'
description: My application description
token: myapp
state: DEACTIVATED
displayName: My app
updatedBy: '1'
visibility: ALL
editable: 'true'
lastUpdateDate: '1411548289900'
version: '1.0'
homePageId: '26'
themeId: '1'
layoutId: '3'
title: Legacy application
uploadApplicationConfiguration_request:
properties:
configuration:
format: binary
type: string
required:
- configuration
type: object
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