Load Sectigo Certificate Manager data in Python using dltHub
Build a Sectigo Certificate Manager-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Sectigo Certificate Manager (SCM) REST Enrollment API allows management of SSL, client, code signing, and device certificates without admin credentials. The REST API base URL is https://{customer}.enroll.{instance}.sectigo.com and all requests require a Bearer token generated via OAuth 2.0 client credentials flow.
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 Sectigo Certificate Manager data in under 10 minutes.
What data can I load from Sectigo Certificate Manager?
Here are some of the endpoints you can load from Sectigo Certificate Manager:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| ssl_certificates | /api/ssl/v1 | GET | List SSL certificates | |
| ssl_certificate_details | /api/ssl/v1/{sslId} | GET | Get SSL certificate details | |
| ssl_certificate_profiles | /api/ssl/v1/types | GET | List SSL certificate profiles | |
| ssl_certificate_custom_fields | /api/ssl/v1/customFields | GET | List SSL certificate custom fields | |
| ssl_certificate_location | /api/ssl/v1/{sslId}/location | GET | List SSL certificate custom locations |
How do I authenticate with the Sectigo Certificate Manager API?
All API methods require an OAuth 2.0 Bearer token provided in the Authorization header as 'Bearer '.
1. Get your credentials
To obtain API credentials, log in to the Sectigo Certificate Manager (SCM) web dashboard. Navigate to Enrollment > REST. Select the desired REST endpoint (e.g., SSL Certificates REST API) and click Accounts. In the REST Accounts dialog, click Add to create a new account, or edit an existing one. Upon creation or reset, the system will provide you with a Client ID and a Client Secret. Ensure you save these securely, as the secret is typically only displayed once.
2. Add them to .dlt/secrets.toml
[sources.sectigo_certificate_manager_source] url = "https://<your-instance>.enroll.sectigo.com/api/v1" client_id = "your_client_id_here" client_secret = "your_client_secret_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 Sectigo Certificate Manager 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 sectigo_certificate_manager_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline sectigo_certificate_manager_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset sectigo_certificate_manager_data The duckdb destination used duckdb:/sectigo_certificate_manager.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 /api/v1/ssl and /api/v1/client from the Sectigo Certificate Manager 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 sectigo_certificate_manager_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{customer}.enroll.{instance}.sectigo.com", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "ssl_certificates", "endpoint": {"path": "api/ssl/v1"}}, {"name": "ssl_certificate_profiles", "endpoint": {"path": "api/ssl/v1/types"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="sectigo_certificate_manager_pipeline", destination="duckdb", dataset_name="sectigo_certificate_manager_data", ) load_info = pipeline.run(sectigo_certificate_manager_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("sectigo_certificate_manager_pipeline").dataset() sessions_df = data.ssl_certificates.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM sectigo_certificate_manager_data.ssl_certificates LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("sectigo_certificate_manager_pipeline").dataset() data.ssl_certificates.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 Sectigo Certificate Manager data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example 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 Sectigo Certificate Manager?
Request dlt skills, commands, AGENT.md files, and AI-native context.