Sonarcloud SonarQube Web API
✓ Official Vendor SpecSocial MediaSocial Managementbasic, bearer156 EndpointsREST
For Agents
Programmatically logout a user., check credentials. returns true for anonymous user.. Covers 156 operations with basic, bearer authentication.
Use for: I need to logout a user., I want to check credentials. returns true for anonymous user., Search for for tasks.<br> either componentid or component can be provided, but not b, Find all returns ce activity related metrics.<br>requires 'administer' permission on the
Not supported: Does not handle payments, communications, or crm — use for social media only.
SonarQube/SonarCloud Web API for code quality and security analysis management. Provides endpoints for managing projects, issues, quality gates, quality profiles, rules, measures, and more. The API exposes 156 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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.
Logout a user.
Check credentials. Returns true for anonymous user.
Search for tasks.<br> Either componentId or component can be provided, but not b
Returns CE activity related metrics.<br>Requires 'Administer' permission on the
Get the pending tasks, in-progress tasks and the last executed task of a given c
Give Compute Engine task details such as type, status, duration and associated c
Use Cases
Patterns agents use SonarQube Web API for, with concrete tasks.
★ Social Media Operations
Use the SonarQube Web API to perform social media operations programmatically. The API provides 156 endpoints covering core functionality including logout a user., check credentials. returns true for anonymous user., search for tasks.<br> either componentid or component can be provided, but not b.
Call POST /authentication/logout to logout a user.
Automated authentication Management
Automate authentication operations by combining multiple SonarQube Web API endpoints. Agents can check credentials. returns true for anonymous user. and then search for tasks.<br> either componentid or component can be provided, but not b in a single workflow.
Call GET /authentication/validate to check credentials. returns true for anonymous user., 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 'logout a user.', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
156 endpoints — sonarqube/sonarcloud web api for code quality and security analysis management.
METHOD
PATH
DESCRIPTION
POST
/authentication/logout
Logout a user.
GET
/authentication/validate
Check credentials. Returns true for anonymous user.
GET
/ce/activity
Search for tasks.<br> Either componentId or component can be provided, but not b
GET
/ce/activity_status
Returns CE activity related metrics.<br>Requires 'Administer' permission on the
GET
/ce/component
Get the pending tasks, in-progress tasks and the last executed task of a given c
GET
/ce/task
Give Compute Engine task details such as type, status, duration and associated c
GET
/components/search
Search for projects. Used to provide the ability to search for any component but
GET
/components/show
Returns a component (file, directory, project) and its ancestors. The ancestors
POST
/authentication/logout
Logout a user.
GET
/authentication/validate
Check credentials. Returns true for anonymous user.
GET
/ce/activity
Search for tasks.<br> Either componentId or component can be provided, but not b
GET
/ce/activity_status
Returns CE activity related metrics.<br>Requires 'Administer' permission on the
GET
/ce/component
Get the pending tasks, in-progress tasks and the last executed task of a given c
GET
/ce/task
Give Compute Engine task details such as type, status, duration and associated c
GET
/components/search
Search for projects. Used to provide the ability to search for any component but
GET
/components/show
Returns a component (file, directory, project) and its ancestors. The ancestors
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
SonarQube Web API basic, bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'logout a user.') and Jentic returns the matching SonarQube Web API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct SonarQube Web API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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 the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I logout a user. with the SonarQube Web API?
Yes. Use the POST /authentication/logout 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 logout a user. through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'logout a user.'. 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 156 endpoints covering authentication, ce, components operations.
GET STARTED