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
Corridor

Corridor Findings API

Retrieve and manage security findings across projects.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

Tagged areas include Findings. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

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

Requests are made against a single base URL, https://app.corridor.dev/api.

4 operations 2 paths 3 schemas 1 DELETE2 GET1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://app.corridor.dev/api
Authentication
HTTP Bearer
Contact
Corridor Support
Resource Areas
1

Authentication & Security 1

Corridor Findings API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — API token with the cor prefix, generated from Profile API Tokens in the Corridor dashboard. Passed as Authorization: Bearer cor....

Paths & Operations 4

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

Findings 4

Retrieve and manage security findings across projects.

GET
/findings/search
Search findings
searchFindings 6 params → 200400401429
GET
/findings/{id}
Get finding
getFinding 1 param → 200401404
PUT
/findings/{id}
Update finding
updateFinding 1 param body → 200400401404
DELETE
/findings/{id}
Delete finding
deleteFinding 1 param → 200401404

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Finding (9 properties), FindingUpdate (8 properties), Error (1 property). Each schema is shown below with its type and property counts.

Finding
object
9 properties
FindingUpdate
object
8 properties
Error
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

corridor-findings-api-openapi.yml Raw ↑

Other APIs Corridor publishes across the network.

Corridor Dashboard API
AE Profile APIs.io
Corridor Guardrails API
AE Profile APIs.io
Corridor PR Reviews API
AE Profile APIs.io
Corridor Projects API
AE Profile APIs.io
Corridor Teams API
AE Profile APIs.io
#Findings
← Back to C APIs
API Details
ID
corridor:corridor-findings-api
Base URL
https://app.corridor.dev/api
Docs
https://docs.corridor.dev/api/reference
Provider
Corridor
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=corridor-findings-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/corridor-findings-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 Corridor Findings 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.