> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/connected-insights/resources-and-references/a-introduction/a-audit-logs-api.md).

# Audit Log APIs

## Audit Log APIs

Use this API to get the Audit Log information in Connected Insights. Search audit logs for cases, subjects, samples, analysis, etc.<br>

1. On the API page, navigate to the AuditLog section.
2. Select **GET /als/api/v1/auditlogs/search**.
3. In the Parameters table, update the description for the following applicable parameters:<br>
   * **caseId** — The displayed case ID (for example, ILM-ABC-234) or the ID for the case (for example, `https://{domain}.connectedinsights.illumina.com/interpretation/{caseId}/reports/{reportId}/overview`).
   * **userDisplayId** — The email of a user's Connected Insights account (for example, <esong@company.com>).
   * **entityId** — The ID of a specific Case, Sample, Subject, or Analysis.
   * **entityType** — A type of entity. An entity is something within Connected Insights (e.g., `user` or `subject`). Refer to the the complete list of Entity Types below.
   * **eventName** — A type of event that occurred in Connected Insights (e.g., `case.added` or `molecular-data.deleted`). Refer to the the complete list of Event Names below.
   * **toDate** — Include audit log entries created on and before this date. This date is in the yyyy-MM-dd'T'HH:flag\_mm:ss'Z' format (for example, 2021-01-30T08:30:00Z).
   * **fromDate** — Include audit log entries created on and after this date. This date is in the yyyy-MM-dd'T'HH:flag\_mm:ss'Z' format (for example, 2021-01-30T08:30:00Z).
   * **pageNumber** — The specific page number of the API response.
   * **pageSize** — The size of each page in the API response.
4. Select **Execute**.

## List of searchable Entity Types:

* actionability-classifications
* assertion
* biomarker
* case
* cli-log
* custom-annotation
* custom-case-data
* data-upload
* disease-configuration
* domain
* filter
* flag-groups
* ici-uploader
* molecular-data
* pipeline-configuration
* preferred-transcript
* qc-configuration
* report
* report-automation
* report-category
* report-footer
* report-summary
* report-template
* sample
* subject

## List of searchable Event Names:

* case.added
* case.analysis.linked
* case.assertion.updated
* case.biomarker.status.updated
* case.deleted
* case.disease.added
* case.disease.updated
* case.metadata.added
* case.metadata.updated
* case.molecular-data.added
* case.report.added
* case.report.deleted
* case.report.json.viewed
* case.report.pdf.viewed
* case.report.status.reset
* case.sample.added
* case.status.updated
* case.subject.added
* case.subject.updated
* case.tags.updated
* case.updated
* case.viewed
* domain.project.added
* file.metadata.added
* file.metadata.error
* file.metadata.processed
* file.metadata.processing
* ici.uploader.downloaded
* molecular-data.added
* molecular-data.cloud.ingestion.added
* molecular-data.deleted
* molecular-data.updated
* sample.metadata.added
* sample.metadata.updated
* subject.deleted
* subject.metadata.added
* subject.metadata.updated
* subject.renamed
* subject.transferred


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.bioinsight.illumina.com/connected-insights/resources-and-references/a-introduction/a-audit-logs-api.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.