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

How do I list my targets through the API?

Quick answer

Call GET /api/targets with a Bearer token whose owner holds target:read. You get every target you may see, each with a rollup of its latest scan and its severity counts. Use GET /api/targets/:id for one target.

Steps

  1. Send your Bearer token with the request.
  2. Call GET /api/targets. It needs target:read.
  3. Read each entry. It includes the latest-scan rollup and severity counts, which matches the dots and counts you see on the Targets page.
  4. For one application, call GET /api/targets/:id.
  5. To get a file, call GET /api/export/targets and add ?format=json or ?format=csv.

Good to know

The list shows targets within the permissions and group scope of the token's owner. Two tokens can therefore return different lists from the same organisation.

Targets never change after you create them. The API reference says as much: a target is immutable. There is no update route, only create with POST /api/targets and delete with DELETE /api/targets/:id. Be careful with delete, because it also removes the target's profiles, schedules, scans and findings.

RoutePermissionReturns
GET /api/targetstarget:readAll visible targets, with rollups
GET /api/targets/:idtarget:readOne target
GET /api/export/targetstarget:readA JSON or CSV file

Use the list to build a dashboard of your own, to check that every app you care about has a recent scan, or to feed a ticket system with severity counts. For a ready-made overview, the app has its Dashboard, and the dashboard endpoint gives you the same figures. When a call fails, read why the API says no.

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.