X-DC-DEVKEY; DigiCert ONE APIs use a separate service-user token in x-api-key; Content Trust operations that document OAuth2 also accept authType: 'oauth_2' with the service scope. Public TLM version and CSC info operations need no key. Webhook operations are out of scope, five deprecated TLM routes are excluded, and 14 CertCentral Discovery catalog operations were discontinued on October 1, 2026. DigiCert ONE also offers mTLS, which this plugin does not implement. See route-inventory.md for per-family counts, exclusions, and sources.
What you get:
- 663 typed API operations
Setup
1
Install
2
Add the plugin
corsair.ts
multiTenancy: true, scope calls with corsair.withTenant(id). See Quick start for KEK + Hub keys, and Multi-tenancy for account isolation.3
Choose authentication
- API Key (Recommended)
- OAuth 2.0
Store the DigiCert API key before the first call: More: API Key
pnpm corsair setup --plugin=digicert --tenant=acme api_key=<your-key> (leave out --tenant without multiTenancy), or pass it as key in the plugin options. With Hub, each tenant enters their own key on the connect page. See API key auth.4
Connect a tenant
Mint a connect link and send the tenant to it. Hub hosts the page and delivers the result to your app — see Connect / OAuth.
Example API calls
List Account Manager localesWhat’s next
API reference
Every
digicert.api.* operation with input and output types.Connect / OAuth
createLink, Hub delivery, and tenant connect flows.
Use with agents
Expose this plugin’s operations as MCP tools.