canonical: https://jentic.com/apis/ssllabs.com/ssllabs

# SSL Labs API

Qualys SSL Labs Assessment API v4 for testing SSL/TLS servers available on the public Internet. Provides detailed analysis of SSL configuration, certificate chain, and security vulnerabilities. The API exposes 6 endpoints secured with apiKey authentication.

## For AI agents

Programmatically register for API access, check ssl labs availability and get engine info. Covers 6 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for security only.

## Capabilities

- Register for API access
- Check SSL Labs availability and get engine info
- Invoke assessment or check progress
- Retrieve detailed endpoint information
- Monitor SSL Labs API operational status and events

## Use cases

### Security Operations

Use the SSL Labs API to perform security operations programmatically. The API provides 6 endpoints covering core functionality including register for API access, check ssl labs availability and get engine info, invoke assessment or check progress.

Example prompt: Call POST /register to register for API access

### Automated Analysis Management

Automate analysis operations by combining multiple SSL Labs API endpoints. Agents can check ssl labs availability and get engine info and then invoke assessment or check progress in a single workflow.

Example prompt: Call GET /info to check ssl labs availability and get engine info, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SSL Labs 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 apiKey tokens manually.

Example prompt: Search Jentic for 'register for API access', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/register` | Register for API access |
| GET | `/info` | Check SSL Labs availability and get engine info |
| GET | `/analyze` | Invoke assessment or check progress |
| GET | `/getEndpointData` | Retrieve detailed endpoint information |
| GET | `/getStatusCodes` | Retrieve known status codes |
| GET | `/getRootCertsRaw` | Retrieve root certificates used for trust validation |

## Key resources

- **Analysis** — SSL/TLS analysis endpoints
- **Information** — Service information
- **Registration** — API registration

## Why Jentic

- **Setup:** Wiring the SSL Labs API by hand means registering for API access on api.ssllabs.com/api/v4, carrying its key into each call, and polling analyze results yourself. Through Jentic you install once, import the SSL Labs API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** You can limit the agent to the operations it needs, such as analyzing a host or reading endpoint data, so it runs scans and reads results and never registers a new API key unless you add that operation.
- **Credential handling:** Your SSL Labs API key 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.
- **Discovery method:** Agents search Jentic by intent such as 'analyze the TLS configuration of a host' or 'get the endpoint scan results', and Jentic returns the matching SSL Labs API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Snyk** — Alternative security API
- **Crowdstrike** — Alternative security API

## FAQ

### What authentication does the SSL Labs API use?

The SSL Labs API uses an API key passed in the `email` header. 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 register for API access with the SSL Labs API?

Yes. Use the POST /register endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the SSL Labs 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 register for API access through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'register for API access'. Jentic returns the matching SSL Labs API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the SSL Labs API have?

The SSL Labs API exposes 6 endpoints covering analysis, information, registration operations.

### Can I limit what my agent is allowed to do with the SSL Labs API?

Yes. Because you run Jentic One yourself, you decide which SSL Labs operations your agent may call and which credentials it may use. You can allow just the read paths, such as analyzing a host with GET /analyze and reading endpoint results with GET /getEndpointData, while withholding POST /register so the agent can run scans and read results but never registers a new API key. The operations you do not grant are simply unavailable to the agent.