Bonitasoft Application Menu API
Manage the set of menus in an application. This set of menus enables a user to navigate to the application pages.There are two types of menu item:A top-level item appears in the navigation bar of the application. A top-level item can be clickable, leading to a page, or can be a parent for a menu of clickable items.A child menu item becomes visible in a menu when the parent is selected. A child menu item is clickable and leads to a page.Each menu item has an index that defines the position in the menu. For a top-level menu item, this is the position in the the navigation bar counting from the left. For a child menu item, this is the position in the menu counting from the top.
Bonitasoft Application Menu API is one of 76 APIs that Bonitasoft publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include ApplicationMenu. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.
This API exposes 5 operations across 2 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 1.0.9.
Requests are made against a single base URL, http://localhost:8080/bonita.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 3
Bonitasoft Application Menu API declares
3 security schemes
for authenticating requests.
An API key is passed in the cookie as JSESSIONID (bonita_auth).
An API key is passed in the header as X-Bonita-API-Token (bonita_token).
It accepts HTTP bearer tokens (bearer_auth).
By default, every request must be authenticated.
bonita_auth— 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.bonita_token— 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.bearer_auth—  When Bonita runtime is configured for SSO with openID Connect it is possible To call the REST…
Paths & Operations 5
Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
Manage the set of menus in an application. This set of menus enables a user to navigate to the application pages. There are two types of menu item: A top-level item appears in the…
Schemas 4
The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are ApplicationMenu (6 properties), ApplicationMenuUpdateRequest (5 properties), ApplicationMenuCreateRequest (4 properties), Error (3 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Bonitasoft 12
Other APIs Bonitasoft publishes across the network.
This is an independent, third-party profile of Bonitasoft Application Menu 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.