Dradis Pro API

Name: Dradis Pro API API
Brand: Dradis Pro API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentSecurityVulnerability ManagementapiKey39 EndpointsREST

For Agents

Manage Dradis Pro projects, issues, evidence, and notes so an agent can ingest scanner findings and assemble penetration test deliverables.

Quickstart

Get started with Dradis Pro API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a Dradis issue"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Dradis Pro API API.

Create and manage penetration test projects with full CRUD on /projects

Add nodes representing hosts, applications, or scopes within a Dradis project

Track vulnerabilities as issues with create, update, and delete operations

Attach evidence to nodes to capture proof-of-exploit findings per scope element

GET STARTED

Start building with Dradis Pro API API

Explore with Jentic

View OpenAPI Document

Use for: I need to create a new penetration test project in Dradis Pro, Add a host node to a Dradis project for scope tracking, Log a new vulnerability issue against a Dradis project, Attach evidence of an exploit to a specific Dradis node

Not supported: Does not run vulnerability scans, exploit hosts, or generate the rendered report PDF — use for engagement data management within Dradis Pro only.

Jentic publishes the only available OpenAPI document for Dradis Pro API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Dradis Pro API, keeping it validated and agent-ready. Dradis Pro is a collaboration and reporting platform built for information security teams running penetration tests, vulnerability assessments, and red team engagements. The API exposes the full project lifecycle — projects, nodes, issues, evidence, notes, content blocks, document properties, and tags — so engagements can be created, populated, and reported on programmatically. Authentication is via a token in the Authorization header, suitable for headless ingestion of scanner output and automated report assembly.

Use Cases

Patterns agents use Dradis Pro API API for, with concrete tasks.

★ Scanner Output Ingestion

Pipe vulnerability scanner output into Dradis Pro by creating issues, nodes, and evidence in bulk. The agent calls POST /projects to bootstrap the engagement, POST /nodes for each in-scope host, POST /issues for each finding, and POST /nodes/{nodeId}/evidence to attach the scanner detail. This replaces manual copy-paste from scanner UIs into Dradis.

Create a Dradis project via POST /projects, add a node for host '10.0.0.5' via POST /nodes, then POST /issues for a 'CVE-2024-1234' finding and attach scanner output as evidence.

Engagement Retest Updates

After a remediation cycle, update Dradis issues with retest results so the final report reflects current state. The agent fetches GET /issues to enumerate findings, then PUTs each issue with the retested status and any new evidence. This keeps the engagement timeline auditable without rebuilding the project from scratch.

Iterate GET /issues for project id 42, then PUT /issues/{issueId} for each closed finding to update its status to 'remediated'.

Per-Host Notes and Evidence Capture

Capture analyst notes and proof-of-exploit evidence at the node level so reviewers can trace each finding back to a specific host or application. The agent uses POST /nodes/{nodeId}/notes for commentary and POST /nodes/{nodeId}/evidence for the artefact body, keeping the engagement file structured for the final report assembly.

On node id 7, POST /nodes/7/notes with an analyst observation and POST /nodes/7/evidence with the proof-of-exploit body.

Final Report Assembly

Pull the assembled engagement contents — projects, nodes, issues, evidence, and content blocks — from Dradis to feed an external report generator or data warehouse. The agent reads each list endpoint and writes the structured payload to the destination, complementing Dradis's own report rendering when teams maintain a custom report pipeline.

For project id 42, list nodes via GET /nodes, list issues via GET /issues, and pull each node's evidence via GET /nodes/{nodeId}/evidence to build a structured engagement export.

AI Agent Engagement Triage

Through Jentic, an AI agent can take 'log this Burp finding into the Acme engagement' and resolve it to the Dradis Pro issue creation operation without browsing docs. Jentic injects the token from the vault and validates the issue payload schema. End-to-end setup is under an hour from sign-up versus a day of manual integration work.

Use Jentic search for 'create a Dradis issue', load the POST /issues operation, and execute it with the engagement project id, finding title, and description.

Key Endpoints

39 endpoints — jentic publishes the only available openapi specification for dradis pro api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/projects

Create a project

GET

/projects

List projects

POST

/nodes

Create a node

POST

/issues

Create an issue

GET

/issues

List issues in a project

POST

/nodes/{nodeId}/evidence

Create evidence on a node

POST

/nodes/{nodeId}/notes

Create a note on a node

POST

/projects

Create a project

GET

/projects

List projects

POST

/nodes

Create a node

POST

/issues

Create an issue

GET

/issues

List issues in a project

POST

/nodes/{nodeId}/evidence

Create evidence on a node

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Dradis Pro tokens are stored encrypted in the Jentic vault and injected as the Authorization header at execution time. Agents receive a scoped reference, never the raw token.

Intent-based discovery

Agents search by intent (e.g. 'create a Dradis issue') and Jentic returns the POST /issues operation with its input schema, so the agent posts the right finding without reading docs.

Time to first call

Direct Dradis Pro integration: 1-2 days for auth, project bootstrapping, and bulk-issue import logic. Through Jentic: under an hour from sign-up to first issue created.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Tenable Attack Surface Management API

Tenable surfaces vulnerabilities; Dradis is where the engagement narrative and report content live.

Use Tenable when the agent needs to detect or enumerate vulnerabilities. Use Dradis to record those findings as engagement issues with evidence.

Complementary

Rapid7 API

Rapid7 runs scans and exposure analysis; Dradis hosts the consolidated engagement record.

Use Rapid7 to source scan output and exposure data. Use Dradis to ingest those findings into a structured pentest project.

Complementary

Snyk API

Snyk identifies code and dependency issues; Dradis catalogues them within an engagement deliverable.

Use Snyk for application and dependency vulnerability discovery. Use Dradis when those findings need to land in an engagement report.

FAQs

Specific to using Dradis Pro API API through Jentic.

Why is there no official OpenAPI spec for Dradis Pro API?

Dradis Pro does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Dradis Pro API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Dradis Pro API use?

Dradis Pro uses a token in the Authorization header. Through Jentic, that token is stored encrypted in the vault and injected at execution time, so it never enters the agent's prompt or response.

Can I create issues and attach evidence with the Dradis Pro API?

Yes. POST /issues creates a finding within a project, and POST /nodes/{nodeId}/evidence attaches proof-of-exploit content to a specific host or scope element. Together they let you build the structured engagement record.

How do I import scanner findings into Dradis through Jentic?

Run pip install jentic, search for 'create a Dradis issue', load the POST /issues operation, and execute it once per scanner finding. Pair with POST /nodes/{nodeId}/evidence to attach the scanner output to the relevant host.

Can I list all issues in a project?

Yes. GET /issues returns the findings recorded against a project, useful for building dashboards or driving retest workflows. GET /projects lists projects so you can discover ids first.

What are the rate limits for the Dradis Pro API?

The published spec does not declare explicit per-endpoint limits. For self-hosted Dradis Pro instances, the limit is effectively the host capacity. Implement client-side throttling for bulk imports and treat 429s as the signal to back off.