Tickets API

A ticket is the unit of work on the AlgaPSA service desk. Use this API to create tickets, move them through your boards and statuses, assign them to technicians, and log comments, time, and files.

Before you create one

A ticket references a board, a status, a priority, and a client — all by ID. Resolve those first: statuses and priorities have their own lookups (GET /tickets/statuses and GET /tickets/priorities), while board and client IDs come from their own APIs. The Create a ticket guide walks through the full lookup-then-create flow.

curl https://algapsa.com/api/v1/tickets \
  -H "X-API-Key: $ALGA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "VPN down at the Northwind branch",
    "client_id": "cl_3f9a2c",
    "board_id": "bd_support",
    "status_id": "st_new",
    "priority_id": "pr_high"
  }'

Move it forward

Once a ticket exists, the rest happens through the sub-resources under /tickets/{id}: add notes with POST /comments, change where it sits with PUT /status, hand it off with PUT /assignment, and read logged effort from GET /time-entries. Files, documents, and materials hang off the same ticket.

Find tickets

List and filter with GET /tickets, run a text query with GET /tickets/search, or pull counts for a dashboard from GET /tickets/stats. To open a ticket straight from a piece of hardware, use POST /tickets/from-asset.

Bundle related tickets

When several tickets describe the same underlying issue, group them under one master ticket. Create the bundle with POST /tickets/{id}/bundle, choosing a sync mode of link_only to just link the children or sync_updates to propagate the master's changes to them. Adjust membership later with POST /tickets/{id}/bundle/children and DELETE /tickets/{id}/bundle/children/{childId}, hand the master role to another ticket with POST /tickets/{id}/bundle/promote, and change the sync mode through PUT /tickets/{id}/bundle/settings. Read a ticket's role (master, child, or standalone) and its full membership from GET /tickets/{id}/bundle, or break the whole group apart with DELETE /tickets/{id}/bundle.

Endpoints

Every endpoint links through to its full parameters, request and response schemas, and code samples.