Skip to content

List work item types ​

GET/api/v2/workspaces/{slug}/projects/{project_id}/work-item-types/

Return the work item types available in a project as a paginated list. This is how you resolve a type name such as Bug to the type_id you send when creating a work item, and how you build a type picker that stays in sync with the project's configuration.

Reading types is unaffected by work item type mode. A project in workspace mode still lists the types imported into it here, so a read integration never has to branch on mode.

Path Parameters ​

slug:requiredstring

The workspace slug. It appears in your Plane URLs — in https://app.plane.so/my-team/projects/, the slug is my-team.

project_id:requiredstring (uuid)

The project whose work item types you want to list.

Query Parameters ​

Neither order_by nor paginate is validated — check your spelling, because both fail silently. An unrecognized order_by value falls back to the default ordering, and anything other than paginate=cursor uses offset pagination. A typo surfaces as an unexpected sort order or envelope, not as an error.

Ordering ​

order_by:optionalstring

Field to sort by. Prefix with - for descending.

  • level , -level — the type hierarchy level
  • name , -name — alphabetical
  • created_at , -created_at — when each type was added
  • id , -id

Order by level when you are rendering types to a user; it is the order the project itself uses.

Pagination ​

per_page:optionalinteger

Page size. Defaults to 50, maximum 200. Most projects define a handful of types, so one page is usually the whole set.

offset:optionalinteger

Number of rows to skip from the start of the result set. Maximum 10000. Read the next value from the response rather than computing offsets yourself.

paginate:optionalstring

Set to cursor to opt into the COUNT-free keyset envelope, which returns next_cursor and has_more instead of next and total_count. Omit it for the default offset envelope.

count:optionalboolean

Defaults to true. Set to false to skip the COUNT(*) behind total_count; the field is then omitted from the response.

Response shaping ​

fields:optionalstring

Comma-separated list of fields to return on each row. Unrequested keys are omitted from the response, not returned as null, so absent means "not requested" and null means "actually null". id always comes back whether or not you name it.

Pass all for every requestable field. An unknown name is a 400 that lists the valid set and suggests the closest match, so a typo can't silently cost you the saving.

Requestable here: created_at, description, id, is_active, is_default, is_epic, level, logo_props, name.

See Sparse fields.

Scopes ​

projects.work_item_types:read

Errors ​

StatusCodeCause
401unauthorizedMissing or invalid credentials.
402payment_requiredThe feature this endpoint belongs to isn't enabled on your plan, or is switched off.
403forbiddenYour role or token scope can't read this project's work item types.
404not_foundNo such workspace or project, or it's outside your tenant.
406not_acceptableThe Accept header asks for a representation the API can't produce.
429rate_limitedThrottled. Honor the Retry-After header before retrying.
List work item types
bash
curl -X GET \
  "https://api.plane.so/api/v2/workspaces/my-team/projects/4af68566-94a4-4eb3-94aa-50dc9427067b/work-item-types/?order_by=level&per_page=50" \
  -H "X-Api-Key: $PLANE_API_KEY"
Response200
json
{
  "data": [
    {
      "id": "9c2f8e51-4a63-47d8-b1e0-5f7a2c40d693",
      "name": "Task",
      "description": "Default work item type with the option to add new properties",
      "is_active": true,
      "is_default": true,
      "is_epic": false,
      "level": 0,
      "logo_props": {
        "in_use": "icon",
        "icon": {
          "name": "Check",
          "background_color": "#1FA191"
        }
      },
      "created_at": "2026-01-14T09:22:41.478363Z"
    },
    {
      "id": "d1e7a4c9-2b58-4f36-9a0e-7c3b5d81f240",
      "name": "Bug",
      "description": "Something is broken and needs a fix",
      "is_active": true,
      "is_default": false,
      "is_epic": false,
      "level": 0,
      "logo_props": {
        "in_use": "icon",
        "icon": {
          "name": "AlertCircle",
          "background_color": "#EF5974"
        }
      },
      "created_at": "2026-01-14T09:24:03.117482Z"
    }
  ],
  "next": null,
  "previous": null,
  "total_count": 2,
  "pagination": {
    "style": "offset"
  }
}
Response200
json
{
  "data": [
    {
      "id": "9c2f8e51-4a63-47d8-b1e0-5f7a2c40d693",
      "name": "Task",
      "description": "Default work item type with the option to add new properties",
      "is_active": true,
      "is_default": true,
      "is_epic": false,
      "level": 0,
      "logo_props": {
        "in_use": "icon",
        "icon": {
          "name": "Check",
          "background_color": "#1FA191"
        }
      },
      "created_at": "2026-01-14T09:22:41.478363Z"
    }
  ],
  "next_cursor": "b3A9MTcx",
  "has_more": true,
  "pagination": {
    "style": "cursor"
  }
}

An empty list is a real answer

A project that has never called enable returns an empty data array rather than an error. Treat "no types" as "the feature has not been turned on for this project yet", not as a failure.

Listing does not tell you what a type accepts

The list gives you names and ids. To find out which fields and custom properties a work item of a given type takes, call Get a work item type schema with that type's id.