Link diligence evidence

/api/v2/launchpad/diligence-items/{diligence_item_id}/artifact-links

AUTHENTICATIONBearer token · launchpad:writeAUTHORITATIVE OWNERlaunchpad-serviceCONTRACT AUTHORITYGenerated Rust OpenAPISTATUSSource ready · production listed

PURPOSE + BUSINESS CONTEXT

Attach an exact authorized Data Vault version to one required diligence item after gateway-side evidence re-attestation.

WHEN THIS CALL IS USEFUL

Use to satisfy one diligence requirement with an exact authorized Data Vault version before a reviewer pins the evidence view.

OUTCOME · Create or advance

What changes

Appends a case-scoped evidence link after re-attestation; it does not mark the requirement reviewed or accepted.

WHY IT MATTERS

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

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

diligence_item_idpathRequired

identifierCanonical diligence item id. It selects the exact diligence item id addressed by this route.EXAMPLEdiligence-item-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.

object_idbodyRequired

Data Vault identifierAuthorized Data Vault object selected for this requirement.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

{
  "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 diligence 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"
}