"Deprecation": "Tue, 31 Dec 2024 23:59:59 GMT",
"Link": "New version of API link; rel=\"alternate\"",
"Sunset": "Mon, 31 Mar 2025 23:59:59 GMT"

"openapi: 3.0.1\ninfo:\n title: Audit\n description: >\n Audit log records are detailed information about actions and events, which can be provided by any service. For some pre-defined events services always create audit records and the Audit Service\n always saves them. Audit records have a lifespan of 30 days, after which they will be discarded.\n\n\n **Base path change and deprecation notice**\n\n\n The base path for the Audit APIs is changing (from `/api/audit-service` to `/api/audit`). The `/api/audit-service/` base path will continue to function until `Mon, 31 Mar 2025 23:59:59 GMT`.\n\n\n Additionally, several endpoints are being deprecated. Endpoints that are being deprecated include additional properties in response headers:\n\n\n ```\n\n \"Deprecation\": \"Tue, 31 Dec 2024 23:59:59 GMT\",\n\n \"Link\": \"New version of API link; rel=\\\"alternate\\\"\",\n\n \"Sunset\": \"Mon, 31 Mar 2025 23:59:59 GMT\"\n\n ```\n\n\n * `Deprecation`: The date and time when a resource will be deprecated. After this date, the resource may be removed from future versions of the API.\n\n * `Link`: A link to a supported endpoint that replicates the functionality of a deprecated one.\n\n * `Sunset`: The date and time when a resource will be removed, and no longer be available.\n\n\n * `Note`: Media type names used in Polaris APIs were renamed and no longer include “synopsys”.\n Although media types that include “synopsys” were removed from the API specifications, existing endpoints will continue to support them until September 1, 2025.\n Please update your scripts to use the new media types.\n contact:\n name: Black Duck Software, Inc.\n url: https://polaris.blackduck.com\n version: 1.0.0\nservers:\n - url: https://polaris.blackduck.com\ntags:\n - name: Records\n description: Contains APIs to get or export audit log records.\n - name: Event Types\n description: Contains API to get information about supported event types.\n - name: Logs\n description: Contains APIs to get or export audit log records.\n - name: Categories\n description: Contains API to get information about supported audit categories.\nsecurity:\n - ApiKeyAuth: []\npaths:\n /api/audit-service/records:\n get:\n tags:\n - Records\n summary: Get audit log records.\n description: >-\n Audit log records can be filtered by the optional parameters in the following section. If filter parameters are not specified, all the records are returned. Otherwise, records matching all the\n filter criteria are returned.\n operationId: getRecordsDeprecated\n parameters:\n - name: eventType\n in: query\n description: |\n Filters records by audit event type. The **eventType** query parameter value is case sensitive. \\\n If the **eventType** does not match any event type, the API will return an empty list. \\\n Example event-types are `Entitlement Offer`, and `Subscription` etc. \\\n Refer `Event Types (/event-types)` API to discover the available event types.\n schema:\n type: string\n example: User Events\n - name: event\n in: query\n description: |\n Filters records by audit event name. The **event** query parameter is case sensitive. \\\n If the **event** name does not match any event, the API will return an empty list. \\\n Example event names are `Logged in`, `Subscription created`, and `Assessment created`.\n schema:\n type: string\n example: Logged In\n - name: startDate\n in: query\n description: >-\n Filters records by the time when an event occurred. You can filter events by only the date or by the date and also the time. Accepted formats are `yyyy-MM-dd`, `yyyy-MM-dd\n HH:mm:ss.SSSSSS`, `yyyy-MM-dd HH:mm:ss.SSSSS`, `yyyy-MM-dd HH:mm:ss.SSSS`, `yyyy-MM-dd HH:mm:ss.SSS`, `yyyy-MM-dd HH:mm:ss.SS`, and `yyyy-MM-dd HH:mm:ss.S`. If `startDate` is specified,\n records for events that occurred on or after the `startDate` will be returned. If not specified, all the records will be returned. Examples are `2022-01-01 01:01:01.1`, `2022-01-01`, and\n `2022-01-01 01:01:01.123456`.\n schema:\n type: string\n example: '2022-01-01 01:01:01.123456'\n - name: endDate\n in: query\n description: >-\n Filters records by the time when events occurred. You can filter events by only the date or by the date and also the time. Accepted formats are `yyyy-MM-dd`, `yyyy-MM-dd HH:mm:ss.SSSSSS`,\n `yyyy-MM-dd HH:mm:ss.SSSSS`, `yyyy-MM-dd HH:mm:ss.SSSS`, `yyyy-MM-dd HH:mm:ss.SSS`, `yyyy-MM-dd HH:mm:ss.SS`, and `yyyy-MM-dd HH:mm:ss.S`. If `endDate` is specified, records for events\n that occurred on or before the `endDate` will be returned. If not specified, all the records will be returned.\n schema:\n type: string\n example: '2022-01-01 01:01:01.123456'\n - name: user\n in: query\n description: Filters records by the user who performed the action. There is no default value for this field. If not specified, records for all users can be returned.\n schema:\n type: string\n example: testuser\n - name: search\n in: query\n description: |\n Filters audit logs based on the contents of their message. \n It allows for case-insensitive partial matching against the messages of audit logs. \\\n Returns the audit logs that contain the provided **search** string in the audit log message.\n If no match is found, it will return an empty list. \\\n The search filter ignores the common english words like `a`, `and`, `the` etc, and special characters like `&` and `|` etc and searches for the remaining words in the message.\n\n **E.g:** If the message is `User logged in`, and the search query is `search=logged`, the audit log will be returned.\n schema:\n type: string\n example: Logged In\n - name: _offset\n in: query\n description: Return results, starting (inclusive) from a given numerical (0-based) offset within the response.\n schema:\n type: integer\n default: 0\n example: 0\n - name: _limit\n in: query\n description: Restrict the number of results provided to an upper bound of the given limit.\n schema:\n type: integer\n default: 25\n example: 25\n responses:\n '200':\n description: Success. A paged list of records will be returned.\n content:\n application/vnd.audit-service.records-1+json:\n schema:\n $ref: '#/components/schemas/Records'\n '400':\n description: Bad request\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Bad request\n status: 400\n detail: Request cannot be processed, as the passed queryParameter is not recognised\n '401':\n description: User is not authorized\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Unauthorized\n status: 401\n detail: Operation is not permitted\n '403':\n description: Forbidden\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Forbidden\n status: 403\n detail: Access denied, cannot access the requested resource\n '404':\n description: Not found\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Not found\n status: 404\n detail: Requested resource is not found\n '405':\n description: Method Not Allowed\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Method Not Allowed\n status: 405\n detail: Request method is not supported\n '500':\n description: Internal Server Error\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Internal Server Error\n status: 500\n detail: Internal Server Error\n deprecated: true\n /api/audit/logs:\n get:\n tags:\n - Logs\n summary: Get audit log records.\n description: >-\n Audit log records can be filtered by the optional parameters in the following section. If filter parameters are not specified, all the records are returned. Otherwise, records matching all the\n filter criteria are returned.\n operationId: getLogRecords\n parameters:\n - name: category\n in: query\n description: |\n Filters records by audit activity category. The **category** query parameter value is case sensitive. \\\n If the **category** does not match any audit activity category, the API will return an empty list. \\\n Example categories are `Entitlement Offer`, and `Subscription` etc. \\\n Refer **Categories (/categories)** API to discover the available audit activity categories.\n schema:\n type: string\n example: User Events\n - name: event\n in: query\n description: |\n Filters records by audit event name. The **event** query parameter is case sensitive. \\\n If the **event** name does not match any event, the API will return an empty list. \\\n Example event names are `Logged in`, `Subscription created`, and `Assessment created`.\n schema:\n type: string\n example: Logged In\n - name: startDate\n in: query\n description: >-\n Filters records by the time when an event occurred. You can filter events by only the date or by the date and also the time. Accepted formats are `yyyy-MM-dd`, `yyyy-MM-dd\n HH:mm:ss.SSSSSS`, `yyyy-MM-dd HH:mm:ss.SSSSS`, `yyyy-MM-dd HH:mm:ss.SSSS`, `yyyy-MM-dd HH:mm:ss.SSS`, `yyyy-MM-dd HH:mm:ss.SS`, and `yyyy-MM-dd HH:mm:ss.S`. If `startDate` is specified,\n records for events that occurred on or after the `startDate` will be returned. If not specified, all the records will be returned. Examples are `2022-01-01 01:01:01.1`, `2022-01-01`, and\n `2022-01-01 01:01:01.123456`.\n schema:\n type: string\n example: '2022-01-01 01:01:01.123456'\n - name: endDate\n in: query\n description: >-\n Filters records by the time when events occurred. You can filter events by only the date or by the date and also the time. Accepted formats are `yyyy-MM-dd`, `yyyy-MM-dd HH:mm:ss.SSSSSS`,\n `yyyy-MM-dd HH:mm:ss.SSSSS`, `yyyy-MM-dd HH:mm:ss.SSSS`, `yyyy-MM-dd HH:mm:ss.SSS`, `yyyy-MM-dd HH:mm:ss.SS`, and `yyyy-MM-dd HH:mm:ss.S`. If `endDate` is specified, records for events\n that occurred on or before the `endDate` will be returned. If not specified, all the records will be returned.\n schema:\n type: string\n example: '2022-01-01 01:01:01.123456'\n - name: user\n in: query\n description: Filters records by the user who performed the action. There is no default value for this field. If not specified, records for all users can be returned.\n schema:\n type: string\n example: testuser\n - name: search\n in: query\n description: |\n Filters audit logs based on the contents of their message. \n It allows for case-insensitive partial matching against the messages of audit logs. \\\n Returns the audit logs that contain the provided **search** string in the audit log message.\n If no match is found, it will return an empty list. \\\n The search filter ignores the common english words like `a`, `and`, `the` etc, and special characters like `&` and `|` etc and searches for the remaining words in the message.\n\n **E.g:** If the message is `User logged in`, and the search query is `search=logged`, the audit log will be returned.\n schema:\n type: string\n example: Logged In\n - name: _offset\n in: query\n description: Return results, starting (inclusive) from a given numerical (0-based) offset within the response.\n schema:\n type: integer\n default: 0\n example: 0\n - name: _limit\n in: query\n description: Restrict the number of results provided to an upper bound of the given limit.\n schema:\n type: integer\n default: 25\n example: 25\n responses:\n '200':\n description: Success. A paged list of log records will be returned.\n content:\n application/vnd.polaris.audit.logs-1+json:\n schema:\n $ref: '#/components/schemas/LogRecords'\n '400':\n description: Bad request\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Bad request\n status: 400\n detail: Request cannot be processed, as the passed queryParameter is not recognised\n '401':\n description: User is not authorized\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Unauthorized\n status: 401\n detail: Operation is not permitted\n '403':\n description: Forbidden\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Forbidden\n status: 403\n detail: Access denied, cannot access the requested resource\n '404':\n description: Not found\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Not found\n status: 404\n detail: Requested resource is not found\n '405':\n description: Method Not Allowed\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Method Not Allowed\n status: 405\n detail: Request method is not supported\n '500':\n description: Internal Server Error\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Internal Server Error\n status: 500\n detail: Internal Server Error\n /api/audit-service/records/export:\n get:\n tags:\n - Records\n summary: Export audit log records as CSV.\n description: >-\n Exports audit records to a CSV file. Records can be filtered by the optional parameters in the following section. If no filtering parameters are specified, all the records are returned.\n Otherwise records matching all the criteria are returned.\n operationId: exportRecordsDeprecated\n parameters:\n - name: eventType\n in: query\n description: Filters records by event type. Example event-types are `Entitlement Offer`, and `Subscription`. You can use the *Event Types API* to discover the available types.\n schema:\n type: string\n example: User Events\n - name: event\n in: query\n description: Filters records by action name. Example actions are `Logged in`, `Subscription created`, and `Assessment created`.\n schema:\n type: string\n example: Logged In\n - name: startDate\n in: query\n description: >-\n Filters records by the time when an event occurred. You can filter events by only the date or by the date and also the time. Accepted formats are `yyyy-MM-dd`, `yyyy-MM-dd\n HH:mm:ss.SSSSSS`, `yyyy-MM-dd HH:mm:ss.SSSSS`, `yyyy-MM-dd HH:mm:ss.SSSS`, `yyyy-MM-dd HH:mm:ss.SSS`, `yyyy-MM-dd HH:mm:ss.SS`, and `yyyy-MM-dd HH:mm:ss.S`. If `startDate` is specified,\n records for events that occurred on or after the `startDate` will be returned. If not specified, all the records will be returned. Examples are `2022-01-01 01:01:01.1`, `2022-01-01`, and\n `2022-01-01 01:01:01.123456`.\n schema:\n type: string\n example: '2022-01-01 01:01:01.123456'\n - name: endDate\n in: query\n description: >-\n Filters records by the time when events occurred. You can filter events by only the date or by the date and also the time. Accepted formats are `yyyy-MM-dd`, `yyyy-MM-dd HH:mm:ss.SSSSSS`,\n `yyyy-MM-dd HH:mm:ss.SSSSS`, `yyyy-MM-dd HH:mm:ss.SSSS`, `yyyy-MM-dd HH:mm:ss.SSS`, `yyyy-MM-dd HH:mm:ss.SS`, and `yyyy-MM-dd HH:mm:ss.S`. If `endDate` is specified, records for events\n that occurred on or before the `endDate` will be returned. If not specified, all the records will be returned.\n schema:\n type: string\n example: '2022-01-01 01:01:01.123456'\n - name: user\n in: query\n description: Filters records by the user who performed the action. There is no default value for this field. If not specified, records of all users can be returned.\n schema:\n type: string\n example: testuser\n - name: search\n in: query\n description: Filters records by the message strings they contain.\n schema:\n type: string\n example: Logged In\n responses:\n '200':\n description: Success. A CSV file containing audit records will be returned.\n content:\n text/csv:\n schema:\n type: string\n '400':\n description: Bad request\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Bad request\n status: 400\n detail: Request cannot be processed, as the passed queryParameter is not recognised\n '401':\n description: User is not authorized\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Unauthorized\n status: 401\n detail: Operation is not permitted\n '403':\n description: Forbidden\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Forbidden\n status: 403\n detail: Access denied, cannot access the requested resource\n '404':\n description: Not found\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Not found\n status: 404\n detail: Requested resource is not found\n '405':\n description: Method Not Allowed\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Method Not Allowed\n status: 405\n detail: Request method is not supported\n '500':\n description: Internal Server Error\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Internal Server Error\n status: 500\n detail: Internal Server Error\n deprecated: true\n /api/audit/logs/export:\n get:\n tags:\n - Logs\n summary: Export audit log records as CSV.\n description: >-\n Exports audit log records to a CSV file. Log records can be filtered by the optional parameters in the following section. If no filtering parameters are specified, all the records are\n returned. Otherwise records matching all the criteria are returned.\n operationId: exportLogRecords\n parameters:\n - name: category\n in: query\n description: >-\n Filters log records by audit activity category. Example audit categories are `Entitlement Offer`, and `Subscription`. You can use the **Categories (/categories)** API to discover the\n available categories.\n schema:\n type: string\n example: User Events\n - name: event\n in: query\n description: Filters records by action name. Example actions are 'Logged in', `Subscription created`, and `Assessment created`.\n schema:\n type: string\n example: Logged In\n - name: startDate\n in: query\n description: >-\n Filters records by the time when an event occurred. You can filter events by only the date or by the date and also the time. Accepted formats are `yyyy-MM-dd`, `yyyy-MM-dd\n HH:mm:ss.SSSSSS`, `yyyy-MM-dd HH:mm:ss.SSSSS`, `yyyy-MM-dd HH:mm:ss.SSSS`, `yyyy-MM-dd HH:mm:ss.SSS`, `yyyy-MM-dd HH:mm:ss.SS`, and `yyyy-MM-dd HH:mm:ss.S`. If `startDate` is specified,\n records for events that occurred on or after the `startDate` will be returned. If not specified, all the records will be returned. Examples are `2022-01-01 01:01:01.1`, `2022-01-01`, and\n `2022-01-01 01:01:01.123456`.\n schema:\n type: string\n example: '2022-01-01 01:01:01.123456'\n - name: endDate\n in: query\n description: >-\n Filters records by the time when events occurred. You can filter events by only the date or by the date and also the time. Accepted formats are `yyyy-MM-dd`, `yyyy-MM-dd HH:mm:ss.SSSSSS`,\n `yyyy-MM-dd HH:mm:ss.SSSSS`, `yyyy-MM-dd HH:mm:ss.SSSS`, `yyyy-MM-dd HH:mm:ss.SSS`, `yyyy-MM-dd HH:mm:ss.SS`, and `yyyy-MM-dd HH:mm:ss.S`. If `endDate` is specified, records for events\n that occurred on or before the `endDate` will be returned. If not specified, all the records will be returned.\n schema:\n type: string\n example: '2022-01-01 01:01:01.123456'\n - name: user\n in: query\n description: Filters records by the user who performed the action. There is no default value for this field. If not specified, records of all users can be returned.\n schema:\n type: string\n example: testuser\n - name: search\n in: query\n description: Filters log records by the message strings they contain.\n schema:\n type: string\n example: Logged In\n responses:\n '200':\n description: Success. A CSV file containing audit log records will be returned.\n content:\n text/csv:\n schema:\n type: string\n '400':\n description: Bad request\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Bad request\n status: 400\n detail: Request cannot be processed, as the passed queryParameter is not recognised\n '401':\n description: User is not authorized\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Unauthorized\n status: 401\n detail: Operation is not permitted\n '403':\n description: Forbidden\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Forbidden\n status: 403\n detail: Access denied, cannot access the requested resource\n '404':\n description: Not found\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Not found\n status: 404\n detail: Requested resource is not found\n '405':\n description: Method Not Allowed\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Method Not Allowed\n status: 405\n detail: Request method is not supported\n '500':\n description: Internal Server Error\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Internal Server Error\n status: 500\n detail: Internal Server Error\n /api/audit-service/event-types:\n get:\n description: Description Needed\n tags:\n - Event Types\n summary: Get available event types.\n operationId: getEventTypesDeprecated\n parameters:\n - name: _offset\n in: query\n description: Return results, starting (inclusive) from a given numerical (0-based) offset within the response.\n schema:\n type: integer\n default: 0\n example: 0\n - name: _limit\n in: query\n description: Restrict the number of results provided to an upper bound of the given limit.\n schema:\n type: integer\n default: 25\n example: 25\n responses:\n '200':\n description: Success. A paged list of records will be returned.\n content:\n application/vnd.audit-service.event-types-1+json:\n schema:\n $ref: '#/components/schemas/eventTypes'\n '400':\n description: Bad request\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Bad request\n status: 400\n detail: Request cannot be processed, as the passed queryParameter is not recognised\n '401':\n description: User is not authorized\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Unauthorized\n status: 401\n detail: Operation is not permitted\n '403':\n description: Forbidden\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Forbidden\n status: 403\n detail: Access denied, cannot access the requested resource\n '404':\n description: Not found\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Not found\n status: 404\n detail: Requested resource is not found\n '405':\n description: Method Not Allowed\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Method Not Allowed\n status: 405\n detail: Request method is not supported\n '500':\n description: Internal Server Error\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Internal Server Error\n status: 500\n detail: Internal Server Error\n deprecated: true\n /api/audit/categories:\n get:\n description: Categories of events that can be audited. This API returns the list of available categories.\n tags:\n - Categories\n summary: Get available event types.\n operationId: getAuditCategories\n parameters:\n - name: _offset\n in: query\n description: Return results, starting (inclusive) from a given numerical (0-based) offset within the response.\n schema:\n type: integer\n default: 0\n example: 0\n - name: _limit\n in: query\n description: Restrict the number of results provided to an upper bound of the given limit.\n schema:\n type: integer\n default: 25\n example: 25\n responses:\n '200':\n description: Success. A paged list of categories will be returned.\n content:\n application/vnd.polaris.audit.categories-1+json:\n schema:\n $ref: '#/components/schemas/Categories'\n '400':\n description: Bad request\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Bad request\n status: 400\n detail: Request cannot be processed, as the passed queryParameter is not recognised\n '401':\n description: User is not authorized\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Unauthorized\n status: 401\n detail: Operation is not permitted\n '403':\n description: Forbidden\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Forbidden\n status: 403\n detail: Access denied, cannot access the requested resource\n '404':\n description: Not found\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Not found\n status: 404\n detail: Requested resource is not found\n '405':\n description: Method Not Allowed\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Method Not Allowed\n status: 405\n detail: Request method is not supported\n '500':\n description: Internal Server Error\n content:\n '*/*':\n schema:\n $ref: '#/components/schemas/ErrorResponse'\n example:\n title: Internal Server Error\n status: 500\n detail: Internal Server Error\ncomponents:\n securitySchemes:\n ApiKeyAuth:\n type: apiKey\n in: header\n name: Api-Token\n schemas:\n ErrorResponse:\n properties:\n status:\n type: integer\n description: The HTTP status code generated by the origin server for this occurrence of the problem.\n example: 404\n title:\n type: string\n description: A short, human-readable summary of the problem type. It SHOULD NOT change from occurrence to occurrence of the problem type, except for purposes of localization.\n example: Resource not found\n errors:\n type: array\n items:\n $ref: '#/components/schemas/Error'\n description: Collection of error items that contains detailed information about failures.\n detail:\n type: string\n description: A human-readable explanation specific to this occurrence of the problem.\n Error:\n type: object\n properties:\n details:\n type: string\n description: A localized, human-readable explanation specific to this occurrence of the problem.\n example: The requested resource could not be found.\n eventTypes:\n type: object\n properties:\n _items:\n type: array\n items:\n $ref: '#/components/schemas/eventTypeV1Resource'\n description: Collection of event types.\n _links:\n $ref: '#/components/schemas/links'\n _collection:\n $ref: '#/components/schemas/collection'\n deprecated: true\n Records:\n type: object\n properties:\n _items:\n type: array\n items:\n $ref: '#/components/schemas/recordV1Resource'\n description: Collection of audit records.\n _links:\n $ref: '#/components/schemas/links'\n _collection:\n $ref: '#/components/schemas/collection'\n deprecated: true\n eventTypeV1Resource:\n allOf:\n - type: string\n properties:\n _type:\n type: string\n description: The type of a single resource\n example: type\n - type: object\n properties:\n _links:\n $ref: '#/components/schemas/links'\n - type: object\n properties:\n id:\n type: string\n description: Unique ID of the event type.\n example: 9f1b397a-55fe-4980-a19e-9afea69ec98e\n name:\n type: string\n description: Name of the event type.\n example: Assessment Audit\n description:\n type: string\n description: Brief description of the event type.\n example: Assessment Audit\n deprecated: true\n recordV1Resource:\n allOf:\n - type: string\n properties:\n _type:\n type: string\n description: The type of a single resource\n example: type\n - type: object\n properties:\n _links:\n $ref: '#/components/schemas/links'\n - type: object\n properties:\n id:\n type: string\n description: Unique ID of the audit record.\n example: f6b4944e-87ce-11ec-a8a3-0242ac120002\n actionName:\n type: string\n description: Name of the action performed by the user.\n example: Logged in, Logged out, Assessment created etc.\n categoryName:\n type: string\n description: Name of the category the action belongs to.\n example: User Events, Assessment Audit etc.\n message:\n type: string\n description: Detailed information about the events.\n example: New assessment created. Assessment name assessment1\n user:\n type: string\n description: Username of the user by whom the action was triggered.\n example: exampleuser1@example.com\n actionAt:\n type: string\n description: Date and Time of the event.\n example: '2022-08-10 12:45:27.245'\n clientIP:\n type: string\n description: IP of the client machine where the event occurred.\n example: 127.0.0.1, 192.18.0.1\n organizationId:\n type: string\n description: The ID of the organization from where the event came from\n example: 60db54c9-d6bd-47d7-94ca-4cf90521311d\n organizationName:\n type: string\n description: The name of the organization from where the event came from\n example: myorg\n deprecated: true\n Categories:\n type: object\n properties:\n _items:\n type: array\n items:\n $ref: '#/components/schemas/categoryV1Resource'\n description: Collection of audit categories.\n _links:\n $ref: '#/components/schemas/links'\n _collection:\n $ref: '#/components/schemas/collection'\n LogRecords:\n type: object\n properties:\n _items:\n description: Collection of audit log records.\n type: array\n items:\n $ref: '#/components/schemas/logRecordV1Resource'\n _links:\n $ref: '#/components/schemas/links'\n _collection:\n $ref: '#/components/schemas/collection'\n logRecordV1Resource:\n allOf:\n - type: string\n properties:\n _type:\n type: string\n description: The type of a single resource\n example: type\n - type: object\n properties:\n _links:\n $ref: '#/components/schemas/links'\n - type: object\n properties:\n id:\n type: string\n description: Unique ID of the audit log record.\n example: f6b4944e-87ce-11ec-a8a3-0242ac120002\n actionName:\n type: string\n description: Name of the action performed by the user.\n example: Logged in, Logged out, Assessment created etc.\n categoryName:\n type: string\n description: Name of the category the action belongs to.\n example: User Events, Assessment Audit etc.\n message:\n type: string\n description: Detailed information about the events.\n example: New assessment created. Assessment name assessment1\n user:\n type: string\n description: Username of the user by whom the action was triggered.\n example: exampleuser1@example.com\n actionAt:\n type: string\n description: Date and Time of the event.\n example: '2022-08-10 12:45:27.245'\n clientIP:\n type: string\n description: IP of the client machine where the event occurred.\n example: 127.0.0.1, 192.18.0.1\n organizationId:\n type: string\n description: The ID of the organization from where the event came from\n example: 60db54c9-d6bd-47d7-94ca-4cf90521311d\n organizationName:\n type: string\n description: The name of the organization from where the event came from\n example: myorg\n categoryV1Resource:\n allOf:\n - type: string\n properties:\n _type:\n type: string\n description: The type of a single resource\n example: type\n - type: object\n properties:\n _links:\n $ref: '#/components/schemas/links'\n - type: object\n properties:\n id:\n type: string\n description: Unique ID of the category.\n example: 9f1b397a-55fe-4980-a19e-9afea69ec98e\n name:\n type: string\n description: Name of the category.\n example: Assessment Audit\n description:\n type: string\n description: Brief description of the category.\n example: Assessment Audit\n links:\n type: array\n description: An array of links that can be followed for further information about this resource.\n items:\n type: object\n description: link that can be followed for further information about this resource.\n properties:\n href:\n type: string\n format: uri\n description: The URI to follow for this reference.\n example: https://example.com/api/audit/logs?_offset=0&_limit=25\n rel:\n type: string\n format: rel\n example: previous\n description: The relation name. The relation names used for pagination are `self`, `first`, `last`, `previous`, and `next`.\n method:\n type: string\n example: GET\n description: The HTTP method to use while following this reference.\n collection:\n type: object\n description: It contains information about the number of items in the response, total number of actual audit records, number of pages.\n properties:\n itemCount:\n type: integer\n description: The total length of the collection. An empty result has an itemCount of 0.\n example: 100\n currentPage:\n type: integer\n description: The current page number of the results (one-based), given the current offset and limit settings. An empty result does not have a current page.\n example: 3\n pageCount:\n type: integer\n description: The number of pages in the collection, given the current limit settings. An empty result has a pageCount of 0.\n example: 3\n type:\n type: string\n description: The type of the resource collection\n example: type\n"

{}