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

Accept Evidence API

The Evidence API from Accept — 4 operation(s) for evidence.

Accept Evidence API is one of 23 APIs that Accept publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Evidence. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and an AsyncAPI specification.

This API exposes 4 operations across 4 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version 1.1.0-rc.1.

Requests are made against a single base URL, http://localhost:8080.

4 operations 4 paths 11 schemas 4 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.1.0-rc.1
Base URL
https://midas.accept.io
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

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

  • BearerAuth — Static bearer token. Configured via MIDASAUTHTOKENS or midas.yaml auth.tokens. Not required when auth.mode=open (development only).

Paths & Operations 4

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

Evidence 4
GET
/v1/evidence/envelopes/{id}/audit-events
Get the runtime audit-event chain for one envelope
getEvidenceEnvelopeAuditEvents 1 param → 200400401403404500501
GET
/v1/evidence/envelopes/{id}/integrity
Verify the audit-event chain integrity for one envelope
getEvidenceEnvelopeIntegrity 1 param → 200400401403404500501
GET
/v1/evidence/envelopes/{id}/packet
Export a decision evidence packet for one envelope
getEvidenceEnvelopePacket 1 param → 200400401403404500501
GET
/v1/evidence/audit-events
Search runtime audit events across envelopes
searchEvidenceAuditEvents 10 params → 200400401403500501

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are Envelope (18 properties), RuntimeAuditEvent (12 properties), RuntimeEvidenceIntegrityResponse (8 properties), ResolvedCapabilitySnapshot (6 properties). Each schema is shown below with its type and property counts.

ResolvedStructure
object
Service-led structural context resolved at evaluation time: the Process the Surface belongs to, the BusinessService that owns the Process, and the set of Capab…
3 properties
ResolvedProcessSnapshot
object
Point-in-time snapshot of the Process the resolved Surface belonged to at evaluation time. Captured as evidence on the envelope per ADR-0001; not derived from…
5 properties
RuntimeAuditEventListResponse
object
Response wrapper for GET /v1/evidence/envelopes/{id}/audit-events. items is always present (empty list for envelopes with no events recorded — an operationally…
3 properties 3 required
RuntimeEvidencePacket
object
Response wrapper for GET /v1/evidence/envelopes/{id}/packet (D30e). Composes three existing runtime evidence reads — envelope detail, the ordered audit-event c…
5 properties 5 required
RuntimeEvidenceIntegrityResponse
object
Response wrapper for GET /v1/evidence/envelopes/{id}/integrity (D30d). Reports the integrity status of the audit-event chain for one envelope. valid is true on…
8 properties 6 required
RuntimeAuditEvent
object
One audit event in the runtime evidence chain for a governance envelope. Returned by GET /v1/evidence/envelopes/{id}/audit-events (D30b). The shape mirrors the…
12 properties 11 required
Envelope
object
Tamper-evident governance record for a single evaluation.
18 properties
RuntimeAuditEventSearchResponse
object
Response wrapper for GET /v1/evidence/audit-events (D30c). Cross-envelope search results: items may span multiple envelopes, so the wrapper deliberately omits…
3 properties 2 required
ResolvedBusinessServiceSnapshot
object
Point-in-time snapshot of the BusinessService that owned the resolved Process at evaluation time. See ADR-0001.
5 properties
Error
object
1 property 1 required
ResolvedCapabilitySnapshot
object
Point-in-time snapshot of one Capability in the BusinessService's enabling set at evaluation time. The set as a whole is captured as a JSONB array on the envel…
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

accept-evidence-api-openapi.yml Raw ↑

Other APIs Accept publishes across the network.

Accept Agents API
Accept Aisystems API
Accept Businessservices API
Accept Capabilities API
Accept Controlplane API
Accept Coverage API
Accept Decisions API
Accept Drift API
Accept Envelopes API
Accept Escalation Targets API
Accept Escalations API
Accept Evaluate API
Where this information came from

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