Research Academy
My account Customers About Blog Careers Legal Contact Resellers
The Burp Suite User Forum was discontinued on the 1st November 2024.

Burp Suite User Forum

For support requests, go to the Support Center. To discuss with other Burp users, head to our Discord page.

SUPPORT CENTER DISCORD

Initiating on demand scan using GraphQL

Abbas | Last updated: Apr 30, 2021 03:54PM UTC

Been trying to initiate an on demand scan using GraphQL API, but can only seem to schedule them. Is this possible? If someone could point me in the right direction i'd appreciate it, i've checked out the documentation but couldn't find what i was looking for.

Abbas | Last updated: Apr 30, 2021 04:31PM UTC

I've found the solution for that now. However i've just noticed a bug. When using the following to initiate a scan; mutation CreateScheduleItem($input: CreateScheduleItemInput!) { create_schedule_item(input: $input) { schedule_item { id } } } It responds back with an ID (in this case 182) but when checking the scan status with this request: query GetScan ($id: ID!) { scan(id: $id) { id status agent { id name } site_application_logins { login_credentials { label username } recorded_logins { label } } audit_items { id issue_counts { total } number_of_requests } scan_configurations { id name } } } It tells me that scan cannot be found. After checking the BS Dashboard, i noticed the ID has actually jumped a digit to 183. So the output of the first request is incorrect compared to the dashboard.

Abbas | Last updated: Apr 30, 2021 04:31PM UTC

I've found the solution for that now. However i've just noticed a bug. When using the following to initiate a scan; mutation CreateScheduleItem($input: CreateScheduleItemInput!) { create_schedule_item(input: $input) { schedule_item { id } } } It responds back with an ID (in this case 182) but when checking the scan status with this request: query GetScan ($id: ID!) { scan(id: $id) { id status agent { id name } site_application_logins { login_credentials { label username } recorded_logins { label } } audit_items { id issue_counts { total } number_of_requests } scan_configurations { id name } } } It tells me that scan cannot be found. After checking the BS Dashboard, i noticed the ID has actually jumped a digit to 183. So the output of the first request is incorrect compared to the dashboard.

Hannah, PortSwigger Agent | Last updated: May 03, 2021 12:34PM UTC