Skip to main content
GET
List issues
Returns the issues reported by your account, newest first. Only your own reports are visible — an API key never sees another customer’s issues.

Pagination

Paging is cursor-based. Make the first request without a cursor, then pass the nextCursor from each response as the cursor of the next request:
nextCursor is only returned when another page actually exists, so you can loop until it’s absent without ever fetching an empty page:
limit defaults to 50 and is capped at 100 — asking for more returns 100 rather than an error.

Filtering by date

from and to bound the report date inclusively, and each accepts either YYYY-MM-DD or a full RFC3339 timestamp. A bare to date covers that entire UTC day, so to=2026-08-31 includes issues reported at 23:59 that evening.
A date that parses as neither format returns 400, as does a from later than the to.

Authorizations

x-api-key
string
header
required

API key for authentication. Must start with dd- prefix.

Headers

x-api-key
string
default:dd-00000000000000000000000065c9cbfe
required

API Key

Query Parameters

limit
integer
default:50

Maximum issues to return per page. Values above 100 are capped at 100.

Required range: 1 <= x <= 100
cursor
string

The nextCursor value from a previous response. Omit to start from the newest issue.

from
string

Only return issues reported on or after this date. Accepts YYYY-MM-DD or an RFC3339 timestamp.

to
string

Only return issues reported on or before this date. Accepts YYYY-MM-DD or an RFC3339 timestamp; a bare date covers that entire UTC day.

Response

A page of issues

A page of issues reported by your account

issues
object[]

Issues on this page, newest first.

nextCursor
string

Pass as cursor to fetch the next page. Absent on the last page.