You can now start Savant Pathseeker tests from your own tools and pipelines using the Bugcrowd API. Use it to retest a staging environment after each release, start a test from a CI/CD pipeline such as GitHub Actions, or run tests on your own schedule.
What’s new
- Allow API-triggered runs: a new option in Pathseeker test setup. Turn it on for each test you want to start from automation.
- Configuration ID: after you turn on the option, the platform shows setup instructions and the test’s Configuration ID. You can reopen the instructions from the test’s Test Overview page.
- New endpoint:
POST /scan_configurations/{id}/scan_executionsstarts a new run of an existing Pathseeker test using the targets, credentials, and settings already saved for it. Available in API version 1.2.0. - Run traceability: each API-triggered run records the token owner, the time, and a
trigger_sourcelabel you provide (for example,github-actions).
How it works
- Turn on Allow API-triggered runs when you set up a Pathseeker test, and copy the Configuration ID.
- Create a Bugcrowd API credential pinned to major version V1.
- Send a
POSTrequest to start the test. Monitor progress and review findings in the platform.
API-triggered tests use your Pathseeker test quota like any other test. Only one run per test configuration can be active at a time. Triggering tests requires the Organization Owner or Test Operator role.
For setup steps and examples, see Trigger Savant Pathseeker Tests.
