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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Credo AI

Credo AI Triggers And Actions API

Endpoints for managing triggers and actions

Documentation Provider Profile APIs.io OpenAPI GitHub

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

Tagged areas include Triggers and Actions. 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 6 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0.

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

12 operations 6 paths 12 schemas 2 DELETE6 GET2 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 Triggers And Actions API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Bearer).

Paths & Operations 12

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

triggers_and_actions 12

Endpoints for managing triggers and actions

GET
/triggers/{id}/affected_use_cases
Returns the count and IDs of use cases affected by this trigger.
CredoAIWeb.API.V2.TriggerController.affected_use_cases 1 param → 200401
GET
/trigger_actions/{id}/affected_use_cases
Returns the count and IDs of use cases affected by this action.
CredoAIWeb.API.V2.TriggerActionController.affected_use_cases 1 param → 200401
DELETE
/triggers/{id}
Delete a trigger identified by its ID.
CredoAIWeb.API.V2.TriggerController.delete 2 params → 200401404
GET
/triggers/{id}
Fetch details of a specific trigger by its ID.
CredoAIWeb.API.V2.TriggerController.show 1 param → 200401404
PATCH
/triggers/{id}
Update an existing trigger identified by its ID.
CredoAIWeb.API.V2.TriggerController.update 1 param body → 200401404
GET
/triggers
Retrieve a list of all available triggers.
CredoAIWeb.API.V2.TriggerController.index → 200401
POST
/triggers
Create a new trigger with the specified attributes.
CredoAIWeb.API.V2.TriggerController.create body → 201401
DELETE
/trigger_actions/{id}
Delete an action identified by its ID from the system.
CredoAIWeb.API.V2.TriggerActionController.delete 2 params → 204401404
GET
/trigger_actions/{id}
Fetch details of a specific action by its ID.
CredoAIWeb.API.V2.TriggerActionController.show 1 param → 200401404
PATCH
/trigger_actions/{id}
Update an existing action identified by its ID.
CredoAIWeb.API.V2.TriggerActionController.update 1 param body → 200401404
GET
/trigger_actions
Retrieve a list of all actions that can be triggered.
CredoAIWeb.API.V2.TriggerActionController.index → 200401
POST
/trigger_actions
Create a new action with the provided attributes.
CredoAIWeb.API.V2.TriggerActionController.create body → 201401

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are TriggerResource (4 properties), ActionResource (4 properties), TriggerResponse (2 properties), ActionResponse (2 properties). Each schema is shown below with its type and property counts.

TriggerUpdateRequest
object
1 property
ActionResource
object
4 properties
TriggerResource
object
4 properties
ActionsResponse
object
A page of [ActionResource](actionresource) results
2 properties 1 required
AuthError
object
1 property
ActionCreateRequest
object
1 property
TriggersResponse
object
A page of [TriggerResource](triggerresource) results
2 properties 1 required
ActionResponse
object
A JSON-API document with a single [ActionResource](actionresource) resource
2 properties 1 required
TriggerResponse
object
A JSON-API document with a single [TriggerResource](triggerresource) resource
2 properties 1 required
TriggerCreateRequest
object
1 property
ActionUpdateRequest
object
1 property
NotFoundError
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

credo-ai-triggers-and-actions-api-openapi.yml Raw ↑

Other APIs Credo AI publishes across the network.

Credo AI Governance Intelligence Pro MCP Server
AE Profile APIs.io
Credo AI Alerts API
AE Profile APIs.io
Credo AI Audit Logs API
AE Profile APIs.io
Credo AI Comment Threads API
AE Profile APIs.io
Credo AI Entities API
AE Profile APIs.io
Credo AI Entity Control Assignments API
AE Profile APIs.io
Credo AI Entity Controls API
AE Profile APIs.io
Credo AI Entity Evidences API
AE Profile APIs.io
Credo AI Entity Policy Packs API
AE Profile APIs.io
Credo AI Entity Risk Scenario Controls API
AE Profile APIs.io
Credo AI Entity Risk Scenarios API
AE Profile APIs.io
Credo AI Entity Section Assignments API
AE Profile APIs.io
#Triggers and Actions
← Back to C APIs
API Details
ID
credo-ai:credo-ai-triggers-and-actions-api
Base URL
https://api.credo.ai/api/v2/{tenant}
Docs
https://docs.sdk.credo.ai/docs/intro/
Provider
Credo AI
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=credo-ai-triggers-and-actions-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/credo-ai-triggers-and-actions-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Credo AI Triggers And Actions 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.