Platform

Platform overview How it works Authorization testing Evidence & reports Private scanning Integrations

Solutions

Security agencies Product teams Regulated industries Partner programme

Learn

Blog Knowledge hub Compare

Resources

Pricing Documentation Help centre FAQ Security & data What we haven’t proved

Company

About Contact Careers Sign in to the platform Start a $199 pilot →

Home / Help centre / Integrations & API

Integrations & API

Can I search across targets, profiles, schedules, issues and scans at once?

Quick answer

Yes. GET /api/search runs one global search across targets, profiles, schedules, issues and scans in a single call. Your token's owner needs the search:read permission, and results follow the permissions and group scope that owner holds.

The short version

Yes. One call searches five kinds of object at once. You do not need to query each list on its own.

How it works in Cyberlop

The route is GET /api/search. The API reference describes it as a global search across targets, profiles, schedules, issues and scans. It sits in the "Groups, tags & search" section and needs search:read.

ObjectWhat a match returns
TargetsApplications under assessment
ProfilesScan configurations
SchedulesRecurring or one-off runs
IssuesFindings
ScansScan runs

Search respects what the token's owner may see. A narrow role finds less, even when a record exists. That is deliberate, and it keeps a script from reading outside its lane.

The page does not list the query parameter name, so check the downloaded OpenAPI spec for the exact name and the shape of the response. Our own screens keep search local to each list. For example, the Issues page has a box that reads "Search findings by title or location...", and the Scan Profiles page has its own search and a tag filter.

What to do next

Use global search when you know a word but not where it lives, such as part of a target name or a finding title. Use the specific list routes when you already know the object type, because they take filters like severity and scan ID. Compare it with pulling the findings for one scan.

New to the API? Start with how to authenticate requests, and keep how to find an endpoint and its permission close by.

Full tutorial

Cyberlop API reference: authentication, permissions and the OpenAPI spec

Step-by-step, with annotated screenshots.

Updated · Back to the help centre

Wiring it into your pipeline?

Share what you are building and we will help you set up the right token, profile and job.