canonical: https://jentic.com/apis/securityscorecard.io/securityscorecard

# SecurityScorecard API

REST API for the SecurityScorecard platform: manage portfolios, companies, scores, findings, and integrations. This documentation is built from two kinds of sources. Internal API docs (`servicesWithInternalApiDocs`) Specs are fetched at runtime from other microservices/repositories. Those sections are dynamic and reflect the live specs exposed by each service. - [audit](https://users.prod.ssc.camp. The API exposes 683 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create a new portfolio, get all portfolios you have access to. Covers 683 operations with apiKey authentication.

## Scope

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

## Capabilities

- Create a new portfolio
- Get all portfolios you have access to
- Add companies in bulk to a portfolios
- Edit a portfolio
- Delete a portfolio
- Remove all companies from a portfolio

## Use cases

### Security Operations

Use the SecurityScorecard API to perform security operations programmatically. The API provides 683 endpoints covering core functionality including create a new portfolio, get all portfolios you have access to, add companies in bulk to a portfolios.

Example prompt: Call POST /portfolios to create a new portfolio

### Automated Actions Management

Automate actions operations by combining multiple SecurityScorecard API endpoints. Agents can get all portfolios you have access to and then add companies in bulk to a portfolios in a single workflow.

Example prompt: Call GET /portfolios to get all portfolios you have access to, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SecurityScorecard 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 'create a new portfolio', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/portfolios` | Create a new portfolio |
| GET | `/portfolios` | Get all portfolios you have access to |
| PUT | `/portfolios/companies/bulk-upload` | Add companies in bulk to a portfolios |
| PUT | `/portfolios/{portfolio_id}` | Edit a portfolio |
| DELETE | `/portfolios/{portfolio_id}` | Delete a portfolio |
| GET | `/portfolios/{portfolio_id}/companies` | Get all companies in a portfolio |
| DELETE | `/portfolios/{id}/companies/all` | Remove all companies from a portfolio |
| PUT | `/portfolios/{portfolio_id}/companies/{domain}` | Add company to portfolio |

## Key resources

- **Actions** — Operations for actions
- **Apps** — Operations for apps
- **Audits** — Operations for audits
- **Companies** — Operations for companies
- **Compliance Frameworks** — Operations for compliance frameworks

## Why Jentic

- **Setup:** Wiring the SecurityScorecard API by hand means sending its key in the Authorization header, navigating a large surface of hundreds of endpoints, and building each portfolio and company request yourself. Through Jentic you install once, import SecurityScorecard from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** SecurityScorecard puts the portfolio id in the URL path (`/portfolios/{portfolio_id}/...`), so a rule can pin your agent to one portfolio: it can list that portfolio's companies and nothing else. You choose the operations it may call, so destructive ones like deleting a portfolio or removing all its companies are not included unless you add them.
- **Credential handling:** Your SecurityScorecard 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 'list companies in a portfolio' or 'create a portfolio', and Jentic returns the matching SecurityScorecard 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 SecurityScorecard API use?

The SecurityScorecard API uses an API key passed in the `Authorization` 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 create a new portfolio with the SecurityScorecard API?

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

### What are the rate limits for the SecurityScorecard 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 create a new portfolio through Jentic?

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

### How many endpoints does the SecurityScorecard API have?

The SecurityScorecard API exposes 683 endpoints covering actions, apps, audits operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which SecurityScorecard operations and credentials the agent can use. SecurityScorecard puts the portfolio id in the URL path, such as `/portfolios/{portfolio_id}/companies`, so a rule can pin the agent to a single portfolio and let it only list that portfolio's companies. You choose the operations it may call, so destructive ones like DELETE `/portfolios/{portfolio_id}` or removing all companies from a portfolio stay off limits unless you add them.