DOCUMENTATIONv2

GET

Newsroom operations

List articles

/api/v2/admin/news/articles

AUTHENTICATIONBearer token · admin:news:readAUTHORITATIVE OWNERnewsroom-serviceCONTRACT AUTHORITYGenerated Rust OpenAPISTATUSSource ready · production listed

PURPOSE + BUSINESS CONTEXT

List restricted draft, scheduled, and published newsroom records.

WHEN THIS CALL IS USEFUL

Use when an authorized editor or agent needs to discover private drafts and lifecycle posture before reading public verification or applying a revision.

OUTCOME · Discover

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 discover articles.
Creates an attributed and versioned editorial workflow with permanent slugs, explicit publication actions, presentation metadata, and retained reasons for lifecycle changes.

ISOLATION + AUTHORITY

Editor identity, article UUID, permanent slug, structured body, metadata, revision version, schedule, publication, archive reason, public projection, and integrity verification remain distinct. Editorial authority does not grant tenant, identity, financial, wallet, settlement, matching, or trading authority.

BEFORE YOU CALL

Authenticate at the documented boundary: bearer+scope.
Use the live OpenAPI schema as the authority for the exact request shape and response model.
Resolve the editor authority, article UUID or unique permanent slug, current revision, requested lifecycle action, attribution, and required publication or archival reason.

WHAT TO DO NEXT

Select an article UUID and inspect its exact revision, lifecycle status, schedule, slug, attribution, and presentation metadata before editing.
Use the public article and verification projections separately after publication; private listing presence does not prove public visibility.

AGENT GUIDANCE

Use articles only for the purpose and lifecycle stage described by this operation; do not treat it as authority for an adjacent action.
Use the live OpenAPI schema as the authority for the exact request shape and response model.
Treat draft creation, content revision, scheduling, publication, public visibility, verification, archival, and external factual accuracy as separate concerns.
Use response links and canonical identifiers instead of constructing internal service URLs or scraping the website.

MACHINE CONTRACT

The exact deployed parameters, schemas, responses, security requirements, and Hybrid-Chain agent metadata are authoritative at this operation's production OpenAPI JSON Pointer. The readable tables below add integration guidance; the deployed OpenAPI controls if guidance and the machine contract ever differ.

Open the authoritative production contract ↗

EXTENDED INTEGRATION GUIDANCE

Readable request and response reference

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 admin:news:read scope.EXAMPLEBearer hc_live_…

cursorqueryOptional

opaque 32-character hexadecimal cursornext_cursor from the previous page; reuse only with the same status and q filters.EXAMPLEdddddddddddddddddddddddddddddddd

limitqueryOptional

integer · 1–200 · default 50Maximum newest article summaries returned.EXAMPLE50

statusqueryOptional

DRAFT | SCHEDULED | PUBLISHED | ARCHIVEDExact lifecycle filter; omit to include all visible restricted states.EXAMPLEDRAFT

qqueryOptional

string · max 200Case-insensitive search over documented editorial summary fields.EXAMPLEagent API

RESPONSES

Status and payload examples

200Newest owner-scoped article summaries. Bodies, revisions, and proof chains are intentionally omitted from the collection.Read completed · JSON RESPONSE+

{
  "items": [
    {
      "article_uuid": "7d41f32773b64855a72106a62ea6a5f1",
      "slug": "agent-ready-api-reference",
      "title": "Hybrid-Chain publishes an agent-ready API reference",
      "eyebrow": "Developer platform",
      "category": "engineering",
      "excerpt": "The V2 reference now exposes an executable OpenAPI contract and retained publication evidence.",
      "author_name": "Hybrid-Chain Editorial",
      "status": "DRAFT",
      "featured": true,
      "tags": [
        "api",
        "agents"
      ],
      "products": [
        "developer-platform"
      ],
      "social_links": {
        "canonical": "https://hybrid-chain.com/news/agent-ready-api-reference"
      },
      "seo_title": "Agent-ready Hybrid-Chain API",
      "seo_description": "Integrate Hybrid-Chain V2 from its live OpenAPI 3.1 contract.",
      "reading_minutes": 2,
      "published_at": null,
      "scheduled_at": null,
      "editorial_date": null,
      "revision": 1,
      "content_commitment": "sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
      "previous_commitment": null,
      "created": "2026-09-01T18:30:00Z",
      "updated": "2026-09-01T18:30:00Z"
    }
  ],
  "next_cursor": null,
  "limit": 50
}

INTEGRATION DECISION

CALLER ACTION: Accept the returned representation or receipt, then select an article UUID and inspect its exact revision, lifecycle status, schedule, slug, attribution, and presentation metadata before editing.
RETRY SAFETY: For another page, send the returned opaque cursor unchanged with the same filters. Restart without a cursor when a new snapshot is required.
STATE RECONCILIATION: Use returned identifiers and versions as the comparison point for later reads. Refresh the exact managed resource and its tenant, role, policy, version, workload, and audit state before another administrative action.

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

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

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 tenant-scoped administrative aggregates, workloads, controls, reviews, and audit-safe operational projections.
ESCALATE WHEN: Escalate when tenant binding, administrator role, step-up purpose, control version, workload state, or audit evidence remains ambiguous.

403The credential lacks exact admin:news:read authority.Authority or policy denied · JSON RESPONSE+

{
  "code": "insufficient_scope",
  "message": "The credential lacks exact admin:news: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 tenant-scoped administrative aggregates, workloads, controls, reviews, and audit-safe operational projections.
ESCALATE WHEN: Escalate when tenant binding, administrator role, step-up purpose, control version, workload state, or audit evidence remains ambiguous.

422The cursor, exact status, search term, or limit is invalid.Request must change · JSON RESPONSE+

{
  "code": "invalid_newsroom_query",
  "message": "The cursor, exact status, search term, or limit is invalid."
}

INTEGRATION DECISIONinvalid_newsroom_query

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 exact managed resource and its tenant, role, policy, version, workload, and audit state before another administrative action.
ESCALATE WHEN: Escalate when tenant binding, administrator role, step-up purpose, control version, workload state, or audit evidence remains ambiguous.

503The authoritative Core publication ledger is unavailable.Dependency unavailable or outcome uncertain · JSON RESPONSE+

{
  "code": "newsroom_unavailable",
  "message": "The authoritative Core publication ledger is unavailable."
}

INTEGRATION DECISIONnewsroom_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 exact managed resource and its tenant, role, policy, version, workload, and audit state before another administrative action.
ESCALATE WHEN: Escalate when tenant binding, administrator role, step-up purpose, control version, workload state, or audit evidence remains ambiguous.

OPERATIONAL NOTES

Security and lifecycle guarantees

Use the collection to locate a private draft or inspect lifecycle posture before applying a revision. Responses are no-store and the authenticated owner context cannot be overridden by a query parameter.
DRAFT and SCHEDULED are not publication. PUBLISHED describes editorial visibility; it does not by itself prove external delivery, syndication, or website deployment.
Treat next_cursor as opaque and reuse it only with identical status and q filters. A null cursor means the filtered collection is complete.
The collection minimizes data intentionally. Use the returned stable article_uuid and latest revision in the governed publisher workflow before making a consequential change.

DOCUMENTATION STATUS

This route is implemented in canonical gateway source and appears in the production OpenAPI snapshot observed 2026-09-11T06:35:11.572Z. Authentication, tenant, feature, venue, and market policy still apply.

Verify the exact production OpenAPI operation ↗Return to the V2 directory ↗