Learn / Reference

Reference · CERTSKOPE 0.6.15

API conventions and safe automation

Use the application's authenticated endpoints with scoped permissions.

Updated 17 November 2026 ·

Session and CSRF

Browser/API operations use an authenticated session. Read /api/session for the CSRF token, then provide X-CSRF-TOKEN on state-changing requests. Re-read session state after login. Do not embed passwords or tokens in scripts committed to source control.

Useful read endpoints

GET /api/config exposes the running version. GET /api/certificates and /api/requests are scoped to your permissions and ownership. GET /api/authorities returns permitted choices. Administrator endpoints include /api/ca-policies and /api/settings/smtp.

Interpreting responses

400 indicates invalid input, 401 requires authentication, 403 indicates insufficient permission, 404 can intentionally conceal another user's record, 409 requires refreshing changed state, and 429 requires respecting the rate limit. Do not automatically retry external actions such as test email or CA submission without checking their outcome.

Contract maturity

This is an endpoint orientation, not a complete stable public API contract or generated OpenAPI specification. Confirm the installed release's request models before automation. The source includes focused regression tests and release notes for implemented behavior.

Continue exploring

Was this guide helpful?

This guide describes CertSkope 0.6.15. A saved integration profile alone does not activate an external connector. See feature availability.