My CI job can't trigger a scan. What should I check?

Why this happens

The trigger call, POST /api/ci/scan, is the front door for pipelines. It needs a valid token, a permission and a profile it may run. One missing piece stops the scan before it starts.

How to fix it

1. Open your repository or CI settings and confirm both CYBERLOP_URL and CYBERLOP_API_TOKEN exist. A masked variable looks the same in the log whether it is full or empty, so check the settings page, not the log.
2. Make sure CYBERLOP_URL is the app's base address. The snippet adds the /api/ci/scan path itself.
3. Look at the request header. It must read authorization: Bearer and then your token.
4. Ask an admin to check that the token's owner holds the ci:trigger permission. The API Reference shows it on the CI row.
5. Confirm the profile. The body takes a profileId or a profileName, and because the scan runs with the owner's permissions and group scope, a profile outside that scope will not start.
6. Open Settings → Plan & usage. The plan must include API and CI tokens, and the scans-at-once limit must have room. If the AI allowance ran out, scans pause until next month.
7. Send the same request with curl from a terminal. The reply shows whether the pipeline or the account is at fault.

Still not working?

The workflow only runs on a push to the main branch or by hand, so a feature branch will not trigger it. See when the CI workflow runs. For a lost token, read what to do if you lost your token. Still stuck? Share the request, without the token, through the contact page. The CI/CD integration tutorial covers the full setup.

Related questions

• Which secrets do I need to add to my repository for CI scans?
• Can I trigger a CI scan by profile name instead of profile ID?
• Whose permissions does a CI-triggered scan run with?
• My CI job can't scan a profile that a teammate can see. Why?
• My API token suddenly stopped working. Why?

Full tutorial

How to add security scanning to your CI/CD pipeline

Step-by-step, with annotated screenshots.

Updated 8 October 2026 · Back to the help centre