GET

Issuer Launchpad

Get finalized release

/api/v2/launchpad/releases/{release_id}
AUTHENTICATIONNone · publicService ownerlaunchpad-serviceContract sourceOpenAPISTATUSProduction listed

Purpose and usage

What this endpoint does

Return one finalized release, its sequence, signatures, finality, availability, and supersession posture.

When to use it

Use to reconcile one finalized public release's sequence, signatures, finality, availability, and supersession posture.

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 finalized release.
  • Connects private issuer preparation to public, citation-bearing disclosure without exposing draft evidence or collapsing review, signature, finality, and availability into one state.

ISOLATION + AUTHORITY

Workspace, issuer, offering, security-class draft, Data Vault object version, requirement pack, diligence case, evidence view, reviewer decision, auditor attestation, release, signer, validator finality, replication, public index, and investor eligibility remain distinct. Launchpad cannot issue, mint, custody, sell, trade, match, settle, or authorize an investment, and its public routes expose only finalized disclosure evidence.

BEFORE YOU CALL

  • No bearer credential is required; apply bounded filters and canonical public identifiers where the contract provides them.
  • Supply the required release_id (path) exactly as defined by the live contract.
  • Resolve the authenticated workspace and derived issuer, reviewer, auditor, signer, or publisher authority for this stage; use exact Data Vault versions and distinguish private preparation from finalized public disclosure.

WHAT TO DO NEXT

  • Follow returned canonical identifiers and commitments into the next explicit Launchpad stage, re-attesting protected evidence and re-reading release finality before public reliance.
  • Refresh finalized release when its observation time, version, or lifecycle state is no longer adequate for the decision.

AGENT GUIDANCE

  • Use finalized release only for the purpose and lifecycle stage described by this operation; do not treat it as authority for an adjacent action.
  • Supply the required release_id (path) exactly as defined by the live contract.
  • Keep draft creation, evidence linking, evidence-view pinning, review, attestation, release assembly, freeze, signature, submission, validator finality, replicated availability, indexing, and supersession as separate lifecycle facts.
  • 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
release_idpathRequired

identifierStable release id selecting the exact resource addressed by this route.EXAMPLErelease-id-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+
{}
INTEGRATION DECISION
CALLER ACTION
Accept the returned representation or receipt, then follow returned canonical identifiers and commitments into the next explicit Launchpad stage, re-attesting protected evidence and re-reading release finality before public reliance.
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 offering revision, evidence commitments, review and disclosure status, readiness milestone, issuer authority, and publication or finality receipt.
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 offering revision, evidence commitments, review and disclosure status, readiness milestone, issuer authority, and publication or finality receipt.
ESCALATE WHEN
Escalate when issuer authority, diligence evidence, disclosures, approvals, publication, or chain finality cannot be matched to one immutable revision.
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 offering revision, evidence commitments, review and disclosure status, readiness milestone, issuer authority, and publication or finality receipt.
ESCALATE WHEN
Escalate when issuer authority, diligence evidence, disclosures, approvals, publication, or chain finality cannot be matched to one immutable revision.

OPERATIONAL NOTES

Security and lifecycle guarantees

  • Return one finalized release, its sequence, signatures, finality, availability, and supersession posture.
  • 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