Skip to main content
List the requests you can see, with simple filters and pagination. A request can gather members, an assignee and a topic, and link statements. You only see the requests you have access to — those you’re a member of, plus any shared with you. Rows are ordered by most recent activity first (last modification date). Each row exposes a resource_url that opens that single request. The result also carries a list-level application_url that reopens the requests board on the same view and status tab you just queried. Because the board is always scoped to one status tab, this link needs a status; it is null without one, and null when the served set matches no single board view.

​
Parameters

Body

​
string
Either a built-in token — “assigned_to_me” or “my_requests” (the ones you created) — or the id of a request view shared with you, never its name. Omitted: every request you can access.
​
string
Free-text filter matched against the request name, its full id, or its reference (the # reference shown in the UI is the last 8 characters of the id; a leading # is accepted).
​
string
Status filter. One of open or closed. One of: open, closed.
​
integer
Page size, between 1 and 250. Defaults to 50.
​
integer
Row offset into the result set — the number of rows to skip before this page. Any offset >= 0 is accepted; it does not have to be a multiple of limit, so you can start from an arbitrary row. Pass the next_offset returned by the previous call to walk the pages, or None for the first page.

​
Response

Body

​
object[]
​
integer
​
string
Deep link that reproduces this list in the web app — the requests board opened on the served view and status tab. Null when status was omitted (the board shows one status tab at a time, so a link cannot faithfully reproduce a multi-status result), and null when the served set matches no single board view.