openapi: 3.0.3 info: title: Lacework API 2.0 Documentation description: >- The Lacework API documentation is available directly from your Lacework application at the following URI: `https://YourLacework.lacework.net/api/v2/docs`, where `YourLacework` is your Lacework application. No login to the Lacework Console is required. However, there is a link to the Lacework API 2.0 documentation from the Lacework Console. From the **Help** drop-down, select **API 2.0 Documentation**. All the Lacework API operations listed below require an API Access Token to allow access to the Lacework API. For more information about getting a temporary API Access Token to pass into these operations as a header, see https://www.laceworkplatform.com/generate-api-access-keys-and-tokens. You can run the Lacework APIs using your favorite REST API tools such as curl or Postman. Example curl commands are listed in the API 2.0 documentation provided by the **Help** > **API** 2.0 Documentation menu option in the Lacework Console. You can also run the Lacework API from the **Lacework CLI**. For more information, see [Get Started with the Lacework CLI](https://www.laceworkplatform.com/cli). termsOfService: https://www.laceworkplatform.com/terms-of-use/ contact: name: Lacework, Inc. url: https://www.laceworkplatform.com/contact email: info@lacework.net license: name: Lacework Use License url: https://www.laceworkplatform.com/terms-of-use/ version: '2.0' tags: - name: OVERVIEW x-displayName: Overview description: |-
| Status Code | Definition | Description |
|---|---|---|
| 200 | OK | The request has succeeded. |
| 201 | Created | The request has been fulfilled and resulted in a new resource being created. |
| 204 | No Content | The server has fulfilled the request but does not need to return an entity-body. |
| 400 | Bad Request | The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications. |
| 401 | Unauthorized | The request requires user authentication. If the request already included Authorization credentials, then the 401 response indicates that authorization has been refused for those credentials. |
| 403 | Forbidden | The server understood the request, but is refusing to fulfill it. Authorization will not fix the issue and the request SHOULD NOT be repeated. |
| 404 | Not Found | The server has not found anything matching the Request-URI. |
| 405 | Method Not Allowed | The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. |
| 409 | Conflict | The request could not be completed due to a conflict with the current state of the resource. |
| 429 | Too Many Requests | Too many requests occurred during the allotted time period and rate limiting was applied. |
| 500 | Internal Server Error | The request did not complete due to an internal error on the server side. The server encountered an unexpected condition which prevented it from fulfilling the request. |
| 503 | Service Unavailable | The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. |