Skip to content
MelonforceAPI docs

Views

A board's saved views: a filter, sort and Group by with a name.

Create a view

POST/v1/boards/{boardId}/views

Adds a Table or Kanban view, placed last, with the default settings and whatever config names. A Kanban view needs nothing on the board: config.statusColumnId may name a live status column of the board, or be null (the default); any other column answers 400 INVALID_REQUEST. The filter, sort, Group by and column list may name only columns the board has, and the Group by cannot be on Name, a button or a column that holds several values (400 GROUPING_NOT_ALLOWED). A board holds at most 30 views.

Who can call: Any API key.

Path parameters

boardId

stringrequired

The board's ID.

  • Pattern ^brd_[0-9a-z]{21}$

Body

name

stringrequired

The view's name, 1 to 40 characters after trimming.

  • 1 to 40 characters
type

stringrequired

table or kanban. It cannot change later.

  • One of "table", "kanban"
config

objectoptional

The settings to start with. Name only the ones to set; each one left out takes its default: no filter, sort or Group by, no status column, every column shown in the board's order, and items open in the panel.

Show 6 fieldsHide 6 fields
filter

Filter or nulloptional

The view's saved filter, the same shape as the items query's filter. Null means none.

Show 2 fieldsHide 2 fields
join

stringrequired

How the entries combine: and when all must match, or when any one is enough.

  • One of "and", "or"
conditions

array of one of FilterCondition, FilterGrouprequired

Conditions and condition groups. A condition has column; a condition group has conditions. Up to 25 conditions in all, those in condition groups included, and up to 5 condition groups.

  • Up to 25 items
Show 2 optionsHide 2 options

One of:

FilterCondition

FilterCondition

One test on one column: column, operator and, except for is_empty and is_not_empty, value. Which operators a column takes depends on its type.

Show 11 optionsHide 11 options

One of:

operator: "is"

object

Show 3 fieldsHide 3 fields
column

stringrequired

The column ID to test. name is the Name column.

  • Pattern ^[a-z][a-z0-9_]{0,39}$
operator

stringrequired

  • Always "is"
value

FilterValuerequired

A plain value, Me on a person column, or a relative date on a date column. Text is matched ignoring ASCII case. A day tested against a column that includes a time means that whole day in timeZone.

Show 3 optionsHide 3 options

One of:

option 1

one of string, number

A label or option ID for status and dropdown, a user ID for person, text (up to 200 characters), a number, or a date as YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS.sssZ.

FilterMe

FilterMe

Me: the member making the request. Person columns only. An API key is not a person, so a key's query that holds Me answers QUERY_INVALID.

Show 1 fieldHide 1 field
type

stringrequired

  • Always "me"
FilterRelativeDate

FilterRelativeDate

A range of days worked out when the query runs, in timeZone. Date columns only. is means inside it, is_not outside it, greater_than after its end and less_than before its start.

Show 2 fieldsHide 2 fields
type

stringrequired

  • Always "relative_date"
value

stringrequired

The range. Weeks start on Monday; last_7_days and next_7_days include today.

  • One of "today", "yesterday", "tomorrow", "this_week", "last_week", "next_week", "this_month", "last_month", "last_7_days", "last_30_days", "next_7_days", "next_30_days"
operator: "is_not"

object

Show 3 fieldsHide 3 fields
column

stringrequired

The column ID to test. name is the Name column.

  • Pattern ^[a-z][a-z0-9_]{0,39}$
operator

stringrequired

  • Always "is_not"
value

FilterValuerequired

A plain value, Me on a person column, or a relative date on a date column. Text is matched ignoring ASCII case. A day tested against a column that includes a time means that whole day in timeZone.

Same options as value in Create a view

operator: "is_any_of"

object

Show 3 fieldsHide 3 fields
column

stringrequired

The column ID to test. name is the Name column.

  • Pattern ^[a-z][a-z0-9_]{0,39}$
operator

stringrequired

  • Always "is_any_of"
value

array of FilterValuerequired

1 to 25 values, each as for is.

  • 1 to 25 items

Same options as value in Create a view

operator: "is_none_of"

object

Show 3 fieldsHide 3 fields
column

stringrequired

The column ID to test. name is the Name column.

  • Pattern ^[a-z][a-z0-9_]{0,39}$
operator

stringrequired

  • Always "is_none_of"
value

array of FilterValuerequired

1 to 25 values, each as for is.

  • 1 to 25 items

Same options as value in Create a view

operator: "is_empty"

object

Show 2 fieldsHide 2 fields
column

stringrequired

The column ID to test. name is the Name column.

  • Pattern ^[a-z][a-z0-9_]{0,39}$
operator

stringrequired

  • Always "is_empty"
operator: "is_not_empty"

object

Show 2 fieldsHide 2 fields
column

stringrequired

The column ID to test. name is the Name column.

  • Pattern ^[a-z][a-z0-9_]{0,39}$
operator

stringrequired

  • Always "is_not_empty"
operator: "contains"

object

Show 3 fieldsHide 3 fields
column

stringrequired

The column ID to test. name is the Name column.

  • Pattern ^[a-z][a-z0-9_]{0,39}$
operator

stringrequired

  • Always "contains"
value

stringrequired

Text to look for, 1 to 200 characters, ignoring ASCII case.

  • 1 to 200 characters
operator: "does_not_contain"

object

Show 3 fieldsHide 3 fields
column

stringrequired

The column ID to test. name is the Name column.

  • Pattern ^[a-z][a-z0-9_]{0,39}$
operator

stringrequired

  • Always "does_not_contain"
value

stringrequired

Text to look for, 1 to 200 characters, ignoring ASCII case.

  • 1 to 200 characters
operator: "greater_than"

object

Show 3 fieldsHide 3 fields
column

stringrequired

The column ID to test. name is the Name column.

  • Pattern ^[a-z][a-z0-9_]{0,39}$
operator

stringrequired

  • Always "greater_than"
value

one of string, number, FilterRelativeDaterequired

A number, a date, or a relative date.

Show 2 optionsHide 2 options

One of:

option 1

one of string, number

A label or option ID for status and dropdown, a user ID for person, text (up to 200 characters), a number, or a date as YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS.sssZ.

FilterRelativeDate

FilterRelativeDate

A range of days worked out when the query runs, in timeZone. Date columns only. is means inside it, is_not outside it, greater_than after its end and less_than before its start.

Show 2 fieldsHide 2 fields
type

stringrequired

  • Always "relative_date"
value

stringrequired

The range. Weeks start on Monday; last_7_days and next_7_days include today.

  • One of "today", "yesterday", "tomorrow", "this_week", "last_week", "next_week", "this_month", "last_month", "last_7_days", "last_30_days", "next_7_days", "next_30_days"
operator: "less_than"

object

Show 3 fieldsHide 3 fields
column

stringrequired

The column ID to test. name is the Name column.

  • Pattern ^[a-z][a-z0-9_]{0,39}$
operator

stringrequired

  • Always "less_than"
value

one of string, number, FilterRelativeDaterequired

A number, a date, or a relative date.

Show 2 optionsHide 2 options

One of:

option 1

one of string, number

A label or option ID for status and dropdown, a user ID for person, text (up to 200 characters), a number, or a date as YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS.sssZ.

FilterRelativeDate

FilterRelativeDate

A range of days worked out when the query runs, in timeZone. Date columns only. is means inside it, is_not outside it, greater_than after its end and less_than before its start.

Show 2 fieldsHide 2 fields
type

stringrequired

  • Always "relative_date"
value

stringrequired

The range. Weeks start on Monday; last_7_days and next_7_days include today.

  • One of "today", "yesterday", "tomorrow", "this_week", "last_week", "next_week", "this_month", "last_month", "last_7_days", "last_30_days", "next_7_days", "next_30_days"
operator: "between"

object

Show 3 fieldsHide 3 fields
column

stringrequired

The column ID to test. name is the Name column.

  • Pattern ^[a-z][a-z0-9_]{0,39}$
operator

stringrequired

  • Always "between"
value

objectrequired

A range of numbers or dates. Both ends are inside it.

Show 2 fieldsHide 2 fields
from

one of string, numberrequired

The low end, inside the range.

to

one of string, numberrequired

The high end, inside the range.

FilterGroup

FilterGroup

A condition group inside a filter, with its own join. It holds conditions only, not other condition groups.

Show 2 fieldsHide 2 fields
join

stringrequired

How the entries combine: and when all must match, or when any one is enough.

  • One of "and", "or"
conditions

array of FilterConditionrequired

1 to 25 conditions.

  • 1 to 25 items

Same options as FilterCondition in Create a view

sort

Sortoptional

The view's saved sort, the same shape as the items query's sort. Empty means none.

  • Up to 5 items
Show 2 fieldsHide 2 fields
column

stringrequired

The column ID to sort by. name is the Name column. A button column cannot be sorted.

  • Pattern ^[a-z][a-z0-9_]{0,39}$
direction

stringrequired

asc for ascending, desc for descending.

  • One of "asc", "desc"
group

GroupBy or nulloptional

The view's saved Group by, the same shape as the items query's group. Null means none. Name cannot be grouped by (400 GROUPING_NOT_ALLOWED); a Group by on Name saved before that stays as it is, and the view runs as if it had none.

Show 3 fieldsHide 3 fields
column

stringrequired

The column ID to group by. It must hold one value: not a button, not the Name column, and not a person or dropdown column that allows several.

  • Pattern ^[a-z][a-z0-9_]{0,39}$
direction

stringrequired

The order of the sections. The section of empty cells is always last.

  • One of "asc", "desc"
showEmpty

booleanoptional

True to list every label or option that no matching item has too, with a count of 0, in the column's order (reversed for desc). For status and dropdown columns; other types ignore it. Left out means false. It adds sections to the counts only; the items are the same.

statusColumnId

string or nulloptional

The status column a Kanban view groups its cards by: a live status column of the board, or null. Null means the view has not picked one; the app then uses the board's indexed status column, then its first status column. A Table view ignores it.

  • Pattern ^[a-z][a-z0-9_]{0,39}$
columns

array of objectoptional

How each column shows, in the order shown: up to 61 entries (the board's 60 columns and Name), each column once, and only columns the board has. A board column left out shows after the listed ones, visible, at the default width.

  • Up to 61 items
Show 4 fieldsHide 4 fields
id

stringrequired

The column's ID. name is the Name column.

  • Pattern ^[a-z][a-z0-9_]{0,39}$
hidden

booleanrequired

True hides the column in this view. The Name column cannot be hidden.

width

integer or nullrequired

The column's width in pixels, 48 to 1,200. Null is the default width.

  • 48 to 1,200
wrap

booleanrequired

True wraps long text in the column's cells.

openIn

stringoptional

Whether items open in the side panel (panel, the default) or as a full page (page). Stored; it has no effect yet.

  • One of "panel", "page"

Answer201 Created

view

Viewrequired

The view as the board shows it now. Its column list leaves out columns the board no longer has.

Show 8 fieldsHide 8 fields
id

stringrequired

The view's ID: viw_ and 21 characters from 0-9 and a-z.

  • Pattern ^viw_[0-9a-z]{21}$
boardId

stringrequired

The ID of the board the view belongs to.

  • Pattern ^brd_[0-9a-z]{21}$
name

stringrequired

The view's name, up to 40 characters.

type

stringrequired

table or kanban. It never changes.

  • One of "table", "kanban"
position

integerrequired

The view's place in the board's tab order, lowest first. The numbers can have gaps.

  • At least 0
config

ViewConfigrequired

A view's settings: its saved filter, sort and Group by, a Kanban view's status column, the column layout, and where items open.

Show 6 fieldsHide 6 fields
filter

Filter or nulloptional

The view's saved filter, the same shape as the items query's filter. Null means none.

Same fields as filter in Create a view

sort

Sortoptional

The view's saved sort, the same shape as the items query's sort. Empty means none.

  • Up to 5 items
Show 2 fieldsHide 2 fields
column

stringrequired

The column ID to sort by. name is the Name column. A button column cannot be sorted.

  • Pattern ^[a-z][a-z0-9_]{0,39}$
direction

stringrequired

asc for ascending, desc for descending.

  • One of "asc", "desc"
group

GroupBy or nulloptional

The view's saved Group by, the same shape as the items query's group. Null means none. Name cannot be grouped by (400 GROUPING_NOT_ALLOWED); a Group by on Name saved before that stays as it is, and the view runs as if it had none.

Show 3 fieldsHide 3 fields
column

stringrequired

The column ID to group by. It must hold one value: not a button, not the Name column, and not a person or dropdown column that allows several.

  • Pattern ^[a-z][a-z0-9_]{0,39}$
direction

stringrequired

The order of the sections. The section of empty cells is always last.

  • One of "asc", "desc"
showEmpty

booleanoptional

True to list every label or option that no matching item has too, with a count of 0, in the column's order (reversed for desc). For status and dropdown columns; other types ignore it. Left out means false. It adds sections to the counts only; the items are the same.

statusColumnId

string or nullrequired

The status column a Kanban view groups its cards by: a live status column of the board, or null. Null means the view has not picked one; the app then uses the board's indexed status column, then its first status column. A Table view ignores it.

  • Pattern ^[a-z][a-z0-9_]{0,39}$
columns

array of objectrequired

How each column shows, in the order shown: up to 61 entries (the board's 60 columns and Name), each column once, and only columns the board has. A board column left out shows after the listed ones, visible, at the default width.

  • Up to 61 items
Show 4 fieldsHide 4 fields
id

stringrequired

The column's ID. name is the Name column.

  • Pattern ^[a-z][a-z0-9_]{0,39}$
hidden

booleanrequired

True hides the column in this view. The Name column cannot be hidden.

width

integer or nullrequired

The column's width in pixels, 48 to 1,200. Null is the default width.

  • 48 to 1,200
wrap

booleanrequired

True wraps long text in the column's cells.

openIn

stringrequired

Whether items open in the side panel (panel, the default) or as a full page (page). Stored; it has no effect yet.

  • One of "panel", "page"
createdAt

stringrequired

When the view was made, in ISO 8601 (UTC).

  • Format date-time (ISO 8601)
updatedAt

stringrequired

When the view's name or settings were last written, in ISO 8601 (UTC). Every PATCH moves it, even one that changes nothing; a new order does not.

  • Format date-time (ISO 8601)

Errors

INVALID_REQUEST

400 Bad Request

The body, a query parameter or the Idempotency-Key does not match its schema, or the request names something the board does not have or allow, such as a column order that is not every column once or the board's last view to delete. An ID in the path that is not shaped like one answers 404 instead. Some refusals carry details.reason, which says why, and details.field, which names the field when one is at fault.

QUERY_INVALID

400 Bad Request

The query names a column the board lacks, an operator or value that does not fit its column, a column that cannot be sorted, or Me, which a key cannot use (sent, or in a saved view). Or the query is too large to run as one statement. Most answers say where in details.issues.

GROUPING_NOT_ALLOWED

400 Bad Request

The query, or a view's group, groups by Name, by a column that holds no value (a button) or by one that allows several values. An items query sent as fields and a view's create or update answer it; with other problems besides, they answer QUERY_INVALID. A saved view run by its ID leaves such a grouping out instead. details.issues names it.

UNAUTHENTICATED

401 Unauthorized

No key was sent, or the key does not work: the header is not Bearer <key>, the key is from another environment, unknown, revoked or expired, or its maker is no longer an owner or admin or its workspace is not active. The answer is the same in every case; when the request had an Authorization header, it comes with WWW-Authenticate: Bearer.

NOT_FOUND

404 Not Found

There is no such board, column, view, group, item or update in the key's workspace (another workspace's counts as none, and so does another board's group in the path), or it was deleted while the request ran. A restore of a board, column or group that is not in the trash answers it too. Nothing is written.

LIMIT_REACHED

409 Conflict

A limit is full: a board's columns or views, its live groups (at most 50, on a group create or restore), or the values a type change would convert. details.limit names it and details.max gives the cap.

PAYLOAD_TOO_LARGE

413 Content Too Large

The body is over its route's size limit. A save of notes with too many characters answers it too, with details.limit notes and details.max.

RATE_LIMITED

429 Too Many Requests

Too many calls in the last 60 seconds: by the key, by its workspace's keys together, or from your address with keys that do not work. Only keys of the right shape count against your address; a header or key of the wrong shape answers 401 and is not counted. Send it again after Retry-After seconds.

With Retry-After: 10, the seconds to wait before sending again.

INTERNAL

500 Internal Server Error

Something went wrong on our side. Try again later.

Example

Request
curl -X POST "https://api.melonforce.com/v1/boards/brd_4f8k2n7q1w9e3r6t5y0u2/views" \
  -H "Authorization: Bearer $MELONFORCE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "name": "Pipeline",
  "type": "kanban",
  "config": {
    "statusColumnId": "status",
    "sort": [
      {
        "column": "move_date",
        "direction": "asc"
      }
    ]
  }
}'
201 Created
{
  "view": {
    "id": "viw_7d3g5k8n2q4t6w9y1a0e5",
    "boardId": "brd_4f8k2n7q1w9e3r6t5y0u2",
    "name": "Pipeline",
    "type": "kanban",
    "position": 1,
    "config": {
      "filter": null,
      "sort": [
        {
          "column": "move_date",
          "direction": "asc"
        }
      ],
      "group": null,
      "statusColumnId": "status",
      "columns": [],
      "openIn": "panel"
    },
    "createdAt": "2026-11-18T14:05:12.412Z",
    "updatedAt": "2026-11-18T14:05:12.412Z"
  }
}

Order the views

POST/v1/boards/{boardId}/views/order

Sets the board's tab order. Send every view ID of the board, each once, in the order to show; a missing, extra, repeated or unknown ID answers 400 INVALID_REQUEST and changes nothing. No view's updatedAt moves.

Who can call: Any API key.

Path parameters

boardId

stringrequired

The board's ID.

  • Pattern ^brd_[0-9a-z]{21}$

Body

viewIds

array of stringrequired

Every view ID of the board, each once, in the order to show.

  • At least 1 item

Answer200 OK

views

array of Viewrequired

The board's views in their new order.

Same fields as view in Create a view

Errors

INVALID_REQUEST

400 Bad Request

The body, a query parameter or the Idempotency-Key does not match its schema, or the request names something the board does not have or allow, such as a column order that is not every column once or the board's last view to delete. An ID in the path that is not shaped like one answers 404 instead. Some refusals carry details.reason, which says why, and details.field, which names the field when one is at fault.

UNAUTHENTICATED

401 Unauthorized

No key was sent, or the key does not work: the header is not Bearer <key>, the key is from another environment, unknown, revoked or expired, or its maker is no longer an owner or admin or its workspace is not active. The answer is the same in every case; when the request had an Authorization header, it comes with WWW-Authenticate: Bearer.

NOT_FOUND

404 Not Found

There is no such board, column, view, group, item or update in the key's workspace (another workspace's counts as none, and so does another board's group in the path), or it was deleted while the request ran. A restore of a board, column or group that is not in the trash answers it too. Nothing is written.

PAYLOAD_TOO_LARGE

413 Content Too Large

The body is over its route's size limit. A save of notes with too many characters answers it too, with details.limit notes and details.max.

RATE_LIMITED

429 Too Many Requests

Too many calls in the last 60 seconds: by the key, by its workspace's keys together, or from your address with keys that do not work. Only keys of the right shape count against your address; a header or key of the wrong shape answers 401 and is not counted. Send it again after Retry-After seconds.

With Retry-After: 10, the seconds to wait before sending again.

INTERNAL

500 Internal Server Error

Something went wrong on our side. Try again later.

Example

Request
curl -X POST "https://api.melonforce.com/v1/boards/brd_4f8k2n7q1w9e3r6t5y0u2/views/order" \
  -H "Authorization: Bearer $MELONFORCE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "viewIds": [
    "viw_7d3g5k8n2q4t6w9y1a0e5",
    "viw_2h6j9m3p5s8v1x4z7c0b6"
  ]
}'
200 OK
{
  "views": [
    {
      "id": "viw_7d3g5k8n2q4t6w9y1a0e5",
      "boardId": "brd_4f8k2n7q1w9e3r6t5y0u2",
      "name": "Pipeline",
      "type": "kanban",
      "position": 0,
      "config": {
        "filter": null,
        "sort": [
          {
            "column": "move_date",
            "direction": "asc"
          }
        ],
        "group": null,
        "statusColumnId": "status",
        "columns": [],
        "openIn": "panel"
      },
      "createdAt": "2026-11-18T14:05:12.412Z",
      "updatedAt": "2026-11-18T14:05:12.412Z"
    },
    {
      "id": "viw_2h6j9m3p5s8v1x4z7c0b6",
      "boardId": "brd_4f8k2n7q1w9e3r6t5y0u2",
      "name": "Table",
      "type": "table",
      "position": 1,
      "config": {
        "filter": null,
        "sort": [],
        "group": null,
        "statusColumnId": null,
        "columns": [
          {
            "id": "name",
            "hidden": false,
            "width": 280,
            "wrap": false
          },
          {
            "id": "origin",
            "hidden": false,
            "width": null,
            "wrap": true
          },
          {
            "id": "destination",
            "hidden": false,
            "width": null,
            "wrap": true
          }
        ],
        "openIn": "panel"
      },
      "createdAt": "2026-11-02T09:14:03.218Z",
      "updatedAt": "2026-11-10T16:41:27.905Z"
    }
  ]
}

Update a view

PATCH/v1/boards/{boardId}/views/{viewId}

Changes the name and the settings. Each setting named replaces the stored one whole, and the others stay. Only what the request names is checked against the board's live columns, so a stored setting that names a deleted column never blocks a change elsewhere. A group it names cannot be by Name (400 GROUPING_NOT_ALLOWED); a Group by on Name saved before that stays until it is changed. A view's type cannot change.

Who can call: Any API key.

Path parameters

boardId

stringrequired

The board's ID.

  • Pattern ^brd_[0-9a-z]{21}$
viewId

stringrequired

The view's ID.

  • Pattern ^viw_[0-9a-z]{21}$

Body

Name at least one of name and config.

name

stringoptional

A new name, 1 to 40 characters after trimming.

  • 1 to 40 characters
config

objectoptional

The settings to change. Each one named replaces the stored one whole; the others stay as they are.

Same fields as config in Create a view

Answer200 OK

view

Viewrequired

The view as the board shows it now. Its column list leaves out columns the board no longer has.

Same fields as view in Create a view

Errors

INVALID_REQUEST

400 Bad Request

The body, a query parameter or the Idempotency-Key does not match its schema, or the request names something the board does not have or allow, such as a column order that is not every column once or the board's last view to delete. An ID in the path that is not shaped like one answers 404 instead. Some refusals carry details.reason, which says why, and details.field, which names the field when one is at fault.

QUERY_INVALID

400 Bad Request

The query names a column the board lacks, an operator or value that does not fit its column, a column that cannot be sorted, or Me, which a key cannot use (sent, or in a saved view). Or the query is too large to run as one statement. Most answers say where in details.issues.

GROUPING_NOT_ALLOWED

400 Bad Request

The query, or a view's group, groups by Name, by a column that holds no value (a button) or by one that allows several values. An items query sent as fields and a view's create or update answer it; with other problems besides, they answer QUERY_INVALID. A saved view run by its ID leaves such a grouping out instead. details.issues names it.

UNAUTHENTICATED

401 Unauthorized

No key was sent, or the key does not work: the header is not Bearer <key>, the key is from another environment, unknown, revoked or expired, or its maker is no longer an owner or admin or its workspace is not active. The answer is the same in every case; when the request had an Authorization header, it comes with WWW-Authenticate: Bearer.

NOT_FOUND

404 Not Found

There is no such board, column, view, group, item or update in the key's workspace (another workspace's counts as none, and so does another board's group in the path), or it was deleted while the request ran. A restore of a board, column or group that is not in the trash answers it too. Nothing is written.

PAYLOAD_TOO_LARGE

413 Content Too Large

The body is over its route's size limit. A save of notes with too many characters answers it too, with details.limit notes and details.max.

RATE_LIMITED

429 Too Many Requests

Too many calls in the last 60 seconds: by the key, by its workspace's keys together, or from your address with keys that do not work. Only keys of the right shape count against your address; a header or key of the wrong shape answers 401 and is not counted. Send it again after Retry-After seconds.

With Retry-After: 10, the seconds to wait before sending again.

INTERNAL

500 Internal Server Error

Something went wrong on our side. Try again later.

Example

Request
curl -X PATCH "https://api.melonforce.com/v1/boards/brd_4f8k2n7q1w9e3r6t5y0u2/views/viw_7d3g5k8n2q4t6w9y1a0e5" \
  -H "Authorization: Bearer $MELONFORCE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "config": {
    "filter": {
      "join": "and",
      "conditions": [
        {
          "column": "move_date",
          "operator": "is",
          "value": {
            "type": "relative_date",
            "value": "next_30_days"
          }
        }
      ]
    }
  }
}'
200 OK
{
  "view": {
    "id": "viw_7d3g5k8n2q4t6w9y1a0e5",
    "boardId": "brd_4f8k2n7q1w9e3r6t5y0u2",
    "name": "Pipeline",
    "type": "kanban",
    "position": 0,
    "config": {
      "filter": {
        "join": "and",
        "conditions": [
          {
            "column": "move_date",
            "operator": "is",
            "value": {
              "type": "relative_date",
              "value": "next_30_days"
            }
          }
        ]
      },
      "sort": [
        {
          "column": "move_date",
          "direction": "asc"
        }
      ],
      "group": null,
      "statusColumnId": "status",
      "columns": [],
      "openIn": "panel"
    },
    "createdAt": "2026-11-18T14:05:12.412Z",
    "updatedAt": "2026-11-18T14:22:48.031Z"
  }
}

Delete a view

DELETE/v1/boards/{boardId}/views/{viewId}

Removes the view for good. A board's last view cannot go: 400 INVALID_REQUEST with details.reason last_view. Once the board is deleted, its views stay for the board's restore, and this answers 404.

Who can call: Any API key.

Path parameters

boardId

stringrequired

The board's ID.

  • Pattern ^brd_[0-9a-z]{21}$
viewId

stringrequired

The view's ID.

  • Pattern ^viw_[0-9a-z]{21}$

Answer200 OK

An empty object, {}.

Errors

INVALID_REQUEST

400 Bad Request

The body, a query parameter or the Idempotency-Key does not match its schema, or the request names something the board does not have or allow, such as a column order that is not every column once or the board's last view to delete. An ID in the path that is not shaped like one answers 404 instead. Some refusals carry details.reason, which says why, and details.field, which names the field when one is at fault.

UNAUTHENTICATED

401 Unauthorized

No key was sent, or the key does not work: the header is not Bearer <key>, the key is from another environment, unknown, revoked or expired, or its maker is no longer an owner or admin or its workspace is not active. The answer is the same in every case; when the request had an Authorization header, it comes with WWW-Authenticate: Bearer.

NOT_FOUND

404 Not Found

There is no such board, column, view, group, item or update in the key's workspace (another workspace's counts as none, and so does another board's group in the path), or it was deleted while the request ran. A restore of a board, column or group that is not in the trash answers it too. Nothing is written.

RATE_LIMITED

429 Too Many Requests

Too many calls in the last 60 seconds: by the key, by its workspace's keys together, or from your address with keys that do not work. Only keys of the right shape count against your address; a header or key of the wrong shape answers 401 and is not counted. Send it again after Retry-After seconds.

With Retry-After: 10, the seconds to wait before sending again.

INTERNAL

500 Internal Server Error

Something went wrong on our side. Try again later.

Example

Request
curl -X DELETE "https://api.melonforce.com/v1/boards/brd_4f8k2n7q1w9e3r6t5y0u2/views/viw_7d3g5k8n2q4t6w9y1a0e5" \
  -H "Authorization: Bearer $MELONFORCE_API_KEY"
200 OK
{}