logs

Get guard logs

Retrieve individual Guard request logs for your organization.

Returns up to limit logs (default 100, max 1000) ordered by timestamp ascending (oldest first). Only flagged results and message-level results are included in each log entry — unflagged detections are omitted.

Pagination. Use offset to page through results. When has_more is true in the response, increment offset by limit to fetch the next page. For example, to iterate over all logs in a time range with pages of 500: fetch with offset=0, then offset=500, then offset=1000, and so on until has_more is false.

Filtering. Narrow results using any combination of these filters:

  • flagged_only — only requests where the policy action flagged the request.

  • detected_only — only requests where at least one detector fired (includes monitor-mode hits where the policy does not flag).

  • detector_types — only requests that triggered one or more of the listed detector types. See the GetLogsRequest schema for the list of accepted values and their corresponding display names in the AI Guardrails Dashboard.

Authentication. Use a Platform API key from the AI Guardrails Dashboard — not the Guard API key used for inference requests at api.lakera.ai.

Access. This endpoint is available to select organizations. Contact your Check Point representative to request access. Community users may also reach out to support@lakera.ai.

post/v1-beta/logs

Request

  • Base URL: https://platform.lakera.ai/api
  • URL: https://platform.lakera.ai/api/v1-beta/logs
  • Auth: HTTP bearer

Request body

start_timestring date-time required

Start of the time range (inclusive)

end_timestring date-time required

End of the time range (exclusive). Must be after start_time.

project_idstring nullable

Filter to a single project by ID. Omit to return logs across all projects in your organization.

limitinteger

Maximum number of logs to return. Logs are ordered by timestamp ascending (oldest first).

offsetinteger

Number of logs to skip before returning results. Use with has_more in the response to page through large result sets: increment offset by limit until has_more is false.

flagged_onlyboolean

When true, only return requests where the policy action flagged the request. Independent of detected_only.

detected_onlyboolean

When true, only return requests where at least one detector fired. This includes monitor-mode requests where a detector fired but the policy did not flag. Independent of flagged_only.

detector_typesstring[]

Filter to requests that triggered one or more of the listed detector types. An empty list (the default) returns all requests regardless of detector.

Accepted values and their corresponding display names in the AI Guardrails Dashboard:

API valueDashboard display name
prompt_attackPrompt attack
data_leakageData leakage (matches all sub-detectors)
content_violationContent violation (matches all sub-detectors)
unknown_linksUnknown links
deny_listedDeny-listed
tool_access_controlTool access control (requires agentic policy feature — contact your Check Point representative to request access)
dangerous_deviationDangerous Deviation
custom_guardrailCustom guardrail
audio_prompt_attackAudio prompt attack
no_detectionsNo detections (requests where no detectors fired)

Response

Guard logs for the requested time range

has_moreboolean required

true when there are more logs beyond this page. Increment offset by limit and repeat the request to fetch the next page.

Changes

No recorded changes to this operation across all 1 revision of this API.