POST

Issuer Launchpad

Link offering evidence

/api/v2/launchpad/offerings/{offering_id}/artifact-links

AUTHENTICATIONBearer token · launchpad:writeService ownerlaunchpad-serviceContract sourceOpenAPISTATUSProduction listed

Purpose and usage

What this endpoint does

Bind an offering to an exact Data Vault object version after the gateway re-resolves access, readiness, media type, and SHA-256 evidence.

When to use it

Use during private preparation to bind a disclosure claim to an exact authorized Data Vault object version.

OUTCOME · Create or advance

What changes

Appends a version-pinned evidence link after gateway re-attestation; it does not disclose the object until an eligible release is finalized.

WHY IT MATTERS

Gives people and agents a contract-backed way to advance link offering evidence.
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

Authenticate at the documented boundary: bearer+scope.
Supply the required offering_id (path), object_id (body), version_id (body), source_sha256 (body) exactly as defined by the live contract.
Use one Idempotency-Key only for retries of the same byte-equivalent logical mutation.
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

Re-read link offering evidence using the canonical identifier returned by this operation.
Reconcile an ambiguous response with the same idempotency key before attempting another mutation.
Follow returned canonical identifiers and commitments into the next explicit Launchpad stage, re-attesting protected evidence and re-reading release finality before public reliance.

AGENT GUIDANCE

Use link offering evidence only for the purpose and lifecycle stage described by this operation; do not treat it as authority for an adjacent action.
Supply the required offering_id (path), object_id (body), version_id (body), source_sha256 (body) 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.
After a timeout or conflict, read authoritative state before deciding whether an equivalent retry is safe.

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 launchpad:write authority.EXAMPLEBearer hc_live_…

offering_idpathRequired

identifierStable offering id selecting the exact resource addressed by this route.EXAMPLEoffering-id-01

X-Request-IDheaderOptional

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

Idempotency-KeyheaderRequired

ASCII string · 1–128Caller-generated stable key reused for retries of the same logical mutation.

classificationbodyOptional

PUBLIC_AFTER_FINALITY | private classificationDisclosure policy for the evidence link; defaults to PUBLIC_AFTER_FINALITY.EXAMPLEPUBLIC_AFTER_FINALITY

object_idbodyRequired

Data Vault identifierAuthorized Data Vault object selected as offering evidence.EXAMPLEvault-object-01J8FQ

source_sha256bodyRequired

SHA-256 · lowercase hexSHA-256 of original document bytes, verified against the exact upload's domain-separated Vault commitment; never an audit-event hash.EXAMPLEdddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd

version_idbodyRequired

Data Vault version identifierExact immutable object version re-resolved and attested by the gateway.EXAMPLEvault-version-01J8FR

REQUEST

JSON body example

{
  "classification": "PUBLIC_AFTER_FINALITY",
  "object_id": "vault-object-01J8FQ",
  "source_sha256": "dddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd",
  "version_id": "vault-version-01J8FR"
}

RESPONSES

Status and payload examples

201Mutation accepted and canonical state returned.Mutation completed · JSON RESPONSE+

{}

INTEGRATION DECISION

CALLER ACTION: Accept the returned representation or receipt, then re-read link offering evidence using the canonical identifier returned by this operation.
RETRY SAFETY: Do not repeat a successful mutation merely to confirm it. For one logical mutation, retain the same Idempotency-Key and byte-equivalent request. Never reuse that key for changed instructions.
STATE RECONCILIATION: Persist returned identifiers, versions, commitments, and receipts. Refresh the offering revision, evidence commitments, review and disclosure status, readiness milestone, issuer authority, and publication or finality receipt.

400Required headers or the canonical source-file digest are missing or malformed.Request must change · JSON RESPONSE+

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