WeKan
WeKan is an open-source kanban board application that helps teams visualize work, manage tasks, and improve workflow efficiency. It offers features such as customizable boards, drag‑and‑drop cards, real‑time collaboration, and integrations with tools like GitHub and Trello. The project is community‑driven, with active development and a focus on flexibility and ease of use for both personal and enterprise environments.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles WeKan the way a machine reads it — 25 machine-readable artifacts across 2 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — WeKan scores 18.0/100 (emerging), with a separate agent-readiness read of 20/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-10-31 · rubric v0.25.0
Put this on your own site. The badge is drawn live from WeKan's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/wekan/"
title="WeKan on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/wekan.svg"
alt="WeKan Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/wekan/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/wekan/"
title="WeKan on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/wekan/card.svg"
alt="WeKan Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile WeKan
Each block below is one kind of artifact we hold for WeKan. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 22
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
WeKan Attachments API
The Attachments API from WeKan — 15 operation(s) for attachments.
WeKan Attachment Storage Settings API
The AttachmentStorageSettings API from WeKan — 1 operation(s) for attachmentstoragesettings.
WeKan Boards API
The Boards API from WeKan — 33 operation(s) for boards.
WeKan Card Comments API
The CardComments API from WeKan — 2 operation(s) for cardcomments.
WeKan Cards API
The Cards API from WeKan — 19 operation(s) for cards.
WeKan Checklists API
The Checklists API from WeKan — 2 operation(s) for checklists.
WeKan Dependencies API
The Dependencies API from WeKan — 3 operation(s) for dependencies.
WeKan Integrations API
The Integrations API from WeKan — 3 operation(s) for integrations.
WeKan Lists API
The Lists API from WeKan — 6 operation(s) for lists.
WeKan Login API
The Login API from WeKan — 2 operation(s) for login.
WeKan Org API
The Org API from WeKan — 3 operation(s) for org.
WeKan Organizations API
The Organizations API from WeKan — 3 operation(s) for organizations.
WeKan Problems API
The Problems API from WeKan — 3 operation(s) for problems.
WeKan Rules API
The Rules API from WeKan — 2 operation(s) for rules.
WeKan Settings API
The Settings API from WeKan — 5 operation(s) for settings.
WeKan Swimlanes API
The Swimlanes API from WeKan — 4 operation(s) for swimlanes.
WeKan Team API
The Team API from WeKan — 3 operation(s) for team.
WeKan Teams API
The Teams API from WeKan — 3 operation(s) for teams.
WeKan Users API
The Users API from WeKan — 8 operation(s) for users.
WeKan Checklist Items API
The Checklist Items API from WeKan — 2 operation(s) for checklist items.
WeKan Custom Fields API
The Custom Fields API from WeKan — 4 operation(s) for custom fields.
WeKan Event Log API
The Event Log API from WeKan — 3 operation(s) for event log.
Scroll within the panel for all 22 ·
Spectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
WeKan API Rules
SPECTRALSecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for WeKan — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Access & Security 1
Authentication, authorization, and security posture
Company 1
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/wekan · machine-readable index on apis.io
This is an independent, third-party profile of WeKan, 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.