API

Find out how you can take advantage of the Kanbanize Restful API.

General information


To use the Kanbanize API, you need to send an https POST request to the following address:

https://<subdomain>.kanbanize.com/index.php/api/kanbanize/<function>

 

Where:

<subdomain> is the subdomain part for your account.

<function> is one of the following:

 

The following limits for using the API are implemented:

Function login get_projects_and_boards get_board_structure get_board_settings create_new_task delete_task get_task_details
Limit per hour (per API KEY) 30 30 30 30 30 60 60
Function get_all_tasks add_comment move_task edit_task get_board_activities block_task  
Limit per hour (per API KEY) 60 30 60 30 30 30  

Authentication


Every Kanbanize user has a personal API key that is used to authenticate the user when accessing the API. Each API request (except those for the “login” function) must contain a valid http header called “apikey”. The header’s value should be a valid API key. You can obtain it from the output of the “login” function or via the web version (click on your username in the upper right corner and select API).

If you have Two Factor Authentication (2FA) enabled for your account you have to supply an additional http header called “otp”. This header should contain a valid One-time Password (OTP) for the time the request is made. The algorithm for generating One-time Password is based on the implementation of Google Authenticator. The personal 2FA secret key used in the algorithm is shown only once when 2FA is set up. You should store it in a secure place and use it to generate OTPs when needed. For more information on how to use 2FA with Kanbanize check this post in our blog.

 

 

Input parameters


Depending on the function you are accessing, you need to specify certain parameters so that the request could be processed properly. The way parameters are set is by embedding them either into the request URI or into the request body. The request body is the recommended approach.

 

Examples:

 

Sending a parameter “boardid” with value 22 as part of the request URI:

 

https://<subdomain>/index.php/api/kanbanize/<function>/boardid/22

 

Sending a parameter “boardid” with value 22 and parameter “taskid” with value 14 as part of the request URI:

 

https://<subdomain>/index.php/api/kanbanize/<function>/boardid/22/taskid/14

 

Sending a parameter “boardid” with value 22 and parameter “taskid” with value 14 as part of the request BODY. The BODY needs to be a valid JSON string. If a value is set in both the BODY and the URI, the BODY value is taken. If you use the backslash (\) or a double quote (“) you need to escape them with the backslash character: (\\) or (\”).

 

The request URI: https://<subdomain>/index.php/api/kanbanize/<function>

The request body: {"boardid":22,"taskid":14}

 

You can also specify the format of the result. Available formats are:

 

XML (default if formatting parameter is not provided)

 

https://<subdomain>/index.php/api/kanbanize/<function>/<parameters>/format/xml

 

JSON (for more information check this website http://www.json.org/)

 

https://<subdomain>/index.php/api/kanbanize/<function>/<parameters>/format/json

Login [login]


Required  email pass
  Your email address Your password
Optional n/a
   
Output mail username realname companyname timezone apikey
  Your email address Your username Your name Company name Your time zone Your API key.

 

https://<subdomain>.kanbanize.com/index.php/api/kanbanize/login/
Request body: {"email": "test@test.com", "pass":"test"}

 

Projects and boards [get_projects_and_boards]


Required  n/a
   
Optional n/a
   
Output projects projects[][name] projects[][id] projects[][boards]
  Array of the projects. The name of the project The ID of the project Array of details for any boards in current project ( name, id )

 

 

https://<subdomain>.kanbanize.com/index.php/api/kanbanize/get_projects_and_boards/

Board structure [get_board_structure]


Required  boardid
  The ID of the board whose structure you want to get. You can see the board ID on the dashboard screen, in the upper right corner of each board.
Optional n/a
   
Output columns columns[][position] columns[][lcname] columns[][description] lanes lanes[][lcname] lanes[][color] lanes[][description]
  Array containing the board columns (only the columns on last level are returned) The position of the column The name of the column. The description of the column or swimlane. Array containing the board swimnales. The name of the swimlane. The color of the swimlane. The description of the column or swimlane.

 

https://<subdomain>.kanbanize.com/index.php/api/kanbanize/get_board_structure/
Request body: {"boardid":"2"}

Full board structure [get_full_board_structure]


Required  boardid
  The ID of the board the structure of which you want to get. You can see the board ID on the dashboard screen, in the upper right corner of each board.
Optional n/a
   
Output columns columns[][position] columns[][lcname] columns[][path] columns[][description] columns[][lcid] columns[][children[]]* lanes lanes[][position] lanes[][lcname] lanes[][path] lanes[][color] lanes[][description] lanes[][lcid]
  Array containing the board columns The position of the column The name of the column. Unique identifier which contains the id of the column with all its parent columns. E.g. progress_17_1478 means that the column id is 1478, its parent is the column with id 17 and the parent area is IN PROGRESS. The description of the column or swimlane. Lane/Column ID. This is the ID of the column, which is the last part of the path parameter described above. If the column has sub-columns, they are returned in the children array recursively. Array containing the board swimnales. The position of the swimlane. The name of the swimlane. Unique identifier of the swimlane which concatenates the string “lane_” concatenated with the swimlane ID. The color of the swimlane. The description of the column or swimlane. Lane/Column ID. This is the ID of the swimlane, which is the last part of the path parameter described above.

 

https://<subdomain>.kanbanize.com/index.php/api/kanbanize/get_full_board_structure/
Request body: {"boardid":"2"}

Board settings [get_board_settings]


Required  boardid
  The ID of the board the structure of which you want to get. You can see the board ID on the dashboard screen, in the upper right corner of each board.
Optional n/a
   

Array with the definitions of all custom fields assigned to the board. 

Output usernames avatars templates types customFields
  Array containing the usernames of the board members. Associative array containing the URLs to the avatars of the board members. Array containing the templates available to this board. Array containing the types available to this board. Array containing the definitions of all custom fields assigned to the board.

 

 

https://<subdomain>.kanbanize.com/index.php/api/kanbanize/get_board_settings/
Request body: {"boardid":"2"}

Get board activities [get_board_activities]


Required  boardid fromdate todate
  The ID of the board. You can see the board ID on the dashboard screen, in the upper right corner of each board. The date after which the activities of interest happened. Accepts the following formats: ‘2012-05-05′, ’10 September 2012’. The date before which the activities of interest happened. Accepts the following formats: ‘2012-05-05′, ’10 September 2012’.
Optional page resultsperpage author eventtype textformat
  Default is 1 Default is 30 Default is ALL Options : Transitions, Updates, Comments, Blocks. Default is All Options: “plain” (default) and “html”. If the plain text format is used, the HTML tags are stripped from the history details.
Output allactivities page activities activities[][author] activities[][event] activities[][text] activities[][date] activities[][taskid]
  The number of all activities for the corresponding time window specified by the fromdate and todate parameters. The current page. Array containing the board activities. Who performed the action. Type of the event (Task moved, Task blocked, Task archived etc.) History details. When the event happened. The id of the task which was updated/moved/blocked, etc.

 

https://<subdomain>.kanbanize.com/index.php/api/kanbanize/get_board_activities/
Request body: {"boardid":"2", "fromdate":"2012-08-05", "todate":"2017-08-05", "page":"2"}

 

https://<subdomain>.kanbanize.com/index.php/api/kanbanize/get_board_activities/
Request body: {"boardid":"2", "fromdate":"2012-08-05", "todate":"2017-08-05", "page":"3", "eventtype":"Comments"}

Create new task [create_new_task]


If the user identified by the API key has pre-configured default column or swimlane for the specified board, and no ‘column’ or ‘lane’ parameter is supplied in the request, the task will be created in the column and swimlane specified in the default board settings.

 

If no default column or swimlane are configured for the specified board and no ‘column’ or ‘lane’ parameters are supplied in the request, the task will be created into the first swimlane of the Backlog section of the board.

 

If ‘column’, ‘lane’ and/or ‘position’ parameters are supplied, then a move operation is executed automatically after the creation of the task. The ‘column’ and ‘lane’ parameters effectively override any configurations with respect to where the task is to be created.

 

 

Required  boardid
  The ID of the board whose structure you want to get. You can see the board ID on the dashboard screen, in the upper right corner of each board.
Optional title description priority assignee color size tags deadline extlink type template < customfield > subtasks subtasks[][title] subtasks[][assignee] column lane position exceedingreason returntaskdetails
  Title of the task Description of the task One of the following: Low, Average, High Username of the assignee (must be a valid username) Any color code (e.g. #34a97b) without the # character. Size of the task Space separated list of tags Deadline in the format: yyyy-mm-dd (e.g. 2011-12-13) A link in the following format: https://domain.com/resource. This option is only supported when parameters are sent in the request body. The name of the type you want to set. The name of the template you want to apply. If you specify any property as part of the request, the one specified in the template will be overwritten. The name of the custom field you want to set. An array of subtasks. Title of the new subtask. An assignee for the subtask (Default:None). The name of the column to create the task into (default is Backlog). If column names are not unique, you must specify the full path to the column: topParentColumn.nextParentColumn.columnName. The name of the swimlane to put the newly created task into. If omitted, the task will be placed in the first swimlane. The position of the task in the new column/swimlane (zero-based). If omitted, the task will be placed at the bottom of the column. If you can exceed a limit with a reason, supply it with this parameter. Applicable only if column, lane and/or position are supplied. If set to 1 the method will return the details of the created task.
Output id details movingerror
  The ID of the newly created task. The details of the newly created task. (Only if returntaskdetails was set)
The format is the same as the output of get_task_details.
If moving failed, the moving error will be returned here. (Only if column, swimlane and/or position were set)

 

https://<subdomain>.kanbanize.com/index.php/api/kanbanize/create_new_task/
Request body: {"boardid":"17", "title":"test task", "description":"task description", "priority":"High", "assignee":"mitaka", "color":"FFCC00", "tags":"tag1 tag2", "deadline":"2011-12-13"}

Delete task [delete_task]


Required  boardid taskid
  The ID of the board where the task to be deleted is. You can see the board ID on the dashboard screen, in the upper right corner of each board. The ID of the task to be deleted.
Optional n/a
   
Output status
  The status of the operation (1 or error).

 

http://<subdomain>.kanbanize.com/index.php/api/kanbanize/delete_task/
Request body: {"boardid":"17", "taskid":"173"}

Get task details [get_task_details]


 

Required  boardid taskid/taskid[]
  The ID of the board where the task is located. You can see the board ID on the dashboard screen, in the upper right corner of each board. The ID of the task (or an array of task ids) whose details you want to get.
Optional history comments event textformat
  Set to “yes” if you want to get history for the task. Set to “yes” if you want to get comments for the task. Only applicable if “history” is set to “yes”. Accepts the following events: move, create, update, block, delete, comment, archived, subtask, loggedtime. If the parameter is not set, all of the events will be returned. Options: “plain” (default) and “html”. If the plain text format is used, the HTML tags are stripped from the task description.
Output taskid title description type assignee subtasks subtaskscomplete color priority size deadline deadlineoriginalformat extlink tags leadtime blocked blockedreason subtaskdetails comments historydetails columnname lanename columnid laneid position columnpath loggedtime customfields customfields[][fieldid] customfields[][name] customfields[][type] customfields[][value] customfields[][mandatory] attachments attachments[][url] attachments[][clientName] attachments[][uniqueName] attachments[][fileSize] attachments[][fileType] attachments[][status]
  The ID of the task Title of the task Description of the task The task type Username of the assignee Number of subtasks Number of completed subtasks Task color Task priority Task size Task deadline in format Day Month (e.g. 01 Aug) Task deadline in format yyyy-mm-dd (e.g. 2012-08-01) Task external link Task tags Leadtime in days Is the task blocked (0 – no/ 1 – yes) Why the task is blocked Details of any subtasks (subtask id, subtask assignee, subtask title, subtask date of completion). Details of any comment (author, event, text, date, taskid). Details of task history (eventtype, historyevent, details, author, date, history id). The name of the column in which the task is located. The name of the swim-lane in which the task is located. The ID of the column in which the task is located. The ID of the swim-lane in which the task is located. The position of the card in its current column. The full path to the card column in the format: “Column.Subcolumn1.Subcolumn2”. If the task is located in a main column this will be the same as “columnname”. The accumulated logged time of the task in hours. Array of the custom fields applied to the card. The id number of the field. The full path to the card column in the format: “Column.Subcolumn1.Subcolumn2”. If the task is located in a main column this will be the same as “columnname”. Data type of the custom field {text|date|number|contributor|link|dropdown}. The value of the custom field. A flag if the field is mandatory {true|false}. Array with the info about the new file(s) attached to the card. A link to the file if it was added from a storage service (Dropbox, Google Drive, etc.). The name of the file as uploaded by the user. Unique name of the file. The size of the file. The extension of the file. Upload status.
 

https://<subdomain>.kanbanize.com/index.php/api/kanbanize/get_task_details/
Request body: {"boardid":"17", "taskid":"173"}

Get all tasks [get_all_tasks]


 

Required  boardid
  The ID of the board where the tasks are located. You can see the board ID on the dashboard screen, in the upper right corner of each board.
Optional subtasks comments container fromdate todate showInitiatives version page textformat
  Set to “yes” if you want to get subtask details for each task. Set to “yes” if you want to get comments for each task. Set to “archive” if you want to get tasks from archive. Only applicable with container=”archive”. The date after which the tasks have been archived. Accepts the format: ‘2012-05-05’. Default valuе is ‘1970-01-01’ Only applicable with container=”archive”. The date before which the tasks have been archived. Accepts the following format: ‘2012-05-05’. Default valuе is ‘now’ Only applicable with container=”archive”. If this parameter is set to “1” the response will return only initiatives. Otherwise, it will return only tasks. Gives the tasks from the specified archive version. The fromdate and todate parameters are ignored. With this parameter you control which page number to get. The method returns 30 tasks per page. Options: “plain” (default) and “html”. If the plain text format is used, the HTML tags are stripped from the task description.
Output taskid position type assignee title description subtasks subtaskscomplete color priority size deadline deadlineoriginalformat extlink tags columnid laneid workflow leadtime blocked blockedreason subtaskdetails comments columnname lanename columnpath logedtime* attachments attachments[][url] attachments[][clientName] attachments[][uniqueName] attachments[][fileSize] attachments[][fileType] attachments[][status]
  The ID of the task The position of the task The task type Username of the assignee Title of the task Description of the task Number of subtasks Number of completed subtasks Task color Task priority Task size Task deadline in format Day Month (e.g. 01 Aug) Task deadline in format yyyy-mm-dd (e.g. 2012-08-01) Task external link Task tags The ID of the column in which the task is located. The ID of the swim-lane in which the task is located. The workflow to which the item belongs (0 – cards workflow / 1 – initiatives workflow). Leadtime in days Is the task blocked (0 – no/ 1 – yes) Why the task is blocked Details of any subtasks (subtask id, subtask assignee, subtask title, subtask date of completion). Details of any comment (author, event, text, date, taskid). The name of the column in which the task is located. The name of the swim-lane in which the task is located. The full path to the card column in the format: “Column.Subcolumn1.Subcolumn2”. If the task is located in a main column this will be the same as “columnname”. The accumulated logged time of the task in hours. *There is a missing letter G, which has not been added on purpose to maintain backwards compatibility. Array with the info about the new file(s) attached to the card. A link to the file if it was added from a storage service (Dropbox, Google Drive, etc.). The name of the file as uploaded by the user. Unique name of the file. The size of the file. The extension of the file. Upload status.
 
 

https://<subdomain>.kanbanize.com/index.php/api/kanbanize/get_all_tasks/
Request body: {"boardid":"17"}

Add comment [add_comment]


Required comment taskid
  The comment to be added. The ID of the task you want to comment.
Optional n/a
   
Output id author date
  ID of the history event Author of the comment Current date
 
 

https://<subdomain>.kanbanize.com/index.php/api/kanbanize/add_comment/
Request body: {"taskid":"173", "comment":"this is a test comment"}

Move task [move_task]


With this action you can move tasks on the board by specifying the column name and optionally the swim-lane name.

 

Required  boardid taskid
  The ID of the board to move the task into. You can see the board ID on the dashboard screen, in the upper right corner of each board. The ID of the task to move.
Optional column lane position* exceedingreason
  The name of the column to move the task into. If the name of the column is unique, you can specify it alone, but if there are more than one columns with that name, you must specify it as columnname1 . columnname2 . columnname3. The name of the swim-lane to move the task into. If omitted, the swimlane doesn’t change. The position of the task in the new column (zero-based). If omitted, the task will be placed at the bottom of the column.
*This parameter is not taken into consideration when moving tasks to another board.
If you can exceed a limit with a reason, supply it with this parameter.
Output status
  The status of the operation (1 or error).
 
 
https://<subdomain>.kanbanize.com/index.php/api/kanbanize/move_task/
Request body: {"boardid":"17", "taskid":"24", "column":"MyColumn"}
 
https://<subdomain>.kanbanize.com/index.php/api/kanbanize/move_task/
Request body: {"boardid":"17", "taskid":"24", "column":"MainColumn.SubColumn.MyColumn"}
 
https://<subdomain>.kanbanize.com/index.php/api/kanbanize/move_task/
Request body: {"boardid":"17", "taskid":"24", "column":"MainColumn.SubColumn.MyColumn", "lane":"Bugs"}

Edit task [edit_task]


With this action you can update the task details.

 

Required boardid taskid
  The ID of the board where the task to be edited is located. You can see the board ID on the dashboard screen, in the upper right corner of each board. The ID of the task to edit.
Optional title description priority assignee color size tags deadline extlink type < customfield >
  Title of the task Description of the task One of the following: Low, Average, High, Critical Username of the assignee (must be a valid username) Any color code (e.g. #34a97b) without the # character in front of the code. Size of the task Space separated list of tags Deadline in the format: yyyy-mm-dd (e.g. 2011-12-13) A link in the following format: https://domain.com/resource. This option is only supported when parameters are sent in the request body. The name of the type you want to set. A custom field to be updated. If the field is not present in the card, it will be automatically assigned with the provided value.
Output status
  The status of the operation (1 or error).
 
 

https://<subdomain>.kanbanize.com/index.php/api/kanbanize/edit_task/
Request body: {"boardid":"17", "taskid":"24", "title":"My new title", "description":"My new description", "size":"24"}

Block task [block_task]


Required boardid taskid event blockreason
  The ID of the board where the task to be blocked/unblocked is located. You can see the board ID on the dashboard screen, in the upper right corner of each board. The ID of the task Possible valules: ‘block’ – block a task; ‘editblock’ – edit the blocked reason; ‘unblock’ – unblock a task Required if event is set to ‘block’ or ‘editblock’
Optional n/a
   
Output status
  The status of the operation (1 or error).
 
 

https://<subdomain>.kanbanize.com/index.php/api/kanbanize/block_task/
Request body: {"boardid":"2", "taskid":"1173", "event":"block", "blockreason":"Reason text"}


https://<subdomain>.kanbanize.com/index.php/api/kanbanize/block_task/
Request body: {"boardid":"2", "taskid":"1173", "event":"unblock"}

Add subtask [add_subtask]


Required taskparent
  The ID of the task where the subtask to be created is located.
Optional title assignee
   Title of the subtask Username of the assignee (must be a valid username)
Output status
  The ID of the newly created subtask or 0 if an error has occurred.
 
 

https://<subdomain>.kanbanize.com/index.php/api/kanbanize/add_subtask/
Request body: {"taskparent":"254", "title":"sample subtask title", "assignee":"myusername"}

Edit subtask [edit_subtask]


Required boardid subtaskid
  The ID of the board where the subtask to be edited is located. You can see the board ID on the dashboard screen, in the upper right corner of each board. The ID of the subtask
Optional title assignee complete
   Title of the subtask Username of the assignee (must be a valid username) Options: 1 or 0. If it`s set to 1 the subtask will be marked as finished, otherwise as unfinished.
Output status
  The status of the operation (1 or error).
 
 

https://<subdomain>.kanbanize.com/index.php/api/kanbanize/edit_subtask/
Request body: {"boardid":"68", "subtaskid":"673", "title":"new subtask title", "complete":"1"}

Log time [log_time]


Required loggedtime taskid
  The number of hours you want to add to the task. The ID of the task or subtask to log time to.
Optional description date
  Comment about the log time entry. Sets the date for which the time is logged. Accepted format is YYYY-MM-DD.
Output id historyid taskid author details loggedtime issubtask title comment origindate entrydate
  The id of the log time event. The id of the event (for internal use). The id of the task or subtask that has been updated with a log time event. The username of the API user who updated the task. Message explaining the log time event. The number of hours that have been logged. A boolean parameter that shows whether the task is a subtask or not. The title of the task that has been updated. The comment that has been added along with the time log. Timestamp of the event (no timezone applied ). Timestamp of the event (timezone applied ).
 
 
 

https://<subdomain>.kanbanize.com/index.php/api/kanbanize/log_time/
Request body: {"taskid":"68", "loggedtime":"673"}

Get links [get_links]


The call to this method will return an array containing the links data. Tasks which do not have any links will be omitted.

Required boardid or taskid
 

boardid : An integer or an array of integers. Data for the links of all tasks will be returned; taskid: An integer or an array of integers for which the links data will be returned.

Optional boardid taskid
  A single integer or an array of integers denoting board IDs. Data for the links of all tasks in the boards will returned. A single integer or an array of integers denoting the task IDs for which the links data will be returned.
Output taskid parent children mirrors relatives predecessors successors
  The id of the task to which the links data belongs. The task ID of the task assigned as a parent. An array of task IDs, which are children of the task. An array of task IDs, which are mirrors of the task. An array of task IDs, which are relatives of the task. An array of task IDs, which are predecessors of the task. An array of task IDs, which are successors of the task.
 

http://<subdomain>.kanbanize.com/index.php/api/kanbanize/get_links/
Request body: {"taskid":[17,27], "boardid":"4"}

Edit link [edit_link]


Required taskid action type linkedid
  The ID of the task that will be linked. Options: “set” or “unset” Options: ‘child’, ‘parent’, ‘relative’, ‘mirror’, ‘predecessor’, ‘successor’. For all link types the logic is as follows: Make {taskid} a {type} of {linkedid} The ID of the task that will be linked to {taskid}.
Optional n/a
   
Output status
  The status of the operation (1 or error).
 
 

https://<subdomain>.kanbanize.com/index.php/api/kanbanize/edit_link/
Request body: {"taskid":"17", "action":"set", "linkedid":"27", "type":"relative"}

Add attachment [add_attachment]


This function is different from the others. The request should be encoded as multipart/form-data. One part should be named params and should contain a JSON with the boardid and taskid of the task you wish to add an attachment to. The other parts (between 1 and 5) should contain the file(s) to be attached in binary format.

Output attachments attachments[][url] attachments[][clientName] attachments[][uniqueName] attachments[][fileSize] attachments[][fileType] attachments[][status]
  Array with the info about the new file(s) attached to the card. A link to the file if it was added from a storage service (Dropbox, Google Drive, etc.). The name of the file as uploaded by the user. Unique name of the file. The size of the file. The extension of the file. Upload status.
 
 
https://<subdomain>.kanbanize.com/index.php/api/kanbanize/add_attachment/

Request headers:
content-type: multipart/form-data; boundary=AnyStringNotFoundInTheBody
apikey:
Request body:
--AnyStringNotFoundInTheBody
Content-Disposition: form-data; name="params"
{"taskid":"12345","boardid":"1"}
--AnyStringNotFoundInTheBody
Content-Disposition: form-data; name="Screenshot.png"; filename="Screenshot.png"
Content-Type: image/png
[binary image data]
--AnyStringNotFoundInTheBody--

Archive task [archive_task]


Required cardid
  Id or ids of cards that will be archived. The cards must be not be blocked, in column Done or in column Archive.
Optional version
  Version of the archive. When selected it can’t be empty, also can’t be array of values.
Output status
  Status 1 (True) if successful operation or Error when False.
 
 

https://<subdomain>.kanbanize.com/index.php/api/kanbanize/archive_task
Request body: {"cardid":[17,321], "version":"name-of-the-versions"}

Edit custom fields [edit_custom_fields]


Required cardid fields fields[][name] fields[][value]
  The id of the card for which you want to apply custom field. The custom field should already have been created. An array of the custom fields. The name of the custom field. Must match valid custom field per board. The value of the custom field. Value type should be the same as from the custom field declaration.
Optional n/a
   
Output status
  Status 1 (True) if successful operation or Error when False!
 
 

https://<subdomain>.kanbanize.com/index.php/api/kanbanize/edit_custom_fields 
Request body: {"cardid":"17", "fields":[{"name":"price", "value":"233"}, {"name":"mail", "value":"ex@test.com"}]}

Get Attachment [get_attachment]


Use this call to download attachments.

Required taskid uniquename
 

The ID of the card holding the attachment.

The uniqueName parameter of the attachment. Can be obtained through get_task_details or get_all_tasks.

Optional thumbnail encoding
  Set to “yes” if you want to get a thumbnail of the original attachment. Valid only for image files. Specifies the encoding in which to return the file. Supported formats are ‘binary’ and ‘base64’. Default is ‘binary’. Note that if any error occurs the response format is determined by the ‘format’ URL parameter.
Output  Attachment data or error.
 
https://.kanbanize.com/index.php/api/kanbanize/get_attachment/
Request body: {taskid:27, uniquename:"uniqueNameOfTheFile.txt"}

Powerful, right? Try it yourself for free now!

Start my free trial The trial account in Kanbanize provides access to all features in the system with almost no restrictions. During the 30-day trial period you can invite your team and test the application in a production-like environment.

A Digital Platform for Classic Kanban Cards

Kanban product management is a proven system that the most successful companies and teams around the world use. This system relies on cards to break large and complex projects into smaller and more manageable pieces.

Kanbanize uses digital boards that feature Kanban cards. These cards give you and your team the ability to:

  • Move cards across the Kanban board so teams can visualize progress
  • Limit the amount of cards given to a user, giving each team member a manageable workload for peak efficiency
  • Create different types of cards, allowing users to only see cards that are relevant to their work
  • Use Kanban card templates that feature predefined attributes and subtasks
  • Define custom fields that you can set as mandatory or optional

Our Kanban card board is a modern and digital representation of the classic Kanban cards that made the system famous. As a user, you get a proven and trusted productivity and efficiency system in a digital platform that adds functionality.

Many software companies are trying to capitalize on the legacy of Kanban management. Some Kanban software providers offer the tools you need, but in an interface that is difficult to master. Others offer easy-to-use software that lacks the tools you need for maximum productivity and efficiency. Kanbanize provides the best system and Kanban cards for a simple reason: We offer a deep and powerful series of features in a user-friendly interface that allows for fast adoption.

Choose Kanbanize and enjoy a boost in productivity up to 300 percent. If you’d like to try our Kanban cards, take advantage of a free 30-day trial. You’ll quickly discover the advantages and benefits that Kanbanize can provide teams and companies of any size.

Get Started →

 

Join our family!
  • Continental Corporation
  • Mozilla
  • BCG Digital Ventures
  • PwC
  • Bose
  • Indiana University
  • Orange Business Services
  • GoDaddy
  • Arsenal Football Club
  • Roche Diagnostics

Always with you, on the go

Access all your projects and boards on the go with our mobile apps. View, create, update, delete and move cards, post comments and more with our mobile apps.