Many docs still used flat GitHub-wiki page-name links like [Backup](Backup), [OAuth2](OAuth2) or [FAQ](FAQ) that only resolved on the old wiki; in the docs/ hierarchy they were broken. Rewrite them to correct relative paths of the existing pages (e.g. ](Backup) -> ](Backup.md), ](OAuth2) -> ](../Login/OAuth2.md), ](Sandstorm) -> ](../Platforms/FOSS/Sandstorm/Sandstorm.md)). Mapping: page name -> docs/<...>/<Name>.md by filename, with explicit handling for renamed pages (Caddy/Nginx-Webserver-Config, Wekan-Markdown, the Sandstorm grain export page, Uberspace) and the REST-API-<X> family -> docs/API/<X>.md. Ambiguous names resolved by preferring a same-directory file or the primary page. Anchors and markdown titles preserved. 280 links across the docs tree. Out of scope (left as-is): source-code references (models/*.js etc.) and [Link](url) placeholders, which are not docs pages. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1.0 KiB
This page is about using Wekan from Java code.
Wekan is made with Javascript and uses MongoDB database.
Using Wekan REST API
With Jython, you can use Wekan REST API like with Python
Global Webhooks
For Global Webhooks in Admin Panel, Wekan sends all events in all boards to webhook URL, like add card. Although, sending some messages for some events is not yet implemented, more could be added later.
Data is sent in this kind of JSON format.
You can receive webhook data in Java like this.
Then for each received data, your code can read content and based on incoming data call Wekan REST API, some Java interface, etc.
Outgoing Webhooks can also go to Slack, RocketChat, NodeRED, PowerShell etc. See right menu webhook links when scrolling down wiki page Wekan documentation
If you call some Java interface that returns some data, you can then write that data to Wekan card with Wekan REST API.