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

anecdotes Findings API

**Findings** record compliance gaps and issues, including links to controls, evidence, and policies.

anecdotes Findings API is one of 18 APIs that anecdotes 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, API documentation, an API reference, a getting-started guide, and authentication docs.

This API exposes 5 operations across 2 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.anecdotes.ai.

5 operations 2 paths 6 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.anecdotes.ai
Authentication
API Key, HTTP Bearer
Contact
Resource Areas
1

Authentication & Security 2

anecdotes Findings API declares 2 security schemes for authenticating requests. An API key is passed in the header as x-anecdotes-api-key (ApiKey). It accepts HTTP bearer tokens (JWT) (Bearer). By default, every request must be authenticated.

  • ApiKey — API key created in the Anecdotes platform. Used only for the Exchange API key endpoint.
  • Bearer — JWT obtained from the Exchange API key endpoint. Valid for 1 hour.

Paths & Operations 5

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

Findings 5

Findings record compliance gaps and issues, including links to controls, evidence, and policies.

GET
/compliance/v1/findings
Get all findings
listFindings 2 params → 200401422
POST
/compliance/v1/findings
Create finding
createFinding body → 201401422
DELETE
/compliance/v1/findings
Delete findings
deleteFindings body → 200401422
GET
/compliance/v1/findings/{finding_id}
Get finding by id
getFindingById → 200401404422
PATCH
/compliance/v1/findings/{finding_id}
Update finding status
patchFinding body → 200401404422

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are Finding (17 properties), FindingLinkedEntity (7 properties), FindingsPagination (5 properties), FindingsListResponse (2 properties). Each schema is shown below with its type and property counts.

FindingsDeleteResponse
object
Bulk delete result.
1 property 1 required
FindingLinkedEntity
object
Link from a finding to another object.
7 properties
FindingsListResponse
object
2 properties 1 required
FindingsPagination
object
Pagination metadata for get-all responses.
5 properties
Finding
object
A compliance finding.
17 properties
ValidationError
object
Validation error response. Each item in detail describes one validation failure. The loc array identifies the field path — each segment may be a string (field…
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

anecdotes-findings-api-openapi.yml Raw ↑

Other APIs anecdotes publishes across the network.

Anecdotes MCP Proxy
anecdotes Analysis Rules API
anecdotes Authorization API
anecdotes Create Controls API
anecdotes Create Evidence API
anecdotes Custom Fields API
anecdotes Download Evidence API
anecdotes Framework API
anecdotes Gated API
anecdotes Policy Manager API
anecdotes Public API
anecdotes Read Controls API
Where this information came from

This is an independent, third-party profile of anecdotes 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.