Before you start
- An
adminuser to create the connector. - Model snapshots reachable over HTTPS through a short-lived, read-only link, for example a blob storage SAS URL.
- The registry able to send an HTTPS POST when a version is promoted.
Create the connector
- In the console, open Connectors, choose API / webhook and select Connect.
- Name it, pick the AI system, the environment (for example
cloud), the modeprocessand the region. - In Allowed artifact hosts, list the hosts CertOne may fetch from, such as
models.example.comor*.blob.core.windows.net. Up to 16 hosts; no IP addresses. - Create it, then copy the Webhook URL and the Webhook secret. The secret is shown once.
Send the promotion event
Post this event when a version is promoted. Authenticate with the secret in the x-certone-secret header; the delivery id makes retries safe.
POST /v1/connectors/<connector-id>/events
content-type: application/json
x-certone-secret: <webhook secret>
x-certone-delivery: <unique delivery id>
{"id": "<unique delivery id>", "eventType": "model.promoted", "version": "v3",
"artifact_url": "https://<allowed host>/releases/hydro-turbine-health/v3.tar.gz?<read-only token>"}CertOne answers right away with the scan it queued:
HTTP 202
{"status": "accepted", "run_id": "...", "event_type": "model.promoted", "scan_id": "..."}Example scripts
The reference scripts snapshot a project to Azure Blob storage, mint a read-only link valid 15 minutes, send the event and follow the scan to its verdict.
pip install --quiet requests azure-storage-blob
export AZURE_STORAGE_CONNECTION_STRING=... # the registry's storage account
export CERTONE_WEBHOOK_SECRET=... # shown once when the connector was created
export CERTONE_API_KEY=ck_... # only for --follow (a viewer key is enough)
ARTIFACT_URL=$(python release.py hydro-turbine-health v3)
python promote_model.py \
--connector-url "https://platform.certkor.ai/v1/connectors/<connector-id>/events" \
--artifact-url "$ARTIFACT_URL" --version v3 --followpromote_model.py prints the accepted run and scan, then verdict: PASS or verdict: FAIL with the counts. It exits 0 on a pass, 1 on a fail and 2 when a variable is missing.
Fetch rules
- HTTPS only, no credentials in the URL, no redirects, and a size limit.
- Only hosts on the connector's allow list, resolving to public addresses.
- Each scan is recorded with the connector name and the version, for example
connector:Model registry@v3. - Optional body fields:
tee(amd_sev_snporkata_cc) andfail_on.
| Response | Meaning |
|---|---|
| 202 | Accepted; the scan is queued. |
| 401 | The secret does not match. |
| 403 | The connector is disabled. |
| 422 | artifact_url is missing or the fetch was refused. Nothing is recorded, so you can retry. |
| 429 | Too many requests. |