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 Create Evidence API

Create custom **Evidence Collections**, **attach** JSON/CSV files to a collection, and upload **manual** evidence of any type. Customer-pushed evidence can also carry **IPE** (Information Produced by Entity) — the structured queries that produced the data — supplied inline (`evidence_api_query`) or as a JSON file (`ipe_file`) on create/attach, or added later to an existing collection via the `/ipe` endpoint. IPE can only be written to API (customer-pushed) evidence.

anecdotes Create Evidence API is one of 18 APIs that anecdotes publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Create Evidence. 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 4 operations across 4 paths, and defines 5 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.

4 operations 4 paths 5 schemas 4 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 Create Evidence 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 4

Across 4 paths, the API surfaces 4 operations — 4 POST. Each is listed below with its method, path, parameters, and response codes.

Create Evidence 4

Create custom Evidence Collections, attach JSON/CSV files to a collection, and upload manual evidence of any type. Customer-pushed evidence can also carry IPE (Information Produce…

POST
/evidence/v1/evidence
Create Manual Evidence
uploadManualEvidence body → 200401422
POST
/evidence/v1/evidence/create
Create an Evidence Collection
createEvidenceCollection body → 201401422
POST
/evidence/v1/evidence/{evidence_id}/attach
Create Evidence within a Collection
attachEvidenceToCollection 1 param body → 201400401422
POST
/evidence/v1/evidence/{evidence_instance_id}/ipe
Add IPE to a Collection
attachEvidenceIpe 1 param body → 200401404422

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Evidence_AttachIpeResponse (2 properties), Evidence_ErrorResponse (2 properties), ValidationError (1 property), Evidence_DetailMessage (1 property). Each schema is shown below with its type and property counts.

Evidence_ErrorResponse
object
Error body returned for Anecdotes business-logic errors (e.g. IPE validation failures and the API-evidence-only guard). errordetail repeats the HTTP status cod…
2 properties 2 required
Evidence_CreateEvidenceResponse
object
1 property 1 required
Evidence_DetailMessage
object
Error body for input-combination errors raised directly by the endpoint (FastAPI HTTPException with a string detail).
1 property 1 required
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
Evidence_AttachIpeResponse
object
Response returned after attaching or replacing IPE on an evidence collection.
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

anecdotes-create-evidence-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 Custom Fields API
anecdotes Download Evidence API
anecdotes Findings 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 Create Evidence 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.