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 Vulnerability Instance API

The vulnerability-instance API from Pynt — 5 operation(s) for vulnerability-instance.

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

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

This API exposes 5 operations across 5 paths, and defines 15 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.

5 operations 5 paths 15 schemas 2 GET1 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 Vulnerability Instance 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 5

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

vulnerability-instance 5
GET
/v1/vulnerability-instance
List Vulnerability Instances
list_vulnerability_instances_v1_vulnerability_instance_get 1 param → 200422
GET
/v1/vulnerability-instance/{vulnerability_instance_id}
Find Vulnerability Instance By Id
find_vulnerability_instance_by_id_v1_vulnerability_instance__vulnerability_instance_id__get 1 param → 200422
PUT
/v1/vulnerability-instance/{vulnerability_instance_id}/relevance
Update Vulnerability Instance Relevance
update_vulnerability_instance_relevance_v1_vulnerability_instance__vulnerability_instance_id__relevance_put 1 param body → 200422
PUT
/v1/vulnerability-instance/{vulnerability_instance_id}/tags
Update Vulnerability Instances Tags
update_vulnerability_instances_tags_v1_vulnerability_instance__vulnerability_instance_id__tags_put 1 param body → 200422
POST
/v1/vulnerability-instance/{vulnerability_instance_id}/ticket/jira
Create Ticket Jira
create_ticket_jira_v1_vulnerability_instance__vulnerability_instance_id__ticket_jira_post 1 param body → 201422

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are VulnerabilityInstanceOut (12 properties), Finding (10 properties), EndpointAttackInfo (6 properties), JiraCreateTicketRequest (5 properties). Each schema is shown below with its type and property counts.

Finding
object
10 properties 1 required
VulnerabilityDefinition
object
2 properties 2 required
VulnerabilityScope
string
JiraCreateTicketRequest
object
5 properties 4 required
VulnerabilityScopeInfo-Output
object
3 properties 2 required
VulnerabilityInstanceRelevance
string
PaginatedVulnerabilityInstancesOut
object
2 properties 2 required
HTTPValidationError
object
1 property
Body_update_vulnerability_instances_tags_v1_vulnerability_instance__vulnerability_instance_id__tags_put
object
1 property 1 required
ValidationError
object
3 properties 3 required
VulnerabilityInstanceOut
object
12 properties 10 required
VulnerabilityInstanceStatus
string
EndpointAttackInfo
object
6 properties 4 required
Body_update_vulnerability_instance_relevance_v1_vulnerability_instance__vulnerability_instance_id__relevance_put
object
1 property 1 required
Ticket
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

pynt-vulnerability-instance-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 Vulnerability Instance 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.