Endpoints
GET /api/applications/:foreignId/disclosure-registry
Lists all disclosure requests for the application. This is the administrator’s view of pending and historical requests — use it to see what auditors have submitted before taking an approve or close action. Required permission:cases:approve_creation (administrator bucket)
The application route segment returned by
GET /auth/me under applications[foreignId]. Identifies which application’s disclosure registry to read.GET /api/applications/:foreignId/cases
Lists approved cases and the auditor’s worklist for the application. Administrators see all cases; auditors see only the cases to which they are assigned and that are within their access window. Required permission:reports:view_transactions (auditor bucket) or administrator/case-specific checks
The application route segment from
GET /auth/me.access_days.
POST /api/applications/:foreignId/cases
Creates a new disclosure case request. The request enters apending state and must be reviewed by an application administrator before it becomes an active case. You can propose the auditors who should be assigned to the case at creation time.
Required permission: cases:create (auditor bucket)
The application route segment from
GET /auth/me.A plain-text explanation of why this disclosure is being requested. Shown to the administrator during review.
Start of the transaction period to disclose. ISO 8601 date string (e.g.
"2024-01-01").End of the transaction period to disclose. ISO 8601 date string (e.g.
"2024-03-31").Number of days from case approval during which assigned auditors may access the transaction data.
Controls which fields are disclosed if the request is approved. All flags default to
false if omitted.full_tx_ids— Include full transaction identifiers.sender_information— Include sender address and identity data.withdrawal_details— Include withdrawal amounts and destination details.
Array of user IDs to assign as auditors if the request is approved. These assignments are proposed at request time and carried over to the live case on approval.
id and an initial status of "pending".
POST /api/applications/:foreignId/cases/requests/:id/withdraw
Withdraws your own pending disclosure request before an administrator has acted on it. You can only withdraw requests that you created, and only while they are inpending status.
Required permission: cases:withdraw_pending_request (auditor bucket)
The application route segment from
GET /auth/me.The ID of the pending disclosure request to withdraw.
POST /api/applications/:foreignId/case-requests/:id/approve
Approves a pending disclosure request and creates an active case from it. Approval copies the proposed auditor assignments from the request to the live case and starts theaccess_days access window.
Required permission: cases:approve_creation (administrator bucket)
The application route segment from
GET /auth/me.The ID of the pending disclosure request to approve.
"approved" status.
POST /api/applications/:foreignId/case-requests/:id/close
Closes a pending disclosure request without granting data access. Use this to formally reject a request. The request moves to"closed" status and no case is created.
Required permission: cases:approve_creation (administrator bucket)
The application route segment from
GET /auth/me.The ID of the pending disclosure request to close.
status set to "closed".
Case Statuses
| Status | Meaning |
|---|---|
pending | The request has been submitted and is awaiting administrator review. Assigned auditors do not yet have data access. |
approved | An administrator has approved the request. An active case exists and assigned auditors can access transaction data within the approved scope and access window. |
closed | An administrator closed the request without granting access, or the request was withdrawn by the requester. No case was created. |
Once a request is
approved or closed, it cannot be re-opened. If you need to modify the scope of an approved case, create a new disclosure request.