Checkmarx SCA Python API Docs | dltHub

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

Last updated:

Checkmarx SCA REST API is used for managing projects, scans, and risk, with base URLs varying by environment. The REST API base URL is https://api-sca.checkmarx.net (US Environment) or https://eu.api-sca.checkmarx.net (EU Environment) and All requests require a Bearer access token for authentication..

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 pip install "dlt[workspace]" 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/scansGETView info about all the scans of a specific Project.
projects/risk-management/projectsPOSTCreate a new Project.
package_vulnerabilities/package-vulnerabilitiesPOSTManage risk by triaging specific vulnerability results.
package_supply_chain_risks/package-supply-chain-risksPOSTManage risk by triaging specific vulnerability results.
packages/packagesPOSTManage packages by ignoring vulnerable packages.
packages_bulk/packages/bulkPOSTManage packages by ignoring vulnerable packages.

How do I authenticate with the Checkmarx SCA API?

Authentication involves submitting a username, password, and Tenant Account name to a POST token endpoint to obtain a Bearer access token. This token must then be included in the 'Authorization: Bearer ' header for subsequent requests.

1. Get your credentials

To obtain API credentials, you need to submit your username, password, and Tenant Account name to the POST token endpoint. This will return an Access Token for the current session.

2. Add them to .dlt/secrets.toml

[sources.checkmarx_sca_source] access_token = "your_access_token_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 venv && source .venv/bin/activate uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

dlt 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:

dlt ai toolkit rest-api-pipeline install

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:

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:

dlt pipeline checkmarx_sca_pipeline 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 scans and projects 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 (US Environment) or https://eu.api-sca.checkmarx.net (EU Environment)", "auth": { "type": "bearer", "access_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.


Troubleshooting

Common API Errors

  • 400 Bad Request: Indicates bad data, such as inaccessible assigned teams.
  • 401 Unauthorized: Likely due to an invalid or missing access token.
  • 409 Conflict: Occurs when attempting to create a resource that already exists, for example, a project with the same name.
  • 500 Internal Server Error: A generic server-side error.

Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.


Next steps

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

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

Was this page helpful?

Community Hub

Need more dlt context for Checkmarx SCA?

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