Skip to main content
PATCH
Update an issue's state
Moves an issue through the review workflow. This is separate from PUT /issues/{id}, which edits the contents of a report — this endpoint only changes its state. You can only change the state of issues created by your own API key; anything else returns 404.

States

Setting state to rejected without a rejectionReason returns 400, as does any value outside the table above.

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

Path Parameters

id
string
required

Issue ID

Body

application/json

Payload for moving an issue to a new workflow state

state
enum<string>
required

State to move the issue to.

Available options:
open,
uploaded_for_correction,
in_progress,
resolved,
rejected
Example:

"resolved"

rejectionReason
string

Why the issue is being rejected. Required when state is rejected, ignored otherwise.

Example:

"not reproducible"

Response

Updated issue

Issue details

id
string
Example:

"iss_12345abcde"

state
enum<string>

Current state of the issue.

Available options:
open,
uploaded_for_correction,
in_progress,
resolved,
rejected
Example:

"open"

rejectionReason
string

Why the issue was rejected. Present only when state is rejected.

Example:

"duplicate report"

createdAt
string<date-time>
updatedAt
string<date-time>
generationId
string
generatedText
string
problemWord
string
voicePromptId
string
type
enum<string>

Category of problem being reported.

Available options:
hallucinations,
glossary
locale
string

Locale of the reported generation, when known.

Example:

"en-US"

additionalComments
string
problemSeconds
number
phoneticHeard
string

Phonetic transcription of how the word actually sounded

phoneticExpected
string

Phonetic transcription of how the word should sound