openapi: 3.1.0 info: title: InsightAppSec Accounts Reports 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: Reports description: 'Reports provide the ability to share information with stakeholders at both scan and app levels. The following table lists the report templates and the various formats that are available:| Report Type | Report Format |
|---|---|
VULN_SUMMARY | PDF HTML CSV |
VULN_REMEDIATION | PDF HTML |
PCI_COMPLIANCE | PDF HTML |
PCI4_COMPLIANCE | PDF HTML |
OWASP_2013_COMPLIANCE | PDF HTML |
OWASP_2017_COMPLIANCE | PDF HTML |
OWASP_2021_COMPLIANCE | PDF HTML |
OWASP_2023API_COMPLIANCE | PDF HTML |
OWASP_2025_COMPLIANCE | PDF HTML |
GDPR_2016_COMPLIANCE | PDF HTML |
SOX_COMPLIANCE | PDF HTML |
HIPAA_COMPLIANCE | PDF HTML |
EXEC_SINGLE_APP (deprecated) | PDF HTML |
EXEC_ALL_APPS (deprecated) | PDF |
EXEC_SINGLE_APP_NEW_VULNS | PDF HTML |
EXEC_ALL_APP_NEW_VULNS | PDF |
EXEC_SINGLE_APP_ALL_VULNS | PDF HTML |
EXEC_ALL_APP_ALL_VULNS | PDF |
EXEC_IAS_IVM_COMPOSITE | PDF |
The default sort for Reports is "generatedDate" (descending); for a full list of sortable properties, refer to the Search Catalog detailed in the Search API.
operationId: get-reports parameters: - name: index in: query schema: type: integer format: int32 - name: size in: query schema: type: integer format: int32 - name: sort in: query schema: type: string - name: page-token in: query schema: type: string responses: '415': description: Unsupported Media Type content: application/json: schema: $ref: '#/components/schemas/Error' '200': description: OK content: application/json: schema: $ref: '#/components/schemas/PageReport' '400': description: Bad Request content: application/json: schema: $ref: '#/components/schemas/Error' '401': description: Unauthenticated content: application/json: schema: $ref: '#/components/schemas/Error' '403': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/Error' '404': description: Resource not found content: application/json: schema: $ref: '#/components/schemas/Error' '500': description: Internal error content: application/json: schema: $ref: '#/components/schemas/Error' post: tags: - Reports summary: Generate Report description: Generate a new Report| Report Type | name | type | format | scanId | filter |
|---|---|---|---|---|---|
VULN_SUMMARY | ✅ | ✅ | ✅ | ✅ | ✳ |
VULN_REMEDIATION | ✅ | ✅ | ✅ | ✅ | ✳ |
PCI_COMPLIANCE | ✅ | ✅ | ✅ | ✅ | ✳ |
PCI4_COMPLIANCE | ✅ | ✅ | ✅ | ✅ | ✳ |
OWASP_2013_COMPLIANCE | ✅ | ✅ | ✅ | ✅ | ✳ |
OWASP_2017_COMPLIANCE | ✅ | ✅ | ✅ | ✅ | ✳ |
OWASP_2021_COMPLIANCE | ✅ | ✅ | ✅ | ✅ | ✳ |
OWASP_2023API_COMPLIANCE | ✅ | ✅ | ✅ | ✅ | ✳ |
OWASP_2025_COMPLIANCE | ✅ | ✅ | ✅ | ✅ | ✳ |
GDPR_2016_COMPLIANCE | ✅ | ✅ | ✅ | ✅ | ✳ |
SOX_COMPLIANCE | ✅ | ✅ | ✅ | ✅ | ✳ |
HIPAA_COMPLIANCE | ✅ | ✅ | ✅ | ✅ | ✳ |
EXEC_SINGLE_APP (deprecated) | ✅ | ✅ | ✅ | ❌ | ✳ |
EXEC_ALL_APPS (deprecated) | ✅ | ✅ | ✅ | ❌ | ✳ |
EXEC_SINGLE_APP_NEW_VULNS | ✅ | ✅ | ✅ | ❌ | ✳ |
EXEC_ALL_APPS_NEW_VULNS | ✅ | ✅ | ✅ | ❌ | ✳ |
EXEC_SINGLE_APP_ALL_VULNS | ✅ | ✅ | ✅ | ❌ | ✳ |
EXEC_ALL_APPS_ALL_VULNS | ✅ | ✅ | ✅ | ❌ | ✳ |
Accept header passed in the call. When retrieving only the Report Information the client should supply an Accept header value that indicates acceptance of the application/json mime type only. To download the Report Contents the client is required to supply Accept header values that indicate acceptance of application/pdf for PDF reports, application/zip for HTML reports or text/csv for CSV reports. To ensure errors can be returned application/json should also be provided as the second Accept header value. Attempts to download a report for which the generation status is not COMPLETE will result in a response of "204 No Content".COMPLETE'
operationId: get-report
parameters:
- name: report-id
in: path
required: true
schema:
type: string
format: uuid
responses:
'415':
description: Unsupported Media Type
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'200':
description: OK
content:
text/csv:
schema:
type: string
format: binary
application/zip:
schema:
type: string
format: binary
application/pdf:
schema:
type: string
format: binary
application/json:
schema:
$ref: '#/components/schemas/EntityModelReport'
'400':
description: Bad Request
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'401':
description: Unauthenticated
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'403':
description: Unauthorized
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'404':
description: Resource not found
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'500':
description: Internal error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
delete:
tags:
- Reports
summary: Delete Report
description: Delete an existing Report
operationId: delete-report
parameters:
- name: report-id
in: path
required: true
schema:
type: string
format: uuid
responses:
'415':
description: Unsupported Media Type
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'204':
description: No Content
'400':
description: Bad Request
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'401':
description: Unauthenticated
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'403':
description: Unauthorized
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'404':
description: Resource not found
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'500':
description: Internal error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'409':
description: Action conflict
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
components:
schemas:
ReadOnlyIdResource:
description: The ID of the module
properties:
id:
type: string
format: uuid
readOnly: true
readOnly: true
ValidationErrors:
properties:
status:
type: string
description: A description of the type of error based on HTTP status code
enum:
- 100 CONTINUE
- 101 SWITCHING_PROTOCOLS
- 102 PROCESSING
- 103 EARLY_HINTS
- 103 CHECKPOINT
- 200 OK
- 201 CREATED
- 202 ACCEPTED
- 203 NON_AUTHORITATIVE_INFORMATION
- 204 NO_CONTENT
- 205 RESET_CONTENT
- 206 PARTIAL_CONTENT
- 207 MULTI_STATUS
- 208 ALREADY_REPORTED
- 226 IM_USED
- 300 MULTIPLE_CHOICES
- 301 MOVED_PERMANENTLY
- 302 FOUND
- 302 MOVED_TEMPORARILY
- 303 SEE_OTHER
- 304 NOT_MODIFIED
- 305 USE_PROXY
- 307 TEMPORARY_REDIRECT
- 308 PERMANENT_REDIRECT
- 400 BAD_REQUEST
- 401 UNAUTHORIZED
- 402 PAYMENT_REQUIRED
- 403 FORBIDDEN
- 404 NOT_FOUND
- 405 METHOD_NOT_ALLOWED
- 406 NOT_ACCEPTABLE
- 407 PROXY_AUTHENTICATION_REQUIRED
- 408 REQUEST_TIMEOUT
- 409 CONFLICT
- 410 GONE
- 411 LENGTH_REQUIRED
- 412 PRECONDITION_FAILED
- 413 PAYLOAD_TOO_LARGE
- 413 REQUEST_ENTITY_TOO_LARGE
- 414 URI_TOO_LONG
- 414 REQUEST_URI_TOO_LONG
- 415 UNSUPPORTED_MEDIA_TYPE
- 416 REQUESTED_RANGE_NOT_SATISFIABLE
- 417 EXPECTATION_FAILED
- 418 I_AM_A_TEAPOT
- 419 INSUFFICIENT_SPACE_ON_RESOURCE
- 420 METHOD_FAILURE
- 421 DESTINATION_LOCKED
- 422 UNPROCESSABLE_ENTITY
- 423 LOCKED
- 424 FAILED_DEPENDENCY
- 425 TOO_EARLY
- 426 UPGRADE_REQUIRED
- 428 PRECONDITION_REQUIRED
- 429 TOO_MANY_REQUESTS
- 431 REQUEST_HEADER_FIELDS_TOO_LARGE
- 451 UNAVAILABLE_FOR_LEGAL_REASONS
- 500 INTERNAL_SERVER_ERROR
- 501 NOT_IMPLEMENTED
- 502 BAD_GATEWAY
- 503 SERVICE_UNAVAILABLE
- 504 GATEWAY_TIMEOUT
- 505 HTTP_VERSION_NOT_SUPPORTED
- 506 VARIANT_ALSO_NEGOTIATES
- 507 INSUFFICIENT_STORAGE
- 508 LOOP_DETECTED
- 509 BANDWIDTH_LIMIT_EXCEEDED
- 510 NOT_EXTENDED
- 511 NETWORK_AUTHENTICATION_REQUIRED
readOnly: true
message:
type: string
description: A description of the error
readOnly: true
errorCode:
type: string
description: An optional code which may help support indicate the underlying cause of the error
enum:
- E1
- E2
- E3
- E4
- E5
- E6
- E7
- E8
- E9
- E10
- E11
- E12
- E13
- E14
- E15
- E16
- E17
- E18
- E19
- E20
- E22
- E23
- E24
- E25
- E26
- E27
- E28
- E999
readOnly: true
errors:
type: array
description: A list of validation errors, when the HTTP status code is 422
items:
$ref: '#/components/schemas/ValidationError'
readOnly: true
title: ValidationErrors
PageReport:
properties:
data:
type: array
items:
$ref: '#/components/schemas/EntityModelReport'
metadata:
$ref: '#/components/schemas/PageMetadata'
links:
type: array
items:
$ref: '#/components/schemas/Link'
readOnly: true
Link:
properties:
rel:
type: string
href:
type: string
profile:
type: string
name:
type: string
readOnly: true
PageMetadata:
properties:
index:
type: integer
format: int64
size:
type: integer
format: int64
sort:
type: string
total_data:
type: integer
format: int64
total_pages:
type: integer
format: int64
page_token:
type: string
app:
description: The App that the Scan is associated with
properties:
id:
type: string
format: uuid
ReferenceResource:
description: The last editor of the comment
properties:
id:
type: string
format: uuid
readOnly: true
required:
- id
ValidationError:
properties:
type:
type: string
description: The type of the validation error
enum:
- OBJECT
- PROPERTY
readOnly: true
context:
type: string
description: An optional contextual indicator of a part of the request which failed validation
readOnly: true
explanation:
type: string
description: Details of the validation error
readOnly: true
ReportGeneration:
properties:
name:
type: string
description: The name of the Report
example: Weekly Report
type:
type: string
description: The type of the Report.EXEC_SINGLE_APP is deprecated. Use EXEC_SINGLE_APP_NEW_VULNS or EXEC_SINGLE_APP_ALL_VULNS instead. EXEC_ALL_APPS is deprecated. Use EXEC_ALL_APPS_NEW_VULNS or EXEC_ALL_APPS_ALL_VULNS instead.
enum:
- VULN_SUMMARY
- VULN_REMEDIATION
- PCI_COMPLIANCE
- PCI4_COMPLIANCE
- OWASP_2013_COMPLIANCE
- OWASP_2017_COMPLIANCE
- OWASP_2021_COMPLIANCE
- OWASP_2023API_COMPLIANCE
- OWASP_2025_COMPLIANCE
- GDPR_2016_COMPLIANCE
- SOX_COMPLIANCE
- HIPAA_COMPLIANCE
- EXEC_SINGLE_APP
- EXEC_ALL_APPS
- EXEC_SINGLE_APP_NEW_VULNS
- EXEC_ALL_APPS_NEW_VULNS
- EXEC_SINGLE_APP_ALL_VULNS
- EXEC_ALL_APPS_ALL_VULNS
example: VULN_SUMMARY
format:
type: string
description: The format of the Report
enum:
- HTML
- CSV
- PDF
example: PDF
scan:
$ref: '#/components/schemas/scan'
app:
$ref: '#/components/schemas/app'
start:
type: string
description: The start date range scope for the Report yyyy-mm-dd
end:
type: string
description: The end date range scope for the Report yyyy-mm-dd
month:
type: string
description: The month date range scope for the Report yyyy-mm
example: 2023-12
filter:
type: string
description: Search-format filter relevant to the Report Type that narrows its scope
example: vulnerability.app.name CONTAINS 'Weekly'
required:
- format
- name
- type
title: Report Generation
scan:
description: The Scan associated with the Report
properties:
id:
type: string
format: uuid
Error:
properties:
status:
type: string
description: A description of the type of error based on HTTP status code
enum:
- 100 CONTINUE
- 101 SWITCHING_PROTOCOLS
- 102 PROCESSING
- 103 EARLY_HINTS
- 103 CHECKPOINT
- 200 OK
- 201 CREATED
- 202 ACCEPTED
- 203 NON_AUTHORITATIVE_INFORMATION
- 204 NO_CONTENT
- 205 RESET_CONTENT
- 206 PARTIAL_CONTENT
- 207 MULTI_STATUS
- 208 ALREADY_REPORTED
- 226 IM_USED
- 300 MULTIPLE_CHOICES
- 301 MOVED_PERMANENTLY
- 302 FOUND
- 302 MOVED_TEMPORARILY
- 303 SEE_OTHER
- 304 NOT_MODIFIED
- 305 USE_PROXY
- 307 TEMPORARY_REDIRECT
- 308 PERMANENT_REDIRECT
- 400 BAD_REQUEST
- 401 UNAUTHORIZED
- 402 PAYMENT_REQUIRED
- 403 FORBIDDEN
- 404 NOT_FOUND
- 405 METHOD_NOT_ALLOWED
- 406 NOT_ACCEPTABLE
- 407 PROXY_AUTHENTICATION_REQUIRED
- 408 REQUEST_TIMEOUT
- 409 CONFLICT
- 410 GONE
- 411 LENGTH_REQUIRED
- 412 PRECONDITION_FAILED
- 413 PAYLOAD_TOO_LARGE
- 413 REQUEST_ENTITY_TOO_LARGE
- 414 URI_TOO_LONG
- 414 REQUEST_URI_TOO_LONG
- 415 UNSUPPORTED_MEDIA_TYPE
- 416 REQUESTED_RANGE_NOT_SATISFIABLE
- 417 EXPECTATION_FAILED
- 418 I_AM_A_TEAPOT
- 419 INSUFFICIENT_SPACE_ON_RESOURCE
- 420 METHOD_FAILURE
- 421 DESTINATION_LOCKED
- 422 UNPROCESSABLE_ENTITY
- 423 LOCKED
- 424 FAILED_DEPENDENCY
- 425 TOO_EARLY
- 426 UPGRADE_REQUIRED
- 428 PRECONDITION_REQUIRED
- 429 TOO_MANY_REQUESTS
- 431 REQUEST_HEADER_FIELDS_TOO_LARGE
- 451 UNAVAILABLE_FOR_LEGAL_REASONS
- 500 INTERNAL_SERVER_ERROR
- 501 NOT_IMPLEMENTED
- 502 BAD_GATEWAY
- 503 SERVICE_UNAVAILABLE
- 504 GATEWAY_TIMEOUT
- 505 HTTP_VERSION_NOT_SUPPORTED
- 506 VARIANT_ALSO_NEGOTIATES
- 507 INSUFFICIENT_STORAGE
- 508 LOOP_DETECTED
- 509 BANDWIDTH_LIMIT_EXCEEDED
- 510 NOT_EXTENDED
- 511 NETWORK_AUTHENTICATION_REQUIRED
readOnly: true
message:
type: string
description: A description of the error
readOnly: true
errorCode:
type: string
description: An optional code which may help support indicate the underlying cause of the error
enum:
- E1
- E2
- E3
- E4
- E5
- E6
- E7
- E8
- E9
- E10
- E11
- E12
- E13
- E14
- E15
- E16
- E17
- E18
- E19
- E20
- E22
- E23
- E24
- E25
- E26
- E27
- E28
- E999
readOnly: true
title: Error
EntityModelReport:
properties:
id:
type: string
format: uuid
name:
type: string
description: The name of the Report
readOnly: true
type:
type: string
description: The type of the Report.EXEC_SINGLE_APP is deprecated. Use EXEC_SINGLE_APP_NEW_VULNS or EXEC_SINGLE_APP_ALL_VULNS instead. EXEC_ALL_APPS is deprecated. Use EXEC_ALL_APPS_NEW_VULNS or EXEC_ALL_APPS_ALL_VULNS instead.
enum:
- VULN_SUMMARY
- VULN_REMEDIATION
- PCI_COMPLIANCE
- PCI4_COMPLIANCE
- OWASP_2013_COMPLIANCE
- OWASP_2017_COMPLIANCE
- OWASP_2021_COMPLIANCE
- OWASP_2023API_COMPLIANCE
- OWASP_2025_COMPLIANCE
- GDPR_2016_COMPLIANCE
- SOX_COMPLIANCE
- HIPAA_COMPLIANCE
- EXEC_SINGLE_APP
- EXEC_ALL_APPS
- EXEC_SINGLE_APP_NEW_VULNS
- EXEC_ALL_APPS_NEW_VULNS
- EXEC_SINGLE_APP_ALL_VULNS
- EXEC_ALL_APPS_ALL_VULNS
- EXEC_IAS_IVM_COMPOSITE
- TARGET_DISCOVERY
readOnly: true
format:
type: string
description: The format of the Report
enum:
- HTML
- CSV
- PDF
readOnly: true
owner:
$ref: '#/components/schemas/ReadOnlyIdResource'
generated_date:
type: string
format: date-time
description: The time the Report was generated
readOnly: true
app:
$ref: '#/components/schemas/ReferenceResource'
status:
type: string
description: The status of the Report
enum:
- PROCESSING
- FAILED
- COMPLETE
readOnly: true
links:
type: array
items:
$ref: '#/components/schemas/Link'
readOnly: true