ClusterHack Kanban Columns API
The kanban-columns API from ClusterHack — 2 operation(s) for kanban-columns.
The kanban-columns API from ClusterHack — 2 operation(s) for kanban-columns.
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/clusterhack-dev:clusterhack-dev-kanban-columns-api"
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.
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: Clusterhack Dev Kanban Columns API
version: 1.3.0
description: 'Operations tagged kanban-columns across 2 of this provider''s published API definitions: clusterhack-dev-openapi-original.json, clusterhack-dev-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://clusterhack.dev
description: Production. Not stated in the provider spec (no servers[]); the spec is served from https://clusterhack.dev/api/schema/ and its paths are rooted at /api/v1 and /geo-api.
tags:
- name: kanban-columns
paths:
/api/v1/kanban-columns/:
post:
operationId: kanban_columns_create
description: 'Shared plumbing for the four kanban resources.
Every one of them gets ``?=``, ``?search=`` and ``?ordering=`` — a
board is unusable over the API if you cannot ask it for "cards assigned to
me, due first". Default ordering stays the model''s ``Meta.ordering`` so a
request without ``?ordering=`` is still deterministic (and paginates
consistently).'
tags:
- kanban-columns
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/KanbanColumnRequest'
application/x-www-form-urlencoded:
schema:
$ref: '#/components/schemas/KanbanColumnRequest'
multipart/form-data:
schema:
$ref: '#/components/schemas/KanbanColumnRequest'
required: true
security:
- jwtAuth: []
- tokenAuth: []
- cookieAuth: []
- basicAuth: []
responses:
'201':
content:
application/json:
schema:
$ref: '#/components/schemas/KanbanColumn'
description: ''
'400':
description: The request body failed validation.
content:
application/json:
schema:
$ref: '#/components/schemas/ValidationError'
'401':
description: 'Not authenticated. The response carries `WWW-Authenticate: Bearer realm="api"`; obtain or refresh a token and retry.'
headers:
WWW-Authenticate:
description: Always `Bearer realm="api"`.
schema:
type: string
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorDetail'
'403':
description: Authenticated, but not permitted to perform this action on this object.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorDetail'
'429':
description: Rate limit exceeded (see `DEFAULT_THROTTLE_RATES`). `Retry-After` gives the number of seconds to wait.
headers:
Retry-After:
description: Seconds until the caller may retry.
schema:
type: integer
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorDetail'
'500':
description: Unhandled server error.
summary: Kanban columns create
x-summary-source: derived
get:
operationId: kanban_columns_list
description: 'Shared plumbing for the four kanban resources.
Every one of them gets ``?=``, ``?search=`` and ``?ordering=`` — a
board is unusable over the API if you cannot ask it for "cards assigned to
me, due first". Default ordering stays the model''s ``Meta.ordering`` so a
request without ``?ordering=`` is still deterministic (and paginates
consistently).'
parameters:
- in: query
name: board
schema:
type: integer
- name: ordering
required: false
in: query
description: Which field to use when ordering the results.
schema:
type: string
- name: page
required: false
in: query
description: A page number within the paginated result set.
schema:
type: integer
- name: page_size
required: false
in: query
description: Number of results to return per page.
schema:
type: integer
- name: search
required: false
in: query
description: A search term.
schema:
type: string
tags:
- kanban-columns
security:
- jwtAuth: []
- tokenAuth: []
- cookieAuth: []
- basicAuth: []
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/PaginatedKanbanColumnList'
description: ''
'401':
description: 'Not authenticated. The response carries `WWW-Authenticate: Bearer realm="api"`; obtain or refresh a token and retry.'
headers:
WWW-Authenticate:
description: Always `Bearer realm="api"`.
schema:
type: string
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorDetail'
'403':
description: Authenticated, but not permitted to perform this action on this object.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorDetail'
'429':
description: Rate limit exceeded (see `DEFAULT_THROTTLE_RATES`). `Retry-After` gives the number of seconds to wait.
headers:
Retry-After:
description: Seconds until the caller may retry.
schema:
type: integer
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorDetail'
'500':
description: Unhandled server error.
summary: Kanban columns list
x-summary-source: derived
/api/v1/kanban-columns/{id}/:
delete:
operationId: kanban_columns_destroy
description: 'Shared plumbing for the four kanban resources.
Every one of them gets ``?=``, ``?search=`` and ``?ordering=`` — a
board is unusable over the API if you cannot ask it for "cards assigned to
me, due first". Default ordering stays the model''s ``Meta.ordering`` so a
request without ``?ordering=`` is still deterministic (and paginates
consistently).'
parameters:
- in: path
name: id
schema:
type: integer
description: A unique integer value identifying this Kanban column.
required: true
tags:
- kanban-columns
security:
- jwtAuth: []
- tokenAuth: []
- cookieAuth: []
- basicAuth: []
responses:
'204':
description: No response body
'401':
description: 'Not authenticated. The response carries `WWW-Authenticate: Bearer realm="api"`; obtain or refresh a token and retry.'
headers:
WWW-Authenticate:
description: Always `Bearer realm="api"`.
schema:
type: string
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorDetail'
'403':
description: Authenticated, but not permitted to perform this action on this object.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorDetail'
'404':
description: No such object, or it is not visible to you.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorDetail'
'429':
description: Rate limit exceeded (see `DEFAULT_THROTTLE_RATES`). `Retry-After` gives the number of seconds to wait.
headers:
Retry-After:
description: Seconds until the caller may retry.
schema:
type: integer
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorDetail'
'500':
description: Unhandled server error.
summary: Kanban columns destroy
x-summary-source: derived
patch:
operationId: kanban_columns_partial_update
description: 'Shared plumbing for the four kanban resources.
Every one of them gets ``?=``, ``?search=`` and ``?ordering=`` — a
board is unusable over the API if you cannot ask it for "cards assigned to
me, due first". Default ordering stays the model''s ``Meta.ordering`` so a
request without ``?ordering=`` is still deterministic (and paginates
consistently).'
parameters:
- in: path
name: id
schema:
type: integer
description: A unique integer value identifying this Kanban column.
required: true
tags:
- kanban-columns
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/PatchedKanbanColumnRequest'
application/x-www-form-urlencoded:
schema:
$ref: '#/components/schemas/PatchedKanbanColumnRequest'
multipart/form-data:
schema:
$ref: '#/components/schemas/PatchedKanbanColumnRequest'
security:
- jwtAuth: []
- tokenAuth: []
- cookieAuth: []
- basicAuth: []
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/KanbanColumn'
description: ''
'400':
description: The request body failed validation.
content:
application/json:
schema:
$ref: '#/components/schemas/ValidationError'
'401':
description: 'Not authenticated. The response carries `WWW-Authenticate: Bearer realm="api"`; obtain or refresh a token and retry.'
headers:
WWW-Authenticate:
description: Always `Bearer realm="api"`.
schema:
type: string
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorDetail'
'403':
description: Authenticated, but not permitted to perform this action on this object.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorDetail'
'404':
description: No such object, or it is not visible to you.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorDetail'
'429':
description: Rate limit exceeded (see `DEFAULT_THROTTLE_RATES`). `Retry-After` gives the number of seconds to wait.
headers:
Retry-After:
description: Seconds until the caller may retry.
schema:
type: integer
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorDetail'
'500':
description: Unhandled server error.
summary: Kanban columns partial update
x-summary-source: derived
put:
operationId: kanban_columns_update
description: 'Shared plumbing for the four kanban resources.
Every one of them gets ``?=``, ``?search=`` and ``?ordering=`` — a
board is unusable over the API if you cannot ask it for "cards assigned to
me, due first". Default ordering stays the model''s ``Meta.ordering`` so a
request without ``?ordering=`` is still deterministic (and paginates
consistently).'
parameters:
- in: path
name: id
schema:
type: integer
description: A unique integer value identifying this Kanban column.
required: true
tags:
- kanban-columns
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/KanbanColumnRequest'
application/x-www-form-urlencoded:
schema:
$ref: '#/components/schemas/KanbanColumnRequest'
multipart/form-data:
schema:
$ref: '#/components/schemas/KanbanColumnRequest'
required: true
security:
- jwtAuth: []
- tokenAuth: []
- cookieAuth: []
- basicAuth: []
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/KanbanColumn'
description: ''
'400':
description: The request body failed validation.
content:
application/json:
schema:
$ref: '#/components/schemas/ValidationError'
'401':
description: 'Not authenticated. The response carries `WWW-Authenticate: Bearer realm="api"`; obtain or refresh a token and retry.'
headers:
WWW-Authenticate:
description: Always `Bearer realm="api"`.
schema:
type: string
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorDetail'
'403':
description: Authenticated, but not permitted to perform this action on this object.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorDetail'
'404':
description: No such object, or it is not visible to you.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorDetail'
'429':
description: Rate limit exceeded (see `DEFAULT_THROTTLE_RATES`). `Retry-After` gives the number of seconds to wait.
headers:
Retry-After:
description: Seconds until the caller may retry.
schema:
type: integer
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorDetail'
'500':
description: Unhandled server error.
summary: Kanban columns update
x-summary-source: derived
get:
operationId: kanban_columns_retrieve
description: 'Shared plumbing for the four kanban resources.
Every one of them gets ``?=``, ``?search=`` and ``?ordering=`` — a
board is unusable over the API if you cannot ask it for "cards assigned to
me, due first". Default ordering stays the model''s ``Meta.ordering`` so a
request without ``?ordering=`` is still deterministic (and paginates
consistently).'
parameters:
- in: path
name: id
schema:
type: integer
description: A unique integer value identifying this Kanban column.
required: true
tags:
- kanban-columns
security:
- jwtAuth: []
- tokenAuth: []
- cookieAuth: []
- basicAuth: []
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/KanbanColumn'
description: ''
'401':
description: 'Not authenticated. The response carries `WWW-Authenticate: Bearer realm="api"`; obtain or refresh a token and retry.'
headers:
WWW-Authenticate:
description: Always `Bearer realm="api"`.
schema:
type: string
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorDetail'
'403':
description: Authenticated, but not permitted to perform this action on this object.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorDetail'
'404':
description: No such object, or it is not visible to you.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorDetail'
'429':
description: Rate limit exceeded (see `DEFAULT_THROTTLE_RATES`). `Retry-After` gives the number of seconds to wait.
headers:
Retry-After:
description: Seconds until the caller may retry.
schema:
type: integer
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorDetail'
'500':
description: Unhandled server error.
summary: Kanban columns retrieve
x-summary-source: derived
components:
schemas:
ErrorDetail:
type: object
description: The body DRF returns for a handled error.
properties:
detail:
type: string
description: Human-readable explanation of the failure.
required:
- detail
PatchedKanbanColumnRequest:
type: object
properties:
name:
type: string
minLength: 1
maxLength: 120
order:
type: integer
maximum: 2147483647
minimum: 0
board:
type: integer
KanbanColumn:
type: object
properties:
id:
type: integer
readOnly: true
name:
type: string
maxLength: 120
order:
type: integer
maximum: 2147483647
minimum: 0
created:
type: string
format: date-time
readOnly: true
last_updated:
type: string
format: date-time
readOnly: true
board:
type: integer
required:
- board
- created
- id
- last_updated
- name
KanbanColumnRequest:
type: object
properties:
name:
type: string
minLength: 1
maxLength: 120
order:
type: integer
maximum: 2147483647
minimum: 0
board:
type: integer
required:
- board
- name
ValidationError:
type: object
description: Field-keyed validation errors. Errors that belong to no single field appear under `non_field_errors`.
additionalProperties:
type: array
items:
type: string
PaginatedKanbanColumnList:
type: object
required:
- count
- results
properties:
count:
type: integer
example: 123
next:
type:
- string
- 'null'
format: uri
example: http://api.example.org/accounts/?page=4
previous:
type:
- string
- 'null'
format: uri
example: http://api.example.org/accounts/?page=2
results:
type: array
items:
$ref: '#/components/schemas/KanbanColumn'
securitySchemes:
basicAuth:
type: http
scheme: basic
cookieAuth:
type: apiKey
in: cookie
name: sessionid
jwtAuth:
type: http
scheme: bearer
bearerFormat: JWT
description: 'Access token from `POST /api/v1/auth/jwt/`, refreshed at `POST /api/v1/auth/jwt/refresh/`. Send as `Authorization: Bearer <access>`.'
tokenAuth:
type: apiKey
in: header
name: Authorization
description: Token-based authentication with required prefix "Token"
x-refined-from:
- clusterhack-dev-openapi-original.json
- clusterhack-dev-openapi.yml