Python client library for the CertiNext certificate management API
Project description
certinext
Python library and CLI scripts for managing your CertiNext environment via the REST API.
Work in progress:
list,get,get_dcv,verify, andchange_dcv_methodhave been tested against the live API.create,deactivate,last_dcv_attempt, anddcv_attempt_historyare implemented based on the API documentation but remain untested against the live API.
Contents
Requirements
- Python 3.10+
- A CertiNext account with OAuth API credentials (account number + client secret)
Installation
From the package registry
pip install certinext \
--extra-index-url https://gitlab.its.maine.edu/api/v4/groups/2236/-/packages/pypi/simple
Or with uv:
uv add certinext --index https://gitlab.its.maine.edu/api/v4/groups/2236/-/packages/pypi/simple
Development install
Clone the repository, then install in editable mode:
uv venv
.venv\Scripts\activate # Windows
# source .venv/bin/activate # macOS / Linux
uv pip install -e .
This installs the certinext package and its dependencies (requests, tabulate, python-dotenv).
Credentials
You need two values from the CertiNext portal (Integrations → APIs → OAuth mode):
| Value | Description |
|---|---|
| Account number | Your CertiNext account number (used as the OAuth client_id) |
| Client secret | The OAuth access key generated in the portal |
The token endpoint defaults to https://us-api.certinext.io/oauth/token. Override with --token-url if yours differs.
Storing credentials in the OS keychain (recommended)
Run the setup script once to store your credentials securely in the system keychain (Windows Credential Manager on Windows, Keychain on macOS, libsecret/SecretService on Linux):
uv pip install -e .[keyring]
uv run scripts/certinext_setup_keyring.py
Scripts read credentials from the keychain automatically — no CLI flags or environment variables needed for day-to-day use.
Named profiles and credential resolution order
Named profiles
Use --profile NAME to store multiple credential sets (e.g. different
accounts or environments):
uv run scripts/certinext_setup_keyring.py --profile prod
Select a profile at runtime with --profile or the CERTINEXT_PROFILE
environment variable:
python scripts/domains.py --profile prod list
CERTINEXT_PROFILE=prod python scripts/pending_dcv.py
Credential resolution order
All scripts resolve credentials in this priority order:
- Explicit CLI argument (
--account-number,--client-secret) - OS keychain (active profile; see above)
- Environment variables (
CERTINEXT_CLIENT_ID,CERTINEXT_CLIENT_SECRET) - Interactive prompt (falls back to
getpassfor secrets)
Scripts
certinext_setup_keyring
scripts/certinext_setup_keyring.py stores CertiNext API credentials in the
OS keychain interactively. Run it once before using the other scripts.
# Store credentials for the default profile
uv run scripts/certinext_setup_keyring.py
# Store credentials for a named profile
uv run scripts/certinext_setup_keyring.py --profile prod
The script prompts for your account number and client secret, shows any currently stored value as a default so you can keep it by pressing Enter, and masks the secret with asterisks on confirmation.
domains
scripts/domains.py is a command-line interface for the domains API.
Common arguments
These appear before the subcommand. Credentials are optional when stored in the keychain (see Credentials above).
--profile NAME Credential profile for keyring lookup (env: CERTINEXT_PROFILE)
--account-number ACCT CertiNext account number / client_id (env: CERTINEXT_CLIENT_ID)
--client-secret SECRET OAuth2 client secret (env: CERTINEXT_CLIENT_SECRET)
--base-url URL API base URL (default: https://us-api.certinext.io)
--token-url URL Token endpoint URL (default: https://us-api.certinext.io/oauth/token)
--scope SCOPE OAuth2 scope (optional)
--json Output raw JSON instead of tabular format
Subcommands
list
List all domains.
# credentials from keychain
python scripts/domains.py list
python scripts/domains.py list --offset 50 --limit 25
# credentials explicit
python scripts/domains.py --account-number ACCT --client-secret SECRET list
get
Get a single domain by name or ID.
python scripts/domains.py get maine.edu
python scripts/domains.py get vuxwZgEXWWFXQQWC-...
create
Create a new domain. Additional API fields can be passed as KEY=VALUE pairs.
python scripts/domains.py create newdomain.example.com
deactivate
Deactivate a domain by ID. Prompts for confirmation unless -y is passed.
python scripts/domains.py deactivate DOMAIN_ID
python scripts/domains.py deactivate DOMAIN_ID -y
get-dcv
Show current DCV status for a domain.
python scripts/domains.py get-dcv DOMAIN_ID
verify-dcv
Trigger DCV verification for a domain.
python scripts/domains.py verify-dcv DOMAIN_ID
change-dcv-method
Change the DCV method for a domain. Accepted values: DNS-TXT, HTTP-URL.
python scripts/domains.py change-dcv-method DOMAIN_ID DNS-TXT
last-dcv-attempt
Show the most recent DCV attempt for a domain.
python scripts/domains.py last-dcv-attempt DOMAIN_ID
dcv-attempt-history
Show the full DCV attempt history for a domain.
python scripts/domains.py dcv-attempt-history DOMAIN_ID
JSON output
Add --json before the subcommand to get raw JSON instead of the default tabular output. Useful for piping into jq:
python scripts/domains.py --json list | jq '.[] | .domainName'
pending_dcv
scripts/pending_dcv.py lists every active domain that has not yet completed
DCV verification. It is a quick read-only diagnostic — no changes are made to
any domain.
Arguments
--profile NAME Credential profile for keyring lookup (env: CERTINEXT_PROFILE)
--account-number ACCT CertiNext account number (env: CERTINEXT_CLIENT_ID)
--client-secret SECRET OAuth2 client secret (env: CERTINEXT_CLIENT_SECRET)
--base-url URL API base URL (default: https://us-api.certinext.io)
--token-url URL Token endpoint URL (default: https://us-api.certinext.io/oauth/token)
--pattern REGEX Filter by domain name regex (re.fullmatch, case-insensitive)
--json Output raw JSON instead of tabular format
Examples
# Credentials from keychain (no flags needed after setup)
python scripts/pending_dcv.py
# Use a named profile
python scripts/pending_dcv.py --profile prod
# Filter to a specific subdomain pattern
python scripts/pending_dcv.py --pattern ".*\.maine\.edu"
# Raw JSON output for scripting
python scripts/pending_dcv.py --json | jq '.[] | .domainName'
# Credentials from environment variables
CERTINEXT_CLIENT_ID=ACCT CERTINEXT_CLIENT_SECRET=SECRET python scripts/pending_dcv.py
Python library
Creating a session
import certinext
sess = certinext.session(
client_id="YOUR_ACCOUNT_NUMBER",
client_secret="YOUR_CLIENT_SECRET",
)
All session() parameters
sess = certinext.session(
base_url="https://us-api.certinext.io",
token_url="https://us-api.certinext.io/oauth/token",
client_id="YOUR_ACCOUNT_NUMBER",
client_secret="YOUR_CLIENT_SECRET",
scope="", # optional
)
The session obtains and caches an OAuth 2.0 bearer token automatically, refreshing it before it expires.
Working with domains
List all domains
domains = sess.domain.get_list()
for d in domains:
print(d)
Paginate with offset and limit:
page = sess.domain.get_list(offset=50, limit=25)
Filter by status server-side (reduces data transferred):
# Only active domains with pending or rejected DCV
domains = sess.domain.get_list(domain_status="ACTIVE", dcv_status="PENDING,REJECTED,EXPIRED")
Note: The API
searchparameter is a confirmed vendor bug (reported 2026-05-20) — all domains are returned regardless of the value passed. Usepattern(below) for reliable filtering until CertiNext notifies the fix is deployed.
Filter by name with a regex (applied client-side after the API response):
# Exact match
domains = sess.domain.get_list(pattern=r"maine\.edu")
# Multiple names via alternation
domains = sess.domain.get_list(pattern=r"maine\.edu|umaine\.edu")
# Subdomain wildcard
domains = sess.domain.get_list(pattern=r".*\.maine\.edu")
pattern uses re.fullmatch with re.IGNORECASE, so it must match the entire
domain name. Combine with status filters to narrow the API response first:
domains = sess.domain.get_list(domain_status="ACTIVE", pattern=r".*\.maine\.edu")
List domains needing DCV
list_pending_dcv() returns active domains that have not yet completed DCV
verification. It fetches all domains and filters client-side using
domain.needs_dcv.
Note: The API
domainStatusanddcvStatusfilter parameters return a 400 error when used together — confirmed vendor bug (reported 2026-05-20). Server-side status filtering is disabled until CertiNext notifies the fix is deployed.
pending = sess.domain.list_pending_dcv()
# Narrow to a subset by name
pending = sess.domain.list_pending_dcv(pattern=r".*\.maine\.edu")
Get a domain
Look up by domain name or by domain ID:
domain = sess.domain.get("maine.edu")
domain = sess.domain.get("vuxwZgEXWWFXQQWC-3zElI5VlhinKlE8xyYJqfeYNtFE0SAP")
When a name is passed (contains a .), the library lists all domains and finds the match. When an ID is passed, it calls the single-domain endpoint directly.
Create a domain
domain = sess.domain.create("newdomain.example.com")
Domain properties and DcvInfo fields
Domain properties
| Property | Type | Description |
|---|---|---|
id |
str | None |
Domain ID |
name |
str | None |
Domain name (FQDN). Settable, but only updates the local object — does not persist to the API. |
status |
str | None |
ACTIVE or INACTIVE |
dcv_status |
str | None |
VERIFIED, PENDING, REJECTED, EXPIRED, etc. |
organization_id |
str | None |
Organization ID |
organization_name |
str | None |
Organization display name |
created_at |
datetime | None |
Creation timestamp (timezone-aware UTC) |
needs_dcv |
bool |
True if status is ACTIVE and dcv_status is not VERIFIED |
Domain objects support str() and repr():
print(domain)
# Domain: maine.edu
# id: vuxwZgEXWWFXQQWC-...
# status: ACTIVE
# dcv_status: VERIFIED
# organization: University of Maine System
# created: 2026-05-04 21:27:14+00:00
repr(domain)
# Domain(id='vuxwZgEXWWFXQQWC-...', name='maine.edu', status='ACTIVE', dcv_status='VERIFIED')
DcvInfo
domain.get_dcv() returns a DcvInfo dataclass with the following fields:
| Field | Type | Description |
|---|---|---|
method |
str |
DCV method in upper case: DNS-TXT or HTTP-URL |
token |
str |
Challenge value to publish (TXT record content for DNS-TXT, file token for HTTP-URL) |
host |
str |
Sub-domain prefix for the challenge record (e.g. _emudhra-challenge). Empty string if not returned by the API. |
Domain methods
# Re-fetch from API and update the object in place
domain.refresh()
# Deactivate (updates the object in place, returns self)
domain.deactivate()
# DCV — Domain Control Validation
dcv = domain.get_dcv() # returns DcvInfo(method, token, host)
print(dcv.method) # e.g. "DNS-TXT" or "HTTP-URL"
print(dcv.token) # challenge value to publish
print(dcv.host) # sub-domain prefix for the challenge record
result = domain.verify() # trigger verification; returns raw API response dict
domain.change_dcv_method("DNS-TXT") # accepted values: "DNS-TXT", "HTTP-URL"
attempt = domain.last_dcv_attempt() # returns raw API response dict
history = domain.dcv_attempt_history() # returns raw API response dict or list
# Get the raw API response dict
raw = domain.as_dict()
Example: verify all pending domains
import certinext
sess = certinext.session(
client_id="YOUR_ACCOUNT_NUMBER",
client_secret="YOUR_CLIENT_SECRET",
)
# Due to a vendor API bug, server-side status filtering is currently disabled.
# list_pending_dcv() fetches all domains and filters client-side for needs_dcv.
for domain in sess.domain.list_pending_dcv():
print(f"Verifying {domain.name} ...")
domain.verify()
Or check needs_dcv manually if you already have a full domain list:
for domain in sess.domain.get_list():
if domain.needs_dcv:
print(f"Verifying {domain.name} ...")
domain.verify()
Project structure
File tree
certinext/
__init__.py # session() factory, top-level exports
_keyring.py # shared keyring helpers (keyring_service, keyring_get)
auth.py # OAuth 2.0 client credentials token management
client.py # HTTP session wrapper (get/post/put/delete)
domains.py # Domain class and DomainAccessor
session.py # CertiNextSession (session.domain accessor)
scripts/
certinext_setup_keyring.py # store API credentials in the OS keychain
domains.py # CLI for domain management
pending_dcv.py # list all domains with pending DCV verification
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file certinext-0.1.2a2.tar.gz.
File metadata
- Download URL: certinext-0.1.2a2.tar.gz
- Upload date:
- Size: 34.2 kB
- Tags: Source
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.13.12
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
8118a816a2633ba6b1db1cf3771d23bce7aca460ec63a2df740653321b0d3707
|
|
| MD5 |
3a9040f55a0313c3d0728bbc9bbaa8bd
|
|
| BLAKE2b-256 |
e42235b2ca6b84e699d640da5a5f817c121860c045f914e4c51d34e9f4fc00c0
|
Provenance
The following attestation bundles were made for certinext-0.1.2a2.tar.gz:
Publisher:
ci.yml on tod-uma/certinext
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
certinext-0.1.2a2.tar.gz -
Subject digest:
8118a816a2633ba6b1db1cf3771d23bce7aca460ec63a2df740653321b0d3707 - Sigstore transparency entry: 1607753093
- Sigstore integration time:
-
Permalink:
tod-uma/certinext@8cb05c353c37cdf924a7ba52447c83a36a7d81a5 -
Branch / Tag:
refs/tags/v0.1.2a2 - Owner: https://github.com/tod-uma
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
ci.yml@8cb05c353c37cdf924a7ba52447c83a36a7d81a5 -
Trigger Event:
push
-
Statement type:
File details
Details for the file certinext-0.1.2a2-py3-none-any.whl.
File metadata
- Download URL: certinext-0.1.2a2-py3-none-any.whl
- Upload date:
- Size: 23.0 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.13.12
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
756a49dc82c96ccf8a8b8d64ee740b1b022b99e8eba0adc867c5b9b9f02aa165
|
|
| MD5 |
074c579ddfaa22b0e48c95b3a778f52c
|
|
| BLAKE2b-256 |
34ea834b237641159d93326b9c534d65aeb9b5c307c23b40e8f10e3b6797107b
|
Provenance
The following attestation bundles were made for certinext-0.1.2a2-py3-none-any.whl:
Publisher:
ci.yml on tod-uma/certinext
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
certinext-0.1.2a2-py3-none-any.whl -
Subject digest:
756a49dc82c96ccf8a8b8d64ee740b1b022b99e8eba0adc867c5b9b9f02aa165 - Sigstore transparency entry: 1607753180
- Sigstore integration time:
-
Permalink:
tod-uma/certinext@8cb05c353c37cdf924a7ba52447c83a36a7d81a5 -
Branch / Tag:
refs/tags/v0.1.2a2 - Owner: https://github.com/tod-uma
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
ci.yml@8cb05c353c37cdf924a7ba52447c83a36a7d81a5 -
Trigger Event:
push
-
Statement type: