Projects and Boards API

The Projects module (Monday-style boards) organizes work into boards with groups, typed columns, and items. The REST API lets you automate task creation from other systems — for example, creating an item when a ticket comes in or a CRM deal is won.

Requirements

• The workspace must have the projects_enabled plan feature; without it these endpoints return 403.
• A Bearer token for the workspace.

Main endpoints

• GET/POST /api/v1/boards — list or create boards.
• GET /api/v1/boards/column-types — available column types (text, status, person, date, number, etc.).
• POST /api/v1/boards/{board}/groups — create a group (section) inside the board.
• POST /api/v1/boards/{board}/columns — add a column.
• POST /api/v1/boards/{board}/items — create an item (task).
• PUT /api/v1/boards/items/{item}/columns/{column} — update a column's value on an item.
• PATCH /api/v1/boards/items/{item}/move — move an item between groups.
• POST /api/v1/boards/items/{item}/subitems — create subitems.

Example: create an item on a board

curl -X POST "https://app.omnifox.io/api/v1/boards/8/items" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
        "title": "Prepare sales proposal",
        "group_id": 22,
        "contact_id": 55
      }'

An item can carry contact_id and/or deal_id to link it to a contact or a CRM deal.

Tips

• Call GET /api/v1/boards/{board}/view to pull the whole board (groups, columns, and items) in a single request — great for external dashboards.
• Board automations (/api/v1/boards/{board}/automations) can create or move items on their own when an event fires; check the catalog with GET .../automations/catalog before building a new rule.

Troubleshooting

• 403 on /boards/*: the workspace's plan doesn't include Projects.
• The column rejects the value you send: each column type (status, person, date…) expects a different payload shape; check GET /api/v1/boards/column-types for the exact schema.
• The item doesn't move to a new group: use PATCH .../move (not PUT) and include the destination group_id.