GET

News and verification

News publication

/api/v2/news/{identifier}

AUTHENTICATIONNone · publicService ownercore-evidence-read-modelContract sourceOpenAPISTATUSProduction listed

Purpose and usage

What this endpoint does

Return one published newsroom entry by its canonical public identifier for article, feed, or developer-portal presentation.

When to use it

Call this after selecting a canonical publication identifier when the client needs the complete published entry rather than a collection summary.

OUTCOME · Inspect

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 inspect news publication.
Makes public newsroom content available through a stable machine contract with bounded filters, canonical identifiers, and a separate verification path.

ISOLATION + AUTHORITY

Publication content, editorial classification, featured placement, canonical identifier, integrity evidence, source provenance, and external claims remain distinct. A published or verified article is public information; it grants no identity, policy, investment, wallet, payment, settlement, publisher, matching, or trading authority.

BEFORE YOU CALL

No bearer credential is required; apply bounded filters and canonical public identifiers where the contract provides them.
Supply the required identifier (path) exactly as defined by the live contract.
Use bounded public filters or a canonical publication identifier, and decide whether the consuming workflow also requires the separate integrity and provenance projection.

WHAT TO DO NEXT

Use the same canonical identifier with the verification operation when the consuming workflow requires integrity or provenance assurance.
Preserve publication and revision metadata when caching or presenting the entry, and refresh it when current applicability matters.

AGENT GUIDANCE

Use news publication only for the purpose and lifecycle stage described by this operation; do not treat it as authority for an adjacent action.
Supply the required identifier (path) exactly as defined by the live contract.
Distinguish publication availability, editorial metadata, publication time, later revision, content integrity, provenance verification, and the truth or current applicability of external claims.
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

identifierpathRequired

identifierPublication UUID or slug. It selects the exact identifier addressed by this route.EXAMPLEidentifier-01

X-Request-IDheaderOptional

stringOptional caller correlation identifier. The gateway emits the effective value on the response.

RESPONSES

Status and payload examples

200Canonical resource projection.Read completed · JSON RESPONSE+

{
  "article_uuid": "01K4A7M4N8Y2Q6R9T3V5W7X1ZB",
  "author_name": "example-author-name",
  "category": "example-category",
  "content_commitment": "example-content-commitment",
  "created": "example-created",
  "editorial_date": "2026-09-02",
  "excerpt": "example-excerpt",
  "eyebrow": "example-eyebrow",
  "featured": true,
  "previous_commitment": "example-previous-commitment",
  "products": [
    "example-product"
  ],
  "published_at": "2026-09-02T18:30:00Z",
  "reading_minutes": 0,
  "revision": 0,
  "scheduled_at": "2026-09-02T18:30:00Z",
  "seo_description": "example-seo-description",
  "seo_title": "example-seo-title",
  "slug": "example-slug",
  "social_links": {},
  "status": "example-status",
  "tags": [
    "example-tag"
  ],
  "title": "example-title",
  "updated": "2026-09-02",
  "body": [
    {
      "items": [
        "example-item"
      ],
      "level": 1,
      "ordered": true,
      "text": "example-text",
      "type": "example-type"
    }
  ],
  "proof_chain": [
    {
      "created": "example-created",
      "event_hash": "example-event-hash",
      "payload_hash": "example-payload-hash",
      "previous_event_hash": "example-previous-event-hash",
      "sequence": 0,
      "type": "example-type"
    }
  ],
  "revisions": [
    {
      "change_summary": "example-change-summary",
      "content_commitment": "example-content-commitment",
      "created": "example-created",
      "previous_commitment": "example-previous-commitment",
      "published_at": "2026-09-02T18:30:00Z",
      "revision": 0,
      "revision_uuid": "01K4A7M4N8Y2Q6R9T3V5W7X1ZB"
    }
  ]
}

INTEGRATION DECISION

CALLER ACTION: Accept the returned representation or receipt, then use the same canonical identifier with the verification operation when the consuming workflow requires integrity or provenance assurance.
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 application, credential or callback record; compare scope, key identifier, secret-display state, version, and revocation or rotation receipt.

404The requested resource does not exist within the authenticated authority boundary.Resource not visible · JSON RESPONSE+

{
  "code": "invalid_credentials",
  "message": "the supplied Hybrid credential is invalid"
}

INTEGRATION DECISIONinvalid_credentials

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 application, credential or callback record; compare scope, key identifier, secret-display state, version, and revocation or rotation receipt.
ESCALATE WHEN: Escalate when a secret-bearing result was lost, key or callback state is ambiguous, or least-privilege scope cannot be established.

422Path, query, or body validation failed.Request must change · JSON RESPONSE+

{
  "code": "invalid_credentials",
  "message": "the supplied Hybrid credential is invalid"
}

INTEGRATION DECISIONinvalid_credentials

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 application, credential or callback record; compare scope, key identifier, secret-display state, version, and revocation or rotation receipt.
ESCALATE WHEN: Escalate when a secret-bearing result was lost, key or callback state is ambiguous, or least-privilege scope cannot be established.

503The authoritative service or read model is unavailable.Dependency unavailable or outcome uncertain · JSON RESPONSE+

{
  "code": "invalid_credentials",
  "message": "the supplied Hybrid credential is invalid"
}

INTEGRATION DECISIONinvalid_credentials

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 application, credential or callback record; compare scope, key identifier, secret-display state, version, and revocation or rotation receipt.
ESCALATE WHEN: Escalate when a secret-bearing result was lost, key or callback state is ambiguous, or least-privilege scope cannot be established.

OPERATIONAL NOTES

Security and lifecycle guarantees

news publication through the canonical Hybrid-Chain V2 interface. Authoritative owner: core-evidence-read-model.
The Rust gateway validates the public contract and routes only to the authoritative owner; clients never address internal services directly.
The tables and examples are derived from the current gateway source OpenAPI. Re-fetch the deployed OpenAPI before execution; deployment status is shown separately on this page.
Only parameters present in the OpenAPI operation are accepted; undocumented query keys fail closed with HTTP 422.

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