openapi: 3.1.0 info: title: InsightAppSec Accounts Vulnerability Exception API description: '
Welcome to the reference documentation for the public APIs available for InsightAppSec.
Here are a few resources to help you learn how to start using our APIs:
After you''ve got the basics down, you can use this API guide to find examples of requests and responses.
This API uses the platform role of a user''s API key to inherit a set of permissions.
Notes:
| Role | Permissions | |
|---|---|---|
| Product Admin | Manage AppsRead Attack TemplatesManage TargetsManage Scan ConfigsManage ScansManage VulnerabilitiesAdminister Vulnerability CommentsManage EnginesManage Engine GroupsManage SchedulesManage BlackoutsManage Global BlackoutsManage FilesManage TagsManage PDF Report | |
| Read Write | Manage AppsRead Attack TemplatesRead TargetsManage Scan ConfigsManage ScansManage VulnerabilitiesManage Vulnerability CommentsRead EnginesRead Engine GroupsManage SchedulesManage BlackoutsManage FilesManage TagsManage PDF Report | |
| Read Only | Read AppsRead Attack TemplatesRead TargetsRead Scan ConfigsRead ScansRead VulnerabilitiesRead Vulnerability CommentsRead EnginesRead Engine GroupsRead SchedulesRead BlackoutsRead FilesRead TagsRead PDF Report |
| Parameter | Description | Example |
|---|---|---|
index | The 0-based index of the page of data desired (default: 0) | ?index=2 |
size | The size of the page of data desired (min: 1, max: 1000, default: 50) | ?size=10 |
sort | The sort terms and (optional) directions for the desired ordering of data (default: specific to each resource) | ?sort=scan.submit_time,DESC,scan.status |
page-token | The page token, used as an alternative to | ?page-token=NDM0NTk0NTIyOjo6X1M6OjpiYW5hbmFz |
When intending to page beyond the 10,000th result, or as an alternative to using the index query parameter, the page-token option may be used instead. After retrieving the first page, the page_token will be present in the metadata section of the response.
For example, with size=99, index=0 to index=99 may be used. To load the next page, use the page_token value used in the response e.g. ?page-token=NDM0NTk0NTIyO
As is generally the accepted practice with REST-ful APIs, creating a resource can be performed by sending an appropriately formatted POST request. Any ID provided for a new resource in a POST request body will simply be ignored (and a new one generated internally and returned as part of the resource in subsequent GET requests), and POST requests to URLs following a format similar to .../resource/ are unsupported and should respond with 415 Method Not Allowed. All requests which successfully create a resource and respond with 201 Created will contain a Location header the value of which is an absolute URI for the resource (the ID of which can be determined as the last section of the path in the given URI). For example:Location: https://us.api.insight.rapid7.com/ias/v1/scans/12345678-1234-5678-90AB-1234567890AB
The value of date and date-time type properties are fixed to the common ISO-8601 format. Unless otherwise specified, all date or date-time data in response bodies are expressed in UTC, and it is also expected that data provided in request bodies are also expressed in UTC.
The first_start and first_end properties of both Blackouts and Schedules, and the last_start property of Blackouts may be specified with a timezone. If the timezone is not specified, it is assumed to be UTC. For example:2019-08-12T14:00:00.000000Z[Asia/Tokyo]
It is also possible to specify the timezone as an offset of either GMT or UTC. For example:2019-09-04T15:00:00.000000Z[GMT+03:00]
| Value | Format | Notes |
|---|---|---|
| Date | YYYY-MM-DD | Defaults to 12 am UTC (if used for a date & time) |
| Date & time only | YYYY-MM-DD''T''hh:mm:ss[.nnn] | Defaults to UTC |
| Date & time in UTC | YYYY-MM-DD''T''hh:mm:ss[.nnn]Z | |
| Date & time with specific timezone | YYYY-MM-DD''T''hh:mm:ss[.nnn]Z[TimeZoneId] |
One characteristic of a powerful API is support for complex search and filtering of resources using a flexible query language. It is entirely possible to provide basic search and filtering functionality on standard GET resource collection operations using HTTP query parameters, but this becomes restrictive when attempting to encode boolean logic. Other solutions are also possible but come with equally restrictive compromises. The most effective way to facilitate this complex search and filtering is to provide it as a top-level API with a robust Domain-Specific Language (DSL).
For simple data retrieval that supports paging and sorting functionality, use the traditional resource-specific GET collection operations; for more complex data retrieval that supports a user-crafted query DSL, use the global Search operation.
Any response from the API with an HTTP Status Code in the 4xx or 5xx range indicates an error. If in the 4xx range it indicates a client-side error, where in the 5xx range it indicates a server-side error. All responses indicating an error should be JSON formatted, and contain both a "status" and a "message" property indicating the cause of the error, a "r7-correlation-id" header should also always be returned in the format of a UUID, which uniquely identifies the HTTP exchange that took place and caused the error (this header is present on every request). On some occasions, an "error_code" property will be included in the response body, which can provide the support team further context into the cause of the error in cases where the message is not explicitly clear.
When contacting support about error responses received from the API, please attempt to include, at minimum:
Specifically, when a response with an HTTP Status Code of 422 is returned, this indicates a validation error, almost always received in a response from a non-idempotent request (normally PUT, POST or DELETE). In this case, there should be an additional "errors" property included in the JSON response body that should describe the cause of the validation exception; this will almost always require a modification to the request body to resolve.
' version: v1 servers: - url: https://[region].api.insight.rapid7.com/ias/v1 tags: - name: Vulnerability Exception description: Vulnerability Exception Resource Controller paths: /api/3/vulnerability_exceptions: get: tags: - Vulnerability Exception summary: Exceptions description: Returns all exceptions defined on vulnerabilities. operationId: getVulnerabilityExceptions schemes: [] consumes: - application/json produces: - application/json;charset=UTF-8 parameters: - name: page in: query description: The index of the page (zero-based) to retrieve. required: false type: integer default: 0 format: int32 - name: size in: query description: The number of records per page to retrieve. required: false type: integer default: 10 format: int32 - name: sort in: query description: 'The criteria to sort the records by, in the format: `property[,ASC|DESC]`. The default sort order is ascending. Multiple sort criteria can be specified using multiple sort query parameters.' required: false type: array items: type: string collectionFormat: multi responses: '200': description: OK schema: $ref: '#/definitions/PageOf«VulnerabilityException»' examples: {} headers: {} '401': description: Unauthorized schema: $ref: '#/definitions/UnauthorizedError' examples: {} headers: {} '404': description: Not Found schema: $ref: '#/definitions/NotFoundError' examples: {} headers: {} '500': description: Internal Server Error schema: $ref: '#/definitions/InternalServerError' examples: {} headers: {} '503': description: Service Unavailable schema: $ref: '#/definitions/ServiceUnavailableError' examples: {} headers: {} security: [] post: tags: - Vulnerability Exception summary: Exceptions description: Creates a vulnerability exception. operationId: createVulnerabilityException schemes: [] consumes: - application/json produces: - application/json;charset=UTF-8 parameters: - in: body name: vulnerabilityException description: The vulnerability exception to create. required: false schema: $ref: '#/definitions/VulnerabilityException' responses: '200': description: OK schema: $ref: '#/definitions/CreatedReference«VulnerabilityExceptionID,Link»' examples: {} headers: {} '400': description: Bad Request schema: $ref: '#/definitions/BadRequestError' examples: {} headers: {} '401': description: Unauthorized schema: $ref: '#/definitions/UnauthorizedError' examples: {} headers: {} '500': description: Internal Server Error schema: $ref: '#/definitions/InternalServerError' examples: {} headers: {} '503': description: Service Unavailable schema: $ref: '#/definitions/ServiceUnavailableError' examples: {} headers: {} security: [] /api/3/vulnerability_exceptions/{id}: get: tags: - Vulnerability Exception summary: Exception description: Returns an exception made on a vulnerability. operationId: getVulnerabilityException schemes: [] consumes: - application/json produces: - application/json;charset=UTF-8 parameters: - name: id in: path description: The identifier of the vulnerability exception. required: true type: integer format: int32 responses: '200': description: OK schema: $ref: '#/definitions/VulnerabilityException' examples: {} headers: {} '401': description: Unauthorized schema: $ref: '#/definitions/UnauthorizedError' examples: {} headers: {} '404': description: Not Found schema: $ref: '#/definitions/NotFoundError' examples: {} headers: {} '500': description: Internal Server Error schema: $ref: '#/definitions/InternalServerError' examples: {} headers: {} '503': description: Service Unavailable schema: $ref: '#/definitions/ServiceUnavailableError' examples: {} headers: {} security: [] delete: tags: - Vulnerability Exception summary: Exception description: Removes an exception made on a vulnerability. operationId: removeVulnerabilityException schemes: [] consumes: - application/json produces: - application/json;charset=UTF-8 parameters: - name: id in: path description: id required: true type: integer format: int32 responses: '200': description: OK schema: $ref: '#/definitions/Links' examples: {} headers: {} '401': description: Unauthorized schema: $ref: '#/definitions/UnauthorizedError' examples: {} headers: {} '404': description: Not Found schema: $ref: '#/definitions/NotFoundError' examples: {} headers: {} '500': description: Internal Server Error schema: $ref: '#/definitions/InternalServerError' examples: {} headers: {} '503': description: Service Unavailable schema: $ref: '#/definitions/ServiceUnavailableError' examples: {} headers: {} security: [] /api/3/vulnerability_exceptions/{id}/expires: get: tags: - Vulnerability Exception summary: Exception Expiration description: Get the expiration date for a vulnerability exception. operationId: getVulnerabilityExceptionExpiration schemes: [] consumes: - application/json produces: - application/json;charset=UTF-8 parameters: - name: id in: path description: id required: true type: integer format: int32 responses: '200': description: OK schema: type: string examples: {} headers: {} '401': description: Unauthorized schema: $ref: '#/definitions/UnauthorizedError' examples: {} headers: {} '404': description: Not Found schema: $ref: '#/definitions/NotFoundError' examples: {} headers: {} '500': description: Internal Server Error schema: $ref: '#/definitions/InternalServerError' examples: {} headers: {} '503': description: Service Unavailable schema: $ref: '#/definitions/ServiceUnavailableError' examples: {} headers: {} security: [] put: tags: - Vulnerability Exception summary: Exception Expiration description: Set the expiration date for a vulnerability exception. This must be a valid date in the future. operationId: updateVulnerabilityExceptionExpiration schemes: [] consumes: - application/json produces: - application/json;charset=UTF-8 parameters: - name: id in: path description: id required: true type: integer format: int32 - in: body name: param1 description: param1 required: true schema: type: string responses: '200': description: OK schema: $ref: '#/definitions/Links' examples: {} headers: {} '400': description: Bad Request schema: $ref: '#/definitions/BadRequestError' examples: {} headers: {} '401': description: Unauthorized schema: $ref: '#/definitions/UnauthorizedError' examples: {} headers: {} '404': description: Not Found schema: $ref: '#/definitions/NotFoundError' examples: {} headers: {} '500': description: Internal Server Error schema: $ref: '#/definitions/InternalServerError' examples: {} headers: {} '503': description: Service Unavailable schema: $ref: '#/definitions/ServiceUnavailableError' examples: {} headers: {} security: [] /api/3/vulnerability_exceptions/{id}/{status}: post: tags: - Vulnerability Exception summary: Exception Status description: 'Update the status of the vulnerability exception. The status can be one of: `"recall"`, `"approve"`, or `"reject"`.' operationId: updateVulnerabilityExceptionStatus schemes: [] consumes: - application/json produces: - application/json;charset=UTF-8 parameters: - name: id in: path description: id required: true type: integer format: int32 - name: status in: path description: Exception Status required: true type: string enum: - recall - approve - reject - in: body name: param2 description: param2 required: false schema: type: string responses: '200': description: OK schema: $ref: '#/definitions/Links' examples: {} headers: {} '400': description: Bad Request schema: $ref: '#/definitions/BadRequestError' examples: {} headers: {} '401': description: Unauthorized schema: $ref: '#/definitions/UnauthorizedError' examples: {} headers: {} '500': description: Internal Server Error schema: $ref: '#/definitions/InternalServerError' examples: {} headers: {} '503': description: Service Unavailable schema: $ref: '#/definitions/ServiceUnavailableError' examples: {} headers: {} security: [] definitions: BadRequestError: type: object required: - status properties: links: type: array description: Hypermedia links to corresponding or related resources. items: $ref: '#/definitions/Link' message: type: string example: An error has occurred. description: The messages indicating the cause or reason for failure. status: type: string example: '400' description: The HTTP status code for the error (same as in the HTTP response). enum: - '400' description: '' Submission: type: object properties: comment: type: string example: '' description: A comment from the submitter as to why the exception was submitted. date: type: string example: '' description: The date and time the vulnerability exception was submitted. readOnly: true links: type: array items: $ref: '#/definitions/Link' name: type: string example: '' description: The login name of the user that submitted the vulnerability exception. readOnly: true reason: type: string example: '' description: 'The reason the vulnerability exception was submitted. One of: `"False Positive"`, `"Compensating Control"`, `"Acceptable Use"`, `"Acceptable Risk"`, `"Other"`' user: type: integer format: int32 example: '' description: The identifier of the user that submitted the vulnerability exception. readOnly: true description: '' UnauthorizedError: type: object required: - status properties: links: type: array description: Hypermedia links to corresponding or related resources. items: $ref: '#/definitions/Link' message: type: string example: An error has occurred. description: The messages indicating the cause or reason for failure. status: type: string example: '401' description: The HTTP status code for the error (same as in the HTTP response). enum: - '401' description: '' VulnerabilityException: type: object properties: expires: type: string example: '' description: The date and time the vulnerability exception is set to expire. id: type: integer format: int32 example: '' description: The identifier of the vulnerability exception. readOnly: true links: type: array items: $ref: '#/definitions/Link' review: example: '' description: Details regarding the review and/or approval of the exception. readOnly: true $ref: '#/definitions/Review' scope: example: '' description: The scope of the vulnerability exception, indicating the results it applies to. $ref: '#/definitions/ExceptionScope' state: type: string example: '' description: 'The state of the vulnerability exception. One of: `"Deleted"`, `"Expired"`, `"Approved"`, `"Rejected"`, `"Under Review".' submit: example: '' description: Details regarding the submission of the exception. readOnly: true $ref: '#/definitions/Submission' description: '' CreatedReference«VulnerabilityExceptionID,Link»: type: object properties: id: type: integer format: int32 example: 1 description: The identifier of the resource created. links: type: array description: Hypermedia links to corresponding or related resources. items: $ref: '#/definitions/Link' description: '' Links: type: object properties: links: type: array description: Hypermedia links to corresponding or related resources. items: $ref: '#/definitions/Link' description: '' ServiceUnavailableError: type: object required: - status properties: links: type: array description: Hypermedia links to corresponding or related resources. items: $ref: '#/definitions/Link' message: type: string example: An error has occurred. description: The messages indicating the cause or reason for failure. status: type: string example: '503' description: The HTTP status code for the error (same as in the HTTP response). enum: - '503' description: '' PageOf«VulnerabilityException»: type: object properties: links: type: array description: Hypermedia links to corresponding or related resources. items: $ref: '#/definitions/Link' page: example: '' description: The details of pagination indicating which page was returned, and how the remaining pages can be retrieved. $ref: '#/definitions/PageInfo' resources: type: array description: The page of resources returned. items: $ref: '#/definitions/VulnerabilityException' description: '' ExceptionScope: type: object properties: id: type: integer format: int64 example: '' description: The identifier of the scope type to which the exception applies. For example in a site scoped vulnerability exception this is the site id, in an asset group vulnerability exception this is the asset group id. key: type: string example: '' description: If the scope type is `"Instance"`, an optional key to discriminate the instance the exception applies to. links: type: array items: $ref: '#/definitions/Link' port: type: integer format: int32 example: '' description: If the scope type is `"Instance"` and the vulnerability is detected on a service, the port on which the exception applies. type: type: string example: '' description: 'The type of the exception scope. One of: `"Global"`, `"Site"`, `"Asset"`, `"Asset Group"`, `"Instance"`' vulnerability: type: string example: '' description: The identifier of the vulnerability to which the exception applies. description: '' NotFoundError: type: object required: - status properties: links: type: array description: Hypermedia links to corresponding or related resources. items: $ref: '#/definitions/Link' message: type: string example: An error has occurred. description: The messages indicating the cause or reason for failure. status: type: string example: '404' description: The HTTP status code for the error (same as in the HTTP response). enum: - '404' description: '' PageInfo: type: object properties: number: type: integer format: int64 example: 6 description: The index (zero-based) of the current page returned. size: type: integer format: int64 example: 10 description: The maximum size of the page returned. totalPages: type: integer format: int64 example: 13 description: The total number of pages available. totalResources: type: integer format: int64 example: 123 description: The total number of resources available across all pages. description: '' Review: type: object properties: comment: type: string example: '' description: 'A comment from the reviewer detailing the review. ' readOnly: true date: type: string example: '' description: The date and time the review took place. readOnly: true links: type: array items: $ref: '#/definitions/Link' name: type: string example: '' description: The identifier of the user that reviewed the vulnerability exception. readOnly: true user: type: integer format: int32 example: '' description: The login name of the user that reviewed the vulnerability exception. readOnly: true description: '' Link: type: object properties: href: type: string example: https://hostname:3780/api/3/... description: 'A hypertext reference, which is either a URI (see RFC 3986) or URI template (see RFC 6570). ' rel: type: string example: self description: The link relation type. This value is one from the Link Relation Type Registry or is the type of resource being linked to. description: '' InternalServerError: type: object required: - status properties: links: type: array description: Hypermedia links to corresponding or related resources. items: $ref: '#/definitions/Link' message: type: string example: An error has occurred. description: The messages indicating the cause or reason for failure. status: type: string example: '500' description: The HTTP status code for the error (same as in the HTTP response). enum: - '500' description: ''