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

ProjectDiscovery configurations API

The configurations API from ProjectDiscovery — 6 operation(s) for configurations.

ProjectDiscovery configurations API is one of 20 APIs that ProjectDiscovery publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

Requests are made against 3 base URLs: https://api.projectdiscovery.io, https://api.dev.projectdiscovery.io, http://localhost:8085.

13 operations 6 paths 5 schemas 3 DELETE4 GET2 PATCH4 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.projectdiscovery.io
Authentication
API Key
Resource Areas
1

Authentication & Security 1

ProjectDiscovery configurations API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-API-Key (X-API-Key). By default, every request must be authenticated.

Paths & Operations 13

Across 6 paths, the API surfaces 13 operations — 3 DELETE, 4 GET, 2 PATCH, 4 POST. Each is listed below with its method, path, parameters, and response codes.

configurations 13
GET
/v1/scans/config
Get Configs List
get-v1-scans-config 5 params → 200400401403500default
POST
/v1/scans/config
Add Config
post-v1-scans-config 1 param body → 200400401403500default
GET
/v1/scans/config/{config_id}
Get Config
get-v1-scans-config-config_id 3 params → 200400401403500default
PATCH
/v1/scans/config/{config_id}
Update Config
patch-v1-scans-config-config_id 3 params body → 200400401403500default
DELETE
/v1/scans/config/{config_id}
Delete Config
delete-v1-scans-config-config_id 2 params → 200400401403500default
GET
/v1/scans/config/exclude
Get excluded templates
get-scans-config-exclude 1 param → 200400401500default
POST
/v1/scans/config/exclude
Add excluded templates and targets
post-scans-config-exclude 1 param body → 200400401500default
DELETE
/v1/scans/config/exclude
Delete excluded templates or targets by ids
delete-scans-config-exclude 1 param body → 200400401500default
GET
/v1/scans/config/severity
Get custom severity mappings
get-v1-scans-config-severity 1 param → 200400401404500default
POST
/v1/scans/config/severity
Add custom severity mapping
post-v1-scans-config-severity 1 param body → 200400401404500default
DELETE
/v1/scans/config/severity
Delete custom severity mapping
delete-v1-scans-config-severity 1 param body → 200400401404500default
PATCH
/v1/scans/config/{config_id}/severity
Modify custom severity mapping
patch-v1-scans-config-config_id-severity 2 params body → 200400401404500default
POST
/v1/scans/config/verify
Verify Config
post-v1-scans-config-verify 1 param body → 200400401500default

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are ConfigResponse (9 properties), ExcludedTemplate (7 properties), CustomSeverityMapping (7 properties). Each schema is shown below with its type and property counts.

ConfigTypeEnum
string
ExcludeConfigRequestType
string
ConfigResponse
object
9 properties 6 required
CustomSeverityMapping
object
7 properties 6 required
ExcludedTemplate
object
7 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

projectdiscovery-configurations-api-openapi.yml Raw ↑

Other APIs ProjectDiscovery publishes across the network.

ProjectDiscovery Asset API
ProjectDiscovery assets API
ProjectDiscovery chaos API
ProjectDiscovery enumerations API
ProjectDiscovery export API
ProjectDiscovery history API
ProjectDiscovery internal API
ProjectDiscovery Leaks API
ProjectDiscovery results API
ProjectDiscovery retests API
ProjectDiscovery scan_log API
ProjectDiscovery scans API
Where this information came from

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