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

Pynt Scan API

The scan API from Pynt — 26 operation(s) for scan.

Pynt Scan API is one of 32 APIs that Pynt 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, an API reference, and API documentation.

This API exposes 27 operations across 26 paths, and defines 58 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against a single base URL, https://api.pynt.io.

27 operations 26 paths 58 schemas 18 GET5 POST4 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://api.pynt.io
Authentication
API Key, API Key, API Key, API Key, API Key
Resource Areas
1

Authentication & Security 5

Pynt Scan API declares 5 security schemes for authenticating requests. An API key is passed in the header as X-API-Key (API_Key). An API key is passed in the header as Authorization (Bearer_Token). An API key is passed in the header as X-System-API-Key (System_API_Key). An API key is passed in the header as X-Organization-ID (Organization_ID). An API key is passed in the header as context (Operator_Organization_Context).

Paths & Operations 27

Across 26 paths, the API surfaces 27 operations — 18 GET, 5 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

scan 27
GET
/v1/scan/{scan_id}/false-positive-analysis
Get False Positive Analysis
get_false_positive_analysis_v1_scan__scan_id__false_positive_analysis_get 1 param → 200422
PUT
/v1/scan/{scan_id}/false-positive-analysis/{finding_id}/approved
Update Finding Approval
update_finding_approval_v1_scan__scan_id__false_positive_analysis__finding_id__approved_put 2 params body → 200422
GET
/v1/scan/{scan_id}/business-impact-analysis
Get Business Impact Analysis
get_business_impact_analysis_v1_scan__scan_id__business_impact_analysis_get 1 param → 200422
PUT
/v1/scan/{scan_id}/business-impact-analysis/{finding_id}/approved
Update Finding Approval
update_finding_approval_v1_scan__scan_id__business_impact_analysis__finding_id__approved_put 2 params body → 200422
GET
/v1/scan/{scan_id}/summary
Get Scan By Id
get_scan_by_id_v1_scan__scan_id__summary_get 1 param → 200422
GET
/v1/scan/summary
List Scans Summaries
list_scans_summaries_v1_scan_summary_get 1 param → 200422
GET
/v1/scan/summary/count
Count Scans Summaries
count_scans_summaries_v1_scan_summary_count_get 1 param → 200422
GET
/v1/scan/config
Get Scan Config
get_scan_config_v1_scan_config_get 1 param → 200422
PUT
/v1/scan
Create Scan
create_scan_v1_scan_put body → 201422
PUT
/v1/scan/{scan_id}/tags
Update Scan Tags
update_scan_tags_v1_scan__scan_id__tags_put 1 param body → 200422
GET
/v1/scan/{scan_id}/requests-log
Get Scan Requests Log
get_scan_requests_log_v1_scan__scan_id__requests_log_get 1 param → 200422
POST
/v1/scan/run-remote-har-scan
Run Har Scan
run_har_scan_v1_scan_run_remote_har_scan_post body → 200422
POST
/v1/scan/run-remote-scan
Run Scan
run_scan_v1_scan_run_remote_scan_post body → 200422
POST
/v1/scan/{scan_id}/progress
Post Scan Progress
post_scan_progress_v1_scan__scan_id__progress_post 1 param body → 200422
POST
/v1/scan/{scan_id}/abort
Abort Scan
abort_scan_v1_scan__scan_id__abort_post 1 param → 200422
GET
/v1/scan/current_scans
Get All Current Scans
get_all_current_scans_v1_scan_current_scans_get 1 param → 200422
GET
/v1/scan/{application_id}/current_scans
Get App Current Scans
get_app_current_scans_v1_scan__application_id__current_scans_get 2 params → 200422
GET
/v1/scan/running
Get All Running Scans
get_all_running_scans_v1_scan_running_get → 200
POST
/v1/scan/{scan_id}/reportdeprecated
Create Report
create_report_v1_scan__scan_id__report_post 1 param body → 201422
GET
/v1/scan/{scan_id}/report
Get Report
get_report_v1_scan__scan_id__report_get 1 param → 200422
GET
/v1/scan/{scan_id}/metadata
Get Scan Metadata
get_scan_metadata_v1_scan__scan_id__metadata_get 1 param → 200422
GET
/v1/scan/{scan_id}/owasp_coverage
Get Scan Owasp
get_scan_owasp_v1_scan__scan_id__owasp_coverage_get 1 param → 200422
GET
/v1/scan/{scan_id}/findings_details
Get Scan Findings
get_scan_findings_v1_scan__scan_id__findings_details_get 2 params → 200422
GET
/v1/scan/{scan_id}/endpoints_details
Get Scan Endpoints
get_scan_endpoints_v1_scan__scan_id__endpoints_details_get 2 params → 200422
GET
/v1/scan/{scan_id}/traffic_data
Get Scan Details Traffic Data
get_scan_details_traffic_data_v1_scan__scan_id__traffic_data_get 3 params → 200422
GET
/v1/scan/{scan_id}/pii_details
Get Scan Pii Details
get_scan_pii_details_v1_scan__scan_id__pii_details_get 2 params → 200422
GET
/v1/scan/{scan_id}/feedback_details
Get Scan Feedbacks
get_scan_feedbacks_v1_scan__scan_id__feedback_details_get 1 param → 200422

Schemas 58

The contract defines 58 schemas that model the data the API accepts and returns. The most detailed are ScanSummaryProgressOut (22 properties), ScanData (21 properties), ScanSummaryOut (20 properties), ScanFinding (17 properties). Each schema is shown below with its type and property counts.

ScanDetailsOwaspCoverage
object
3 properties 3 required
PaginatedPiiResponse
object
2 properties 2 required
Feedback
object
3 properties 2 required
CountOut
object
1 property 1 required
ScanDetailsEndpoint
object
3 properties 3 required
FalsePositiveLLMResult
object
The direct, typed result from an LLM for a false positive query.
3 properties 3 required
VulnerabilityInstanceRelevance
string
Severity
integer
FindingDetails
object
2 properties 2 required
ScanDuration
object
1 property
ScanDetailsMetadata
object
6 properties 6 required
PiiDetailsItem
object
5 properties 5 required
PaginatedScanCurrentOut
object
2 properties 2 required
PaginatedFindingsResponse
object
2 properties 2 required
OwaspCoverage
object
3 properties 3 required
ScanWarning
object
8 properties 4 required
ScanDetailsFeedback
object
3 properties 2 required
BusinessImpactAnalysis-Output
object
Represents a claim that a finding is a false positive.
6 properties 5 required
ScanDetailsFinding
object
3 properties 3 required
RunRemoteScanRequestBody
object
4 properties 3 required
ScanDetailsEndpointTrafficItem
object
9 properties 9 required
ScanSummaryProgressOut
object
22 properties 19 required
RunRemoteHarScanRequestBody
object
3 properties 3 required
BusinessImpactLLMResult-Output
object
The direct, typed result from an LLM for a business impact query.
2 properties 2 required
PiiSeenItem
object
5 properties 4 required
ApprovalUpdateRequest
object
1 property 1 required
PaginatedTrafficResponse
object
2 properties 2 required
Conclusion
string
Enum for the conclusion of a false positive analysis: YES, NO, or INCONCLUSIVE.
CreateScanRequestBody
object
3 properties 2 required
ScanConfigOut
object
6 properties 5 required
ScanSummaryProgressType
string
ScanSummaryOut
object
20 properties 17 required
ScanData
object
21 properties 13 required
ScanAttackConfig
object
1 property 1 required
ScanExecutionProgressUpdateRequest
object
7 properties 7 required
ScanReportFalsePositiveAnalysis
object
Represents a collection of false positive claims for a specific scan.
2 properties 2 required
HTTPValidationError
object
1 property
AnalysisEndpoint
object
7 properties 6 required
ValidationError
object
3 properties 3 required
UploadReportRequest
object
2 properties 1 required
Endpoint
object
2 properties 2 required
Source
object
3 properties 2 required
EntitiesRelationships
object
Represents a collection of entity relationships.
1 property 1 required
ScanDetailsEndpointItem
object
5 properties 5 required
FeedbackSeverity
string
EntityRelationship
object
3 properties 3 required
VulnerabilitiesDetails-Output
object
1 property 1 required
ScanSummary
object
14 properties 13 required
ScanFinding
object
17 properties 14 required
ScanCurrentOut
object
15 properties 14 required
AttackCandidate
object
3 properties 3 required
VulnerabilityDefinition
object
2 properties 2 required
GraphqlSeenItem
object
2 properties 2 required
FalsePositiveClaim-Output
object
Represents a claim that a finding is a false positive.
6 properties 5 required
ScanReportBusinessImpactAnalysis
object
Represents a collection of business impact analysis for a specific scan.
2 properties 2 required
OwaspStatus
string
ScanCreateOut
object
1 property 1 required
PaginatedEndpointsResponse
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

pynt-scan-api-openapi.yml Raw ↑

Other APIs Pynt publishes across the network.

Pynt Alive API
Pynt API Key API
Pynt Application API
Pynt Artifacts API
Pynt Auth API
Pynt Aws Marketplace API
Pynt Config API
Pynt Endpoint Group API
Pynt Endpoint Llm Analysis API
Pynt Event Logs API
Pynt Evidence API
Pynt Integrations API
Where this information came from

This is an independent, third-party profile of Pynt Scan 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.