iKanban core API

iKanban core API as documented publicly: 3 operations. Contract generated from the documentation by API Evangelist (2026-11-12); not the provider's own document.

GitHub OpenAPI

Operations 3

POST /sse POST /sse #
POST /tasks Step 4 — Your First Endpoint (Axum) #
GET /tasks/{id} Step 4 — Your First Endpoint (Axum) #

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.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/i-kanban-com:core-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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

i-kanban-com-core-openapi-generated.yml Raw ↑
openapi: 3.1.0
info:
  title: iKanban core API
  version: '2026-11-12'
  description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-11-12: 3 operation(s) read from 2 public documentation page(s) (each operation
    names its page in x-source). This is not the provider''s published contract; iKanban has published no machine-readable contract that the pipeline
    could find. Engine: local.'
  x-evidence-tiers:
    code-example: 4
    documentation: 6
    pages-with-code: 8
    pages-read: 10
  x-generated-from: documentation
  x-provenance: generated
  x-authored-by: API Evangelist
  x-generated: '2026-11-12'
  x-generator: generate-contract-from-docs.py
  x-engine: local
  x-sources:
  - https://i-kanban.com/docs/mcp/other-clients
  - https://i-kanban.com/guides/rust-as-backend/first-endpoint
  x-docs-section: core
servers:
- url: https://mcp.i-kanban.com
paths:
  /sse:
    post:
      operationId: post_sse
      tags:
      - Sse
      summary: POST /sse
      x-source: https://i-kanban.com/docs/mcp/other-clients
      responses:
        '201':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl -s -o /dev/null -w \"%{http_code}\\n\" -X POST https://mcp.i-kanban.com/sse\n Once your client is connected, ask it something\
          \ that needs the board, using your own team's identifier: \n List the open tasks in the ENG team.\n It should call list_issues and reply\
          \ with the tasks. \n What the server offers \n Read, create and update across teams, issues, projects, sprints, releases, documents,\
          \ folders, co"
  /tasks:
    post:
      operationId: post_tasks
      tags:
      - Tasks
      summary: Step 4 — Your First Endpoint (Axum)
      x-source: https://i-kanban.com/guides/rust-as-backend/first-endpoint
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PostTasksRequest'
      responses:
        '201':
          description: Success (status as documented)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PostTasksResponse'
      x-evidence:
        kind: documentation
  /tasks/{id}:
    get:
      operationId: get_tasks_id
      tags:
      - Tasks
      summary: Step 4 — Your First Endpoint (Axum)
      x-source: https://i-kanban.com/guides/rust-as-backend/first-endpoint
      parameters:
      - name: id
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Success (status as documented)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetTasksIdResponse'
      x-evidence:
        kind: documentation
security:
- bearer: []
components:
  schemas:
    PostTasksRequest:
      type: object
      properties:
        title:
          type: string
          description: Title of the new task
      required:
      - title
    PostTasksResponse:
      type: object
      properties:
        id:
          type: integer
        title:
          type: string
        done:
          type: boolean
    GetTasksIdResponse:
      type: object
      properties:
        id:
          type: integer
        title:
          type: string
        done:
          type: boolean
  securitySchemes:
    bearer:
      type: http
      scheme: bearer
tags:
- name: Sse
- name: Tasks