Microsoft Azure

Azure Confidentialledger: Cts

Azure Confidentialledger: Cts endpoints from Microsoft Azure

Developer tools#openapi

Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.

Overview

Azure Confidentialledger: Cts endpoints from Microsoft Azure

Endpoints 8

  • GETListScittKeys/.well-known/scitt-keys?api-version=stringList all service keys in COSE_Key_Set format, per Section 2.1 of draft-ietf-scitt-scrapi-09
  • GETGetScittKey/.well-known/scitt-keys/:kid?api-version=stringGet a single service key by kid, per Section 2.2 of draft-ietf-scitt-scrapi-09
  • GETGetTransparencyConfigCbor/.well-known/transparency-configuration?api-version=stringGet the transparency service configuration, mandatory in IETF SCITT draft
  • POSTCreateEntry/entries?api-version=string&waitForCommit=truePost an entry to be registered on the CodeTransparency instance, mandatory in IETF SCITT draft
  • GETGetEntry/entries/:entryId?api-version=stringGet receipt
  • GETGetEntryStatement/entries/:entryId/statement?api-version=stringGet the transparent statement consisting of the signed statement and the receipt embedded in the header
  • GETGetPublicKeys/jwks?api-version=stringGet the public keys used by the service to sign receipts, mentioned in IETF SCITT draft as part of jwks_uri implementation
  • GETGetOperation/operations/:operationId?api-version=stringDeprecated. Get status of the long running registration operation. Deprecated in SCRAPI v09 but retained unchanged for backward compatibility; clients should…

API details

Authentication
None declared in the description
Operations
8 operations on 8 pathsGET 7POST 1
1 marked deprecated
Response formats
application/json
Description format
Swagger 2.0, API version 2026-03-26

How to test the Azure Confidentialledger: Cts in Swastik Codes

  1. Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
  2. Fork it into your workspaceChoose a workspace. You get your own copy of the Azure Confidentialledger: Cts collection, without the publisher's secrets.
  3. Add your credentialsOpen the collection's variables or an environment and enter your API key or token, if the API needs one.
  4. Send a requestPick an endpoint, for example “ListScittKeys” (GET /.well-known/scitt-keys?api-version=string), and press Send. Check the response, add tests and run the whole collection with the runner.

Frequently asked questions

What is the Azure Confidentialledger: Cts?

Azure Confidentialledger: Cts endpoints from Microsoft Azure It is listed under Developer tools and has 8 endpoints.

Who publishes the Azure Confidentialledger: Cts?

It is listed from Microsoft Azure's public API description (an OpenAPI document), not published by Microsoft Azure on Swastik Codes. Anyone who controls azure.com can claim the profile by adding a DNS TXT record.

How do I authenticate with the Azure Confidentialledger: Cts?

Its OpenAPI description does not declare an authentication scheme. Some endpoints may be open; check the provider's documentation before relying on that.

How many endpoints does the Azure Confidentialledger: Cts have?

8 operations on 8 paths (7 GET, 1 POST).

Is forking the Azure Confidentialledger: Cts free?

Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.

Suggest an API

Tell us which public API is missing. We check it, then add it here with its endpoints when it has an OpenAPI (Swagger) description.