GET

Evidence streams

List events

/api/v2/evidence-streams/{stream_uuid}/events

AUTHENTICATIONBearer token · evidence:readService ownerevidence-stream-serviceContract sourceOpenAPISTATUSProduction listed

Purpose and usage

What this endpoint does

List retained events and verification state for a stream.

When to use it

Load a bounded newest-first commitment chain for one owned stream after resolving its schema and source posture.

OUTCOME · Reconcile

What changes

Read-only projection; it grants no mutation, settlement, traffic, or authority change.

WHY IT MATTERS

Gives people and agents a contract-backed way to reconcile events.
Lets integrations follow evidence from schema and source enrollment through ordered commitments, validation posture, operational alerts, and exception review.

ISOLATION + AUTHORITY

Schema, source, signer, stream, event, payload, sequence, validation, quarantine, alert, acknowledgement, retention, and business-outcome authorities remain distinct. Evidence visibility or cryptographic validity does not by itself prove semantic truth, regulatory acceptance, settlement, or authorization for an external action.

BEFORE YOU CALL

Authenticate at the documented boundary: bearer+scope.
Supply the required stream_uuid (path) exactly as defined by the live contract.
Resolve the owner scope, schema, source, stream, sequence or time window, validation posture, and minimum payload disclosure required by the decision.

WHAT TO DO NEXT

Correlate the schema, source, stream, sequence, commitment, validation, quarantine, and alert state for the selected evidence lineage.
Escalate or acknowledge exceptions through their separately authorized workflow; do not equate cryptographic validity with semantic or regulatory acceptance.

AGENT GUIDANCE

Use events only for the purpose and lifecycle stage described by this operation; do not treat it as authority for an adjacent action.
Supply the required stream_uuid (path) exactly as defined by the live contract.
Distinguish schema validity, source authenticity, signature validity, sequence continuity, payload availability, quarantine status, alert acknowledgement, operational health, and business acceptance.
Use response links and canonical identifiers instead of constructing internal service URLs or scraping the website.

Contract reference

Use the deployed OpenAPI for exact parameters, schemas and security requirements. The tables below provide integration guidance.

Open this operation in OpenAPI

Request and response

Make the request

Examples illustrate integration intent; the referenced OpenAPI operation and component schemas define the executable shape.

PARAMETERS

Headers, path, query, and body

NAMELOCATIONPRESENCETYPE / RULES / PURPOSE

AuthorizationheaderRequired

Bearer tokenCredential containing the evidence:read scope.EXAMPLEBearer hc_live_…

stream_uuidpathRequired

32-character hexadecimal identifierOwned stream identifier returned by the Evidence Streams collection.EXAMPLE6ecf43f09da445c7aa534b51b2cf05cb

limitqueryOptional

integer · 1–200 · default 100Maximum newest records returned. This is a bounded window, not a durable synchronization cursor.EXAMPLE100

RESPONSES

Status and payload examples

200Newest retained events in descending sequence order with commitment and validation evidence but no payload cleartext.Read completed · JSON RESPONSE+

{
  "items": [
    {
      "event_id": "f10403f921f34aef9574e449ca2dbac0",
      "stream_id": "6ecf43f09da445c7aa534b51b2cf05cb",
      "device_id": "038ee1b3c92445bab120a611598c677d",
      "sequence": 18421,
      "event_type": "temperature.observation",
      "occurred_at": "2026-09-01T20:16:00Z",
      "received_at": "2026-09-01T20:16:01Z",
      "payload_commitment": "sha256:dddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd",
      "previous_chain_commitment": "sha256:eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee",
      "chain_commitment": "sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
      "signature_algorithm": "HMAC-SHA256",
      "signature_key_id": "evidence-stream-v1",
      "server_signature": "base64url-signature",
      "billing_state": "POSTED",
      "status": "ACCEPTED",
      "source_authenticated": true,
      "payload_size_bytes": 164,
      "validation": {
        "schema": "VALID",
        "source_signature": "VALID",
        "timestamp": "VALID",
        "nonce": "VALID",
        "storage": "INLINE_PRIVATE"
      }
    }
  ],
  "total": 1
}

INTEGRATION DECISION

CALLER ACTION: Accept the returned representation or receipt, then correlate the schema, source, stream, sequence, commitment, validation, quarantine, and alert state for the selected evidence lineage.
RETRY SAFETY: Repeat only when the integration needs a fresher authoritative projection.
STATE RECONCILIATION: Use returned identifiers and versions as the comparison point for later reads. Refresh the stream and checkpoint, compare event commitment, sequence, retention boundary, consumer position, and latest accepted receipt.

404The stream does not exist in the authenticated workspace.Resource not visible · JSON RESPONSE+

{
  "code": "evidence_resource_not_found",
  "message": "The stream does not exist in the authenticated workspace."
}

INTEGRATION DECISIONevidence_resource_not_found

CALLER ACTION: Verify the canonical identifier and authenticated owner boundary. A 404 may intentionally conceal a resource outside the caller's authority.
RETRY SAFETY: Do not retry the unchanged identifier repeatedly. Refresh the relevant collection or lookup before choosing another identifier.
STATE RECONCILIATION: Refresh the stream and checkpoint, compare event commitment, sequence, retention boundary, consumer position, and latest accepted receipt.
ESCALATE WHEN: Escalate when sequence continuity, checkpoint commitment, retention, ownership, or consumer position cannot be proven.

422The stream identifier or limit is invalid.Request must change · JSON RESPONSE+

{
  "code": "invalid_evidence_identifier",
  "message": "The stream identifier or limit is invalid."
}

INTEGRATION DECISIONinvalid_evidence_identifier

CALLER ACTION: Rebuild the request from the live OpenAPI operation and correct the rejected method, media type, header, parameter, or body field.
RETRY SAFETY: Do not retry the same invalid request. A corrected read may be sent as a new attempt.
STATE RECONCILIATION: Compare the submitted values with the documented constraints before another call. Refresh the stream and checkpoint, compare event commitment, sequence, retention boundary, consumer position, and latest accepted receipt.
ESCALATE WHEN: Escalate when sequence continuity, checkpoint commitment, retention, ownership, or consumer position cannot be proven.

401The bearer credential is missing, expired, or invalid.Authentication required · JSON RESPONSE+

{
  "code": "invalid_credentials",
  "message": "The bearer credential is missing, expired, or invalid."
}

INTEGRATION DECISIONinvalid_credentials

CALLER ACTION: Discard the rejected credential, complete the documented authentication or reassertion flow, and rebuild any request signature with fresh timestamps and nonces.
RETRY SAFETY: Retry only with a newly valid credential and fresh replay-protection values. Do not replay an expired signature.
STATE RECONCILIATION: Authentication failed before an authoritative read was returned for owner-scoped stream metadata, events, checkpoints, commitments, retention windows, and consumer positions.
ESCALATE WHEN: Escalate when sequence continuity, checkpoint commitment, retention, ownership, or consumer position cannot be proven.

403The credential lacks explicitly provisioned evidence:read authority.Authority or policy denied · JSON RESPONSE+

{
  "code": "insufficient_scope",
  "message": "The credential lacks explicitly provisioned evidence:read authority."
}

INTEGRATION DECISIONinsufficient_scope

CALLER ACTION: Verify the exact scope, tenant or workspace membership, owner boundary, step-up purpose, feature policy, and resource eligibility. Never broaden authority automatically.
RETRY SAFETY: Do not retry until the missing authority or policy condition has been deliberately resolved with least privilege.
STATE RECONCILIATION: Confirm the caller and resource resolve to the same authority boundary for owner-scoped stream metadata, events, checkpoints, commitments, retention windows, and consumer positions.
ESCALATE WHEN: Escalate when sequence continuity, checkpoint commitment, retention, ownership, or consumer position cannot be proven.

503The authoritative Core Evidence Streams projection is unavailable.Dependency unavailable or outcome uncertain · JSON RESPONSE+

{
  "code": "evidence_streams_unavailable",
  "message": "The authoritative Core Evidence Streams projection is unavailable."
}

INTEGRATION DECISIONevidence_streams_unavailable

CALLER ACTION: Treat the failure as transient and preserve the last known good representation without presenting it as fresh.
RETRY SAFETY: Retry with bounded exponential backoff and jitter; stop after the integration's failure budget is exhausted.
STATE RECONCILIATION: Refresh the stream and checkpoint, compare event commitment, sequence, retention boundary, consumer position, and latest accepted receipt.
ESCALATE WHEN: Escalate when sequence continuity, checkpoint commitment, retention, ownership, or consumer position cannot be proven.

OPERATIONAL NOTES

Security and lifecycle guarantees

Verify each payload_commitment, previous_chain_commitment, chain_commitment, and server signature according to the key policy before claiming chain integrity. A bounded response may not contain the prior link needed for complete verification.
source_authenticated means a scoped credential passed at ingestion. It does not attest device calibration, factual accuracy, current authorization, or the legal/business effect of the event.
validation reports retained ingestion checks. ACCEPTED and VALID are evidence posture, never settlement, payment, trading, governance, disclosure, or operational authority.
Raw payloads, metadata, source keys, credentials, nonces, idempotency material, owner/actor IDs, attachment content, and billing identifiers are excluded. Responses are no-store.

Reference version and availability details

This route is implemented in canonical gateway source and appears in the production OpenAPI snapshot observed 2026-10-02T23:27:55.510Z. Authentication, tenant, feature, venue, and market policy still apply.

Verify the exact production OpenAPI operation Return to the V2 directory