How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Fortify Scans API

View and manage security scans

Fortify Scans API is one of 42 APIs that Fortify publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Scans. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, and a getting-started guide.

This API exposes 14 operations across 13 paths, and defines 15 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 4 base URLs: https://api.ams.fortify.com, https://api.emea.fortify.com, https://api.apac.fortify.com, {protocol}://{host}/api.

14 operations 13 paths 15 schemas 1 DELETE10 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.ams.fortify.com
Authentication
HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 2

Fortify Scans API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). An API key is passed in the header as Authorization (fortifyToken).

  • bearerAuth — OAuth2 Bearer token obtained from POST /oauth/token using either clientcredentials or password grant type.
  • fortifyToken — Fortify token-based authentication. Pass as: FORTIFYTOKEN . Obtain a CI token from SSC Administration or use an SSC auth token.

Paths & Operations 14

Across 13 paths, the API surfaces 14 operations — 1 DELETE, 10 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Scans 14

View and manage security scans

GET
/api/v3/applications/{applicationId}/scans
Fortify List application scans
listApplicationScans 6 params → 200401403404429
GET
/api/v3/releases/{releaseId}/scans
Fortify List release scans
listReleaseScans 6 params → 200401403404429
GET
/api/v3/releases/{releaseId}/scans/{scanId}
Fortify Get release scan
getReleaseScan 2 params → 200401403404429
GET
/api/v3/releases/{releaseId}/scans/{scanId}/polling-summary
Fortify Get scan polling summary
getReleaseScanPollingSummary 2 params → 200401403404429
GET
/api/v3/releases/{releaseId}/assessment-types
Fortify List assessment types
listReleaseAssessmentTypes 8 params → 200401403404429
GET
/api/v3/releases/{releaseId}/import-scan-session-id
Fortify Get import scan session ID
getReleaseImportScanSessionId 1 param → 200401403404429
GET
/scans
Fortify List scans
listScans 6 params → 200401403
GET
/scans/{scanId}
Fortify Get scan
getScan 1 param → 200401404
DELETE
/scans/{scanId}
Fortify Delete scan
deleteScan 1 param → 200401404
POST
/scans/{scanId}/action
Fortify Perform scan action
performScanAction 1 param body → 200400401404
GET
/scans/{scanId}/scan-log
Fortify Get scan log
getScanLog 1 param → 200401404
GET
/scans/{scanId}/scan-summary
Fortify Get scan summary
getScanSummary 1 param → 200401404
POST
/scans/start-scan
Fortify Start scan
startScan body → 200400401403
POST
/scans/start-scan-cicd
Fortify Start scan from CI/CD
startScanCicd body → 200400401403

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are DastScan (17 properties), Scan (12 properties), DastScanSummary (11 properties), PollingScanSummary (5 properties). Each schema is shown below with its type and property counts.

AssessmentType
object
Represents an assessment type
5 properties
ScanListResponse
object
Paginated list of scans
2 properties
PollingScanSummary
object
Scan status for polling
5 properties
Scan
object
Represents a security scan
12 properties
GetImportScanSessionIdResponse
object
Response with import scan session ID
1 property
ErrorResponse
object
Error response
1 property
ReleaseAssessmentTypeListResponse
object
List of available assessment types for a release
2 properties
ScanListResponse_2
object
Paginated list of scans
2 properties
DastScanSummary
object
Summary of a DAST scan
11 properties
StartScanRequest
object
Request to start a scan
3 properties 1 required
StartScanCicdRequest
object
Request to start a scan from CI/CD pipeline
2 properties 1 required
ErrorResponse_2
object
Error response
3 properties
ScanActionRequest
object
Request to perform an action on a scan
1 property 1 required
StartScanResponse
object
Response after starting a scan
2 properties
DastScan
object
Represents a DAST scan
17 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fortify-scans-api-openapi.yml Raw ↑

Other APIs Fortify publishes across the network.

Fortify Alert Definitions API
Fortify API Keys API
Fortify Applications API
Fortify Artifacts API
Fortify Attributes API
Fortify Audit Templates API
Fortify Auth Entities API
Fortify Authentication API
Fortify CI/CD API
Fortify Cloud Pools API
Fortify Custom Tags API
Fortify DAST Automated Scans API
Where this information came from

This is an independent, third-party profile of Fortify Scans API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.