A board groups tickets and sets the defaults they inherit: which category and priority model applies, who gets new work, and whether the live timer runs. Tickets reference a board by ID, so most integrations resolve or create one here first.
Only board_name is required. The two fields worth setting deliberately are category_type and priority_type: each is either custom or itil, and the choice decides whether the board uses your own categories and priorities or the ITIL model. Set is_default to make this the board new tickets land on, and default_assigned_to to auto-assign them.
curl https://algapsa.com/api/v1/boards \
-H "X-API-Key: $ALGA_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"board_name": "Network Operations",
"category_type": "itil",
"priority_type": "itil",
"is_default": false,
"enable_live_ticket_timer": true
}'List every board with GET /boards to map names to IDs, or fetch one with GET /boards/{id}. Adjust defaults, the ITIL display toggles, or the assignee through PUT /boards/{id}. Retire a board you no longer route to by setting is_inactive; delete it outright with DELETE /boards/{id} only when nothing still references it.
Every endpoint links through to its full parameters, request and response schemas, and code samples.
GET/api/v1/boardsAlgaPSAAlgaDeskList boardsPOST/api/v1/boardsAlgaPSAAlgaDeskCreate boardGET/api/v1/boards/{id}AlgaPSAAlgaDeskGet board by IDPUT/api/v1/boards/{id}AlgaPSAAlgaDeskUpdate boardDELETE/api/v1/boards/{id}AlgaPSAAlgaDeskDelete board