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 Questionnaires API

Operations related to questionnaires, questionnaire sections, and questionnaire evidence for a specific use case

Credo AI Use Case Questionnaires 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 12 operations across 8 paths, and defines 22 schemas. It is described by OpenAPI 3.2.0.

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

12 operations 8 paths 22 schemas 2 DELETE5 GET1 PATCH4 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 Questionnaires API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Bearer).

Paths & Operations 12

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

use_case_questionnaires 12

Operations related to questionnaires, questionnaire sections, and questionnaire evidence for a specific use case

GET
/use_cases/{use_case_id}/questionnaire_sections/{section_id}/files
Retrieves a list of all supplementary files associated with a specific questionnaire section for a given use case.
CredoAIWeb.API.V2.UseCase.Questionnaire.SectionFileController.index 2 params → 200401
POST
/use_cases/{use_case_id}/questionnaire_sections/{section_id}/files
Creates a new file associated with a specific questionnaire section for a given use case.
CredoAIWeb.API.V2.UseCase.Questionnaire.SectionFileController.create 2 params body → 201401403
GET
/use_cases/{use_case_id}/questionnaires
List all usecasequestionnaires of usecase
CredoAIWeb.API.V2.UseCase.QuestionnaireController.index 1 param → 200401404
POST
/use_cases/{use_case_id}/questionnaires
Add questionnaire to use case, as a result creates usecasequestionnaires and usecasequestionnairesections
CredoAIWeb.API.V2.UseCase.QuestionnaireController.create 1 param body → 201401403404
GET
/use_cases/{use_case_id}/questionnaire_sections
Retrieves a list of all questionnaire sections associated with a specific use case.
CredoAIWeb.API.V2.UseCase.Questionnaire.SectionController.index 1 param → 200401
DELETE
/use_cases/{use_case_id}/questionnaire_sections/{section_id}/files/{id}
Deletes a specific file from a questionnaire section for a given use case.
CredoAIWeb.API.V2.UseCase.Questionnaire.SectionFileController.delete 3 params → 204401403404
POST
/use_cases/{use_case_id}/questionnaire_sections/{section_id}/tasks
Creates a new task associated with a specific questionnaire section of a use case.
CredoAIWeb.API.V2.UseCase.Questionnaire.SectionController.create_task 2 params body → 201401403
GET
/use_cases/{use_case_id}/questionnaire_sections/{section_id}/evidences
Retrieves a list of evidences associated with a specific use case questionnaire section.
CredoAIWeb.API.V2.UseCase.Questionnaire.SectionEvidenceController.index 2 params → 200401
POST
/use_cases/{use_case_id}/questionnaire_sections/{section_id}/evidences
Creates a new evidence entry for a specific question within a questionnaire section of a use case.
CredoAIWeb.API.V2.UseCase.Questionnaire.SectionEvidenceController.create 2 params body → 200401404
GET
/use_cases/{use_case_id}/questionnaire_sections/{id}
Fetches a specific questionnaire section for a given use case by its unique ID.
CredoAIWeb.API.V2.UseCase.Questionnaire.SectionController.show 2 params → 200401404
DELETE
/use_cases/{use_case_id}/questionnaires/{id}
Remove queationnaire from use case, as a result deletes usecasequestionnaires and usecasequestionnairesections
CredoAIWeb.API.V2.UseCase.QuestionnaireController.delete 2 params → 204401403404
PATCH
/use_cases/{use_case_id}/questionnaires/{id}
Update usecasequestionnaires. If version is provided, it will upgrade questinnaire to that version and other attributes will be ignored. If duedate is provided, it will update duedate of usecasequest…
CredoAIWeb.API.V2.UseCase.QuestionnaireController.update 2 params body → 200401403404

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are UseCaseQuestionnaireSectionResource (4 properties), SectionFileResource (4 properties), UseCaseQuestionnaireResource (4 properties), TaskResource (4 properties). Each schema is shown below with its type and property counts.

UseCaseQuestionnaireSectionEvidenceCreateRequest
object
1 property
TaskResponse
object
A JSON-API document with a single [TaskResource](taskresource) resource
2 properties 1 required
SectionFileResponse
object
A JSON-API document with a single [SectionFileResource](sectionfileresource) resource
2 properties 1 required
TaskResource
object
4 properties
UseCaseQuestionnaireSectionResponse
object
A JSON-API document with a single [UseCaseQuestionnaireSectionResource](usecasequestionnairesectionresource) resource
2 properties 1 required
EvidenceResponse
object
A JSON-API document with a single [EvidenceResource](evidenceresource) resource
2 properties 1 required
EvidencesResponse
object
A collection of [EvidenceResource](evidenceresource)
1 property 1 required
UseCaseControlTaskCreateRequest
object
1 property
UseCaseQuestionnaireCreateRequest
object
1 property
SectionFileCreateRequest
object
1 property
EvidenceResource
object
4 properties
UseCaseQuestionnaireSectionsResponse
object
A collection of [UseCaseQuestionnaireSectionResource](usecasequestionnairesectionresource)
1 property 1 required
UseCaseQuestionnairesResponse
object
A collection of [UseCaseQuestionnaireResource](usecasequestionnaireresource)
1 property 1 required
UseCaseQuestionnaireResponse
object
A JSON-API document with a single [UseCaseQuestionnaireResource](usecasequestionnaireresource) resource
2 properties 1 required
ForbiddenError
object
1 property
AuthError
object
1 property
UseCaseQuestionnaireSectionResource
object
4 properties
UseCaseQuestionnaireResource
object
4 properties
SectionFileResource
object
4 properties
SectionFilesResponse
object
A page of [SectionFileResponse](sectionfileresponse) results
2 properties 1 required
NotFoundError
object
1 property
UseCaseQuestionnaireUpdateRequest
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

credo-ai-use-case-questionnaires-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 Questionnaires 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.