How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Sigstore CA API

The CA API from Sigstore — 3 operation(s) for ca.

Sigstore CA API is one of 6 APIs that Sigstore publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include CA. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a GitHub repository.

This API exposes 3 operations across 3 paths, and defines 14 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against a single base URL, http://fulcio.sigstore.dev.

3 operations 3 paths 14 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://rekor.sigstore.dev
Resource Areas
1

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

CA 3
GET
/api/v2/configuration
Returns the configuration of supported OIDC issuers, including the required challenge for each issuer.
CA_GetConfiguration → 200default
POST
/api/v2/signingCert
Returns an X.509 certificate created by the Fulcio certificate authority for the given request parameters
CA_CreateSigningCertificate body → 200default
GET
/api/v2/trustBundle
Returns the bundle of certificates that can be used to validate code signing certificates issued by this Fulcio instance
CA_GetTrustBundle → 200default

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are v2OIDCIssuer (8 properties), fulciov2CreateSigningCertificateRequest (3 properties), rpcStatus (3 properties), fulciov2PublicKey (2 properties). Each schema is shown below with its type and property counts.

v2Credentials
object
1 property
v2SigningCertificateDetachedSCT
object
2 properties
v2OIDCIssuer
object
Metadata about an OIDC issuer.
8 properties
v2PublicKeyRequest
object
2 properties 2 required
fulciov2PublicKey
object
2 properties 1 required
protobufAny
object
Any contains an arbitrary serialized protocol buffer message along with a URL that describes the type of the serialized message. Protobuf library provides supp…
1 property
fulciov2CreateSigningCertificateRequest
object
3 properties 3 required
v2SigningCertificate
object
2 properties
v2CertificateChain
object
1 property
v2SigningCertificateEmbeddedSCT
object
1 property
v2PublicKeyAlgorithm
string
rpcStatus
object
3 properties
v2Configuration
object
The configuration for the Fulcio instance.
1 property
v2TrustBundle
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

sigstore-ca-api-openapi.yml Raw ↑

Other APIs Sigstore publishes across the network.

Sigstore entries API
Sigstore index API
Sigstore pubkey API
Sigstore tlog API
Where this information came from

This is an independent, third-party profile of Sigstore CA API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.