SonarQube Web API
Official vendor OpenAPI document · agent-readySecurityThreat Detectionbasic, bearer7 EndpointsREST
For Agents
Programmatically validate credentials, logout. Covers 7 operations with basic, bearer authentication.
Use for: I need to validate credentials, I want to logout, Search for projects, Find all issues
Not supported: Does not handle payments, communications, or crm - use for security only.
SonarQube/SonarCloud Web API for code quality and security analysis. Provides access to projects, issues, measures, users, and more. The API exposes 7 endpoints secured with basic, bearer authentication.
Install Jentic One Beta
Connect the SonarQube Web API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SonarQube Web API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsonarqube.org%2Fsonarqube" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsonarqube.org%2Fsonarqube" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with SonarQube Web API.
Validate credentials
Logout
Search projects
Get component measures
List web services
Use Cases
Patterns agents use SonarQube Web API for, with concrete tasks.
★ Security Operations
Use the SonarQube Web API to perform security operations programmatically. The API provides 7 endpoints covering core functionality including validate credentials, logout, search projects.
Call GET /authentication/validate to validate credentials
Automated authentication Management
Automate authentication operations by combining multiple SonarQube Web API endpoints. Agents can logout and then search projects in a single workflow.
Call POST /authentication/logout to logout, then verify the result
AI Agent Integration via Jentic
AI agents discover and call SonarQube Web API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic, bearer tokens manually.
Search Jentic for 'validate credentials', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
7 endpoints — sonarqube/sonarcloud web api for code quality and security analysis.
METHOD
PATH
DESCRIPTION
GET
/authentication/validate
Validate credentials
POST
/authentication/logout
Logout
GET
/projects/search
Search projects
GET
/issues/search
Search issues
GET
/measures/component
Get component measures
GET
/ce/activity
Get compute engine tasks
GET
/webservices/list
List web services
GET
/authentication/validate
Validate credentials
POST
/authentication/logout
Logout
GET
/projects/search
Search projects
GET
/issues/search
Search issues
GET
/measures/component
Get component measures
GET
/ce/activity
Get compute engine tasks
GET
/webservices/list
List web services
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the SonarQube Web API by hand means choosing between basic and token bearer auth, pointing at either the sonarcloud.io/api host or a local SonarQube host, and handling paging and retries on its search calls yourself. Through Jentic you install once, import the SonarQube Web API from the API Directory, store the token once, and your agent calls it.
Permission scoping
The SonarQube Web API targets projects and issues through query parameters rather than resource ids in the URL path, so scope the agent to the operations it needs, such as searching projects, searching issues, or reading component measures. You choose the operations it may call, so state-changing ones like logging a user out are not included unless you add them.
Credential isolation
Your SonarQube token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'search issues in a project' or 'read component measures', and Jentic returns the matching SonarQube Web API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Snyk
Alternative security API
Choose Snyk when you need a different approach to security operations
FAQs
Specific to using SonarQube Web API through Jentic.
What authentication does the SonarQube Web API use?
The SonarQube Web API uses basic, bearer authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I validate credentials with the SonarQube Web API?
Yes. Use the GET /authentication/validate endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the SonarQube Web API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I validate credentials through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'validate credentials'. Jentic returns the matching SonarQube Web API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the SonarQube Web API have?
The SonarQube Web API exposes 7 endpoints covering authentication, projects, issues operations.
Can I limit what my agent is allowed to do with the SonarQube Web API?
Yes. Because you run Jentic One yourself, your own rules decide which SonarQube operations and credentials your agent can use. You can scope it to read-only calls such as searching projects, searching issues, or reading component measures, and leave out state-changing operations like logging a user out unless you explicitly grant them. The stored SonarQube token is injected only for the operations you allow, so the agent can never reach endpoints you have not enabled.
GET STARTED