Multi-Target Engagements
A pentest credit is an engagement. Each tier includes an allowance of targets, so one launch can cover several hosts and produce a single combined report and a single signed attestation that lists every target.
Target allowance
| Tier | Price | Targets included | Agent hours |
|---|---|---|---|
| Audit-Ready | $99 | 1 | 4 |
| Threat-Hunt | $299 | up to 4 | 20 |
| Adversarial-Depth | $699 | up to 8 | 80 |
Agent hours are pooled across the engagement's targets. An extra target is always $99; the tier's allowance is the only discount.
Extra targets
Each extra target beyond the allowance uses one more credit. An Audit-Ready credit ($99) adds its 4 agent hours to the pool. Any credit you hold can serve as an extra, and it adds the agent hours of its own tier. An engagement covers at most 8 targets.
For example, 5 targets on Threat-Hunt is one Threat-Hunt credit ($299) plus one extra Audit-Ready credit ($99), for $398 and one report.
What counts as a target
A target is a hostname, IP address or cloud asset you have verified. example.com and www.example.com count as one target, so listing both does not use an extra credit. All targets must be verified, and none may already have an active pentest.
One report
An engagement produces one combined report and one signed attestation listing every target. Findings are filterable per target. If you want separate reports, launch separate single-target pentests.
If a target fails
If at least one target completes the tool phase, the engagement continues. The report lists each failed host as not tested, and no credit is refunded. If every target fails, every credit is refunded.
API usage
curl -X POST https://turbopentest.com/api/pentests \
-H "Authorization: Bearer $TURBOPENTEST_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"targetUrls": [
"https://app.example.com",
"https://api.example.com",
"https://admin.example.com"
],
"tier": "deep",
"repoUrl": "https://github.com/org/repo"
}'targetUrls takes 2 to 8 targets after twin hosts are collapsed. The launch spends one engagement credit plus one credit for each extra target.
Choosing the engagement credit
| Field | Type | Description |
|---|---|---|
tier | string | Tier of the credit that runs the engagement: standard, deep or blitz. The oldest available credit of that tier is used. |
creditId | string (UUID) | A specific available credit to run the engagement. Takes precedence over tier. |
If you hold credits of more than one tier, send tier or creditId; otherwise the launch returns 400 tier_required and nothing is spent. With a single tier held, the oldest available credit is used. A Recon credit covers one target, so it cannot run a multi-target engagement. Extra targets spend your cheapest available credits first.
Response
The response is 201 Created, or 202 Accepted when every target is capacity-queued.
{
"groupId": "uuid",
"primaryScanId": "uuid-1",
"engagement": {
"tier": "deep",
"targets": [
"https://app.example.com",
"https://api.example.com",
"https://admin.example.com"
],
"included": 4,
"extras": 0,
"agentHours": 20,
"twins": {}
},
"scans": [
{ "id": "uuid-1", "targetUrl": "https://app.example.com", "status": "queued" },
{ "id": "uuid-2", "targetUrl": "https://api.example.com", "status": "queued" }
],
"queuedScans": [
{ "id": "uuid-3", "targetUrl": "https://admin.example.com", "status": "capacity_queued" }
]
}The engagement object:
| Field | Type | Description |
|---|---|---|
tier | string | Tier of the engagement credit |
targets | string[] | The target URLs the engagement covers, after twin collapse |
included | number | Targets the engagement credit's tier includes |
extras | number | Extra credits spent for targets beyond the allowance |
agentHours | number | Agent hours pooled across the targets |
twins | object | Maps each collapsed twin host to the target it was merged into, for example { "https://www.example.com": "https://example.com" }; {} when none |
scans lists the targets launched immediately. Launching is capacity-aware: targets beyond the available capacity (or your concurrency limit) appear in queuedScans with status capacity_queued and launch automatically as capacity frees up.
The report and attestation for any member id resolve to the primary's combined deliverable. Download it with GET /api/pentests/{primaryScanId}/report.
Errors
| Status | Error | Meaning |
|---|---|---|
400 | too_many_targets | More than 8 targets after twin collapse |
400 | promo_not_supported_for_engagement | A promo code was sent with a multi-target launch |
400 | tier_required | You hold credits of more than one tier and sent neither tier nor creditId |
402 | insufficient_credits | No credit of the requested tier (the message names it), a Recon credit was picked, or not enough credits for the extras (the message names how many) |
409 | - | One of the targets already has an active pentest |
Limits
- Maximum 8 targets per engagement
- Each target must be verified and pass URL validation
- Each target can only appear once, and none of the targets may already have an active pentest
- Credits are consumed atomically - either the whole engagement is created or nothing is
- Schedules stay single-target: one target per schedule
Black Box, Gray Box and White Box
Understand black-box, gray-box and white-box pentesting in TurboPentest, what each covers, and when to add test credentials or connect GitHub source code.
Understanding Results
How to read TurboPentest findings - severity, CVSS scores, and evidence - and prioritize which vulnerabilities your team should remediate first.