Skip to main content

​
Goal

Use the public API to move from an open finding to a documented investigation.

​
Prerequisites

  • A read or admin key for reads.
  • A write or admin key for assignment and notes.
  • An issue ID from GET /v1/issues.

​
List open issues

cURL
The public API supports open, resolved, and resolved_late. It does not support acknowledged or investigating.

​
Inspect one issue

cURL
Read the category, message, opened time, resolved time, and current assignee.

​
Read linked evidence

cURL
Compare event time, received time, type, amount, and reference. The received time helps you tell a late event from a missing event.

​
Find an assignee

cURL
Use the returned member ID. The response does not include email addresses.

​
Assign the issue

cURL
Send {"assigned_to":null} to remove the assignment. Assignment is a set-to-value operation, so you do not need an idempotency header.

​
Add a note safely

cURL
The header is optional. Use it when a client may retry after a timeout. The same key and request replay the original note. The same key with a different issue or body returns 409 idempotency_conflict.

​
Handle resolved-late findings

resolved_late means the expected evidence arrived after the deadline. Keep the issue in your audit workflow even though the evidence eventually arrived.

​
Protect sensitive data

Do not log bearer tokens, full event payloads, note bodies, amounts, or customer identifiers. Store only the request ID and a redacted error when you need support. See the generated issue operations for exact request and response fields.