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

Credo AI Use Case Reports API

Operations related to reports for a specific use case, including creation, retrieval, and management of attestation requests

Credo AI Use Case Reports API is one of 40 APIs that Credo AI publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and authentication docs.

This API exposes 8 operations across 5 paths, and defines 13 schemas. It is described by OpenAPI 3.2.0.

Requests are made against a single base URL, /api/v2/credoai.

8 operations 5 paths 13 schemas 2 DELETE3 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
Base URL
https://api.credo.ai/api/v2/{tenant}
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Credo AI Use Case Reports API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Bearer).

Paths & Operations 8

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

use_case_reports 8

Operations related to reports for a specific use case, including creation, retrieval, and management of attestation requests

DELETE
/use_cases/{use_case_id}/reports/{report_id}/attestation_requests/{id}
Cancel a specific attestation request associated with a report and use case.
CredoAIWeb.API.V2.UseCase.Report.AttestationRequestController.delete 3 params → 204401403404
DELETE
/use_cases/{use_case_id}/reports/{id}
Delete a report and its associated widgets.
CredoAIWeb.API.V2.UseCase.ReportController.delete 2 params → 204401403404
GET
/use_cases/{use_case_id}/reports/{id}
Fetch detailed information about a specific report with widget data.
CredoAIWeb.API.V2.UseCase.ReportController.show 2 params → 200401404
PATCH
/use_cases/{use_case_id}/reports/{id}
Update report metadata (name, description). Structure cannot be changed after creation.
CredoAIWeb.API.V2.UseCase.ReportController.update 2 params body → 200401403404
POST
/use_cases/{use_case_id}/reports/{report_id}/attestation_requests
Create a new attestation request for a specific report associated with a use case.
CredoAIWeb.API.V2.UseCase.Report.AttestationRequestController.create 2 params body → 201401403
GET
/use_cases/{use_case_id}/reports/{report_id}/snapshot
Retrieve the snapshot data for a specific report associated with a use case.
CredoAIWeb.API.V2.UseCase.ReportController.show_snapshot 2 params → 200401404
GET
/use_cases/{use_case_id}/reports
Retrieve a list of reports associated with a specific use case.
CredoAIWeb.API.V2.UseCase.ReportController.index 5 params → 200401
POST
/use_cases/{use_case_id}/reports
Create a new report. Use templateid for template-based reports or policypackkey for legacy reports.
CredoAIWeb.API.V2.UseCase.ReportController.create 1 param body → 201401403

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are UseCaseSnapshotResource (4 properties), ReportResource (4 properties), ReportAttestationRequestResource (4 properties), ReportResponse (2 properties). Each schema is shown below with its type and property counts.

UseCaseSnapshotResource
object
4 properties
ReportAttestationRequestCreateRequest
object
1 property
ReportResource
object
4 properties
ReportAttestationRequestResource
object
4 properties
ReportsResponse
object
A collection of [ReportResource](reportresource)
1 property 1 required
AuthError
object
1 property
ReportAttestationRequestResponse
object
A JSON-API document with a single [ReportAttestationRequestResource](reportattestationrequestresource) resource
2 properties 1 required
UseCaseSnapshotResponse
object
A JSON-API document with a single [UseCaseSnapshotResource](usecasesnapshotresource) resource
2 properties 1 required
ReportCreateRequest
object
1 property
ForbiddenError
object
1 property
ReportUpdateRequest
object
1 property
ReportResponse
object
A JSON-API document with a single [ReportResource](reportresource) resource
2 properties 1 required
NotFoundError
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

credo-ai-use-case-reports-api-openapi.yml Raw ↑

Other APIs Credo AI publishes across the network.

Credo AI Governance Intelligence Pro MCP Server
Credo AI Alerts API
Credo AI Audit Logs API
Credo AI Comment Threads API
Credo AI Entities API
Credo AI Entity Control Assignments API
Credo AI Entity Controls API
Credo AI Entity Evidences API
Credo AI Entity Policy Packs API
Credo AI Entity Risk Scenario Controls API
Credo AI Entity Risk Scenarios API
Credo AI Entity Section Assignments API
Where this information came from

This is an independent, third-party profile of Credo AI Use Case Reports 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.