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 Application API

The application API from Pynt — 21 operation(s) for application.

Pynt Application API is one of 32 APIs that Pynt publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Application. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

This API exposes 27 operations across 21 paths, and defines 64 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 21 paths 64 schemas 3 DELETE15 GET2 PATCH5 POST2 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 Application 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 21 paths, the API surfaces 27 operations — 3 DELETE, 15 GET, 2 PATCH, 5 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

application 27
GET
/v1/application/{application_id}/endpoint-llm-analysis
Get Endpoint Llm Analysis
get_endpoint_llm_analysis_v1_application__application_id__endpoint_llm_analysis_get 1 param → 200422
POST
/v1/application/{application_id}/scan-schedule
Create Scan Schedule
create_scan_schedule_v1_application__application_id__scan_schedule_post 1 param body → 201422
GET
/v1/application/{application_id}/scan-schedule
Get Scan Schedule By Application
get_scan_schedule_by_application_v1_application__application_id__scan_schedule_get 1 param → 200422
PATCH
/v1/application/{application_id}/scan-schedule/{scan_schedule_id}
Update Scan Schedule
update_scan_schedule_v1_application__application_id__scan_schedule__scan_schedule_id__patch 2 params body → 200422
DELETE
/v1/application/{application_id}/scan-schedule/{scan_schedule_id}
Delete Scan Schedule
delete_scan_schedule_v1_application__application_id__scan_schedule__scan_schedule_id__delete 2 params → 204422
PATCH
/v1/application/{application_id}/scan-schedule/{scan_schedule_id}/state
Update Scan Schedule State
update_scan_schedule_state_v1_application__application_id__scan_schedule__scan_schedule_id__state_patch 2 params body → 200422
GET
/v1/application
List Applications
list_applications_v1_application_get 1 param → 200422
PUT
/v1/application
Create Application
create_application_v1_application_put body → 200422
GET
/v1/application/count
Count Applications
count_applications_v1_application_count_get 1 param → 200422
GET
/v1/application/metadata
List Application Metadatas
list_application_metadatas_v1_application_metadata_get 1 param → 200422
GET
/v1/application/metadata/count
Count Application Metadatas
count_application_metadatas_v1_application_metadata_count_get 1 param → 200422
GET
/v1/application/metrics
Get Application Metrics
get_application_metrics_v1_application_metrics_get → 200
GET
/v1/application/{application_identifier}
Get Application
get_application_v1_application__application_identifier__get 1 param → 200422
POST
/v1/application/{application_id}
Update Application
update_application_v1_application__application_id__post 1 param body → 200422
DELETE
/v1/application/{application_id}
Delete Application By Id
delete_application_by_id_v1_application__application_id__delete 1 param → 204422
GET
/v1/application/{application_id}/metadata
Get Application Metadata By Id
get_application_metadata_by_id_v1_application__application_id__metadata_get 1 param → 200422
GET
/v1/application/{application_id}/metrics
Get Single Application Metrics
get_single_application_metrics_v1_application__application_id__metrics_get 1 param → 200422
GET
/v1/application/{application_id}/scans/running
Get Running Scans By Application Id
get_running_scans_by_application_id_v1_application__application_id__scans_running_get 1 param → 200422
GET
/v1/application/{application_id}/data-sources/{data_source_type}
Get Data Source
get_data_source_v1_application__application_id__data_sources__data_source_type__get 2 params → 200422
DELETE
/v1/application/{application_id}/data-sources/{data_source_type}
Delete Data Source
delete_data_source_v1_application__application_id__data_sources__data_source_type__delete 2 params → 204422
PUT
/v1/application/{application_id}/data-sources/Live Traffic
Legacy Live Traffic Put
legacy_live_traffic_put_v1_application__application_id__data_sources_Live_Traffic_put 1 param body → 200422
POST
/v1/application/{application_id}/data-sources
Upsert Data Source
upsert_data_source_v1_application__application_id__data_sources_post 1 param body → 200422
POST
/v1/application/{application_id}/endpoints
Create Endpoints
create_endpoints_v1_application__application_id__endpoints_post 1 param body → 201422
GET
/v1/application/{application_id}/pentest-report
Get Latest Pentest Report
get_latest_pentest_report_v1_application__application_id__pentest_report_get 1 param → 200422
POST
/v1/application/{application_id}/pentest-report
Create Pentest Report
create_pentest_report_v1_application__application_id__pentest_report_post 1 param → 201422
GET
/v1/application/{application_id}/pentest-report/{pentest_id}
Get Pentest Report
get_pentest_report_v1_application__application_id__pentest_report__pentest_id__get 2 params → 200422
GET
/v1/application/{application_id}/pentest-report-list
List Pentest Reports
list_pentest_reports_v1_application__application_id__pentest_report_list_get 1 param → 200422

Schemas 64

The contract defines 64 schemas that model the data the API accepts and returns. The most detailed are EndpointLLMAnalysis (28 properties), ScanSummaryProgressOut (22 properties), ApplicationMetadataOut (14 properties), ApplicationListItemOut (9 properties). Each schema is shown below with its type and property counts.

PiiItem
object
2 properties 2 required
UpdateScanScheduleStateRequest
object
1 property 1 required
CountOut
object
1 property 1 required
LastScansStatusSummary
object
7 properties
AppScanTargetOut
object
Scan target for a Pynt application's built collection. The client supplies only the integration type; the collection's S3 location is derived server-side from…
1 property
NewmanScanTargetOut
object
4 properties 2 required
OnlyOnceSpec
object
2 properties 1 required
CreateDayOfWeekSpec
object
3 properties 2 required
SwaggerDataSource
object
2 properties 2 required
ScanDuration
object
1 property
SyncStatus
string
DocsLinkType
string
SeveritySummary
object
5 properties
DayOfWeek
string
SourceFileType
string
CreateApplicationRequest
object
8 properties 1 required
HarScanTargetOut
object
3 properties 1 required
CreateScanScheduleRequest
object
2 properties 2 required
CreateDayIntervalSpec
object
3 properties 2 required
ApplicationsMetrics
object
2 properties
ScanSummaryProgressOut
object
22 properties 19 required
UpdateScanScheduleRequest
object
2 properties
DayOfWeekSpec-Output
object
3 properties 2 required
ApplicationListItemOut
object
9 properties 1 required
ScanSummaryProgressType
string
PathParameter
object
2 properties 2 required
ScanScheduleOut
object
7 properties 7 required
CreateEndpointRequest
object
6 properties 6 required
PostmanCollectionDataSource
object
2 properties 2 required
SwaggerFileDataSource
object
2 properties 2 required
PentestReportStatus
string
DayOfWeekSpec-Input
object
3 properties 2 required
YesNoQuestion
object
2 properties 1 required
CreateOnlyOnceSpec
object
2 properties 1 required
DataSourceOut
object
5 properties 5 required
AggregatedRisks
object
6 properties
ApplicationMetadataListOut
object
2 properties 2 required
ApplicationMetadataOut
object
14 properties 5 required
HTTPValidationError
object
1 property
ValidationError
object
3 properties 3 required
Endpoint
object
2 properties 2 required
Source
object
3 properties 2 required
DataSourceStatus
string
PostmanFileDataSource
object
2 properties 2 required
DayIntervalSpec-Input
object
3 properties 2 required
PentestReportOut
object
3 properties 3 required
LiveTrafficUpdateDataSourceRequest
object
1 property 1 required
EndpointLLMAnalysis
object
Business model — extends the LLM schema with application-level fields.
28 properties 4 required
UpdateApplicationRequest
object
4 properties
PentestReportListItemOut
object
3 properties 3 required
ScanDataSource
object
2 properties 2 required
SingleApplicationMetrics
object
5 properties 1 required
HarFileDataSource
object
2 properties 2 required
ScanType
string
UpdateDataSourceRequest
object
2 properties 1 required
ApplicationOut
object
8 properties 1 required
DayIntervalSpec-Output
object
3 properties 2 required
EndpointPropertiesInDB
object
7 properties
EndpointSource
object
2 properties 2 required
ScanExecutionStatus
string
ScheduleState
string
AuthenticationInfo
object
2 properties
ApplicationDataSourceOut
object
1 property 1 required
Body_create_endpoints_v1_application__application_id__endpoints_post
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

pynt-application-api-openapi.yml Raw ↑

Other APIs Pynt publishes across the network.

Pynt Alive API
Pynt API Key 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
Pynt Invite API
Where this information came from

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