Checkmarx SCA Python API Docs | dltHub

Build a Checkmarx SCA-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

Checkmarx SCA is a platform for managing Software Composition Analysis projects, scan results, and risk reports via REST APIs. The REST API base URL is https://api-sca.checkmarx.net and all requests require an Authorization header with a Bearer token.

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading Checkmarx SCA data in under 10 minutes.


What data can I load from Checkmarx SCA?

Here are some of the endpoints you can load from Checkmarx SCA:

ResourceEndpointMethodData selectorDescription
scans/risk-management/scansGETRetrieve a list of scans for a project, supports pagination via size and page parameters
projects/risk-management/projectsGETRetrieve a list of projects in the account
scan_details/risk-management/scans/{scanId}GETRetrieve detailed information about a specific scan
scan_status/api/scans/{scanId}GETRetrieve the current status of a specific scan
analysis_requests/analysis/requests/{requestId}GETRetrieve detailed results from SCA file analysis

How do I authenticate with the Checkmarx SCA API?

Authentication uses a JWT (JSON Web Token) obtained via a POST /identity/connect/token request; this token must be included in the Authorization header of all subsequent requests in the format 'Bearer <access_token>'.

1. Get your credentials

To generate an API key for Checkmarx integrations, log in to the Checkmarx One web portal and navigate to 'Settings' > 'Identity and Access Management' in the main navigation. Once in the IAM portal, select 'API Keys' and click 'Create Key'. Configure the necessary settings, such as notification emails for key expiration, and then click 'Create'. You must copy the resulting key immediately, as it cannot be retrieved after closing the window. Note that existing API keys become invalid whenever the Checkmarx license is updated (e.g., adding a new scanner).

2. Add them to .dlt/secrets.toml

[sources.checkmarx_sca_source] cx_api_key = "your_api_key_here"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

uv run dlthub ai toolkit install rest-api-pipeline

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the Checkmarx SCA API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

uv run python checkmarx_sca_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline checkmarx_sca_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset checkmarx_sca_data The duckdb destination used duckdb:/checkmarx_sca.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

uv run dlthub show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads /risk-management/projects and /risk-management/scans from the Checkmarx SCA API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def checkmarx_sca_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api-sca.checkmarx.net", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "scans", "endpoint": {"path": "risk-management/scans"}}, {"name": "projects", "endpoint": {"path": "risk-management/projects"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="checkmarx_sca_pipeline", destination="duckdb", dataset_name="checkmarx_sca_data", ) load_info = pipeline.run(checkmarx_sca_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("checkmarx_sca_pipeline").dataset() sessions_df = data.scans.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM checkmarx_sca_data.scans LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("checkmarx_sca_pipeline").dataset() data.scans.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load Checkmarx SCA data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI harness:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for Checkmarx SCA?

Request dlt skills, commands, AGENT.md files, and AI-native context.