DOCUMENTATIONv2

GET

Smart-contract lifecycle

List launches

/api/v2/contracts

AUTHENTICATIONBearer token · contracts:readAUTHORITATIVE OWNERcontract-authority-serviceCONTRACT AUTHORITYGenerated Rust OpenAPISTATUSSource ready · production listed

PURPOSE + BUSINESS CONTEXT

List smart-contract launch records visible to the caller.

WHEN THIS CALL IS USEFUL

Call this when a contract author, authority reviewer, deployment operator, or contract-lifecycle agent needs to discover launches and choose a canonical record for a later step so it can move a contract launch through draft, analysis, governance binding, freeze, evidence, and deployment preparation without collapsing those gates.

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 launches.
Creates an auditable path from editable launch intent to immutable, authority-bound deployment inputs.

ISOLATION + AUTHORITY

Launch owner, workspace, source artifact, analysis, declared authority, governance binding, frozen revision, deployment preparation, target network, and runtime deployment remain distinct. Analysis or preparation does not deploy code, freezing does not approve it, and no contract route grants wallet, publisher, matching, trading, or external-domain 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 launch owner, current revision, source and configuration commitments, authority analysis, governance binding, and target-network policy.

WHAT TO DO NEXT

Select one canonical identifier from the response and open its detail operation when the live contract exposes one.
Compare the launch revision, source and configuration commitments, authority analysis, governance binding, and target-network policy before moving to the next contract stage.

AGENT GUIDANCE

Use launches 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 editing, authority analysis, governance binding, freeze, evidence completion, deployment preparation, deployment, activation, and external effects as separate states.
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 contracts:read scope.EXAMPLEBearer hc_live_…

cursorqueryOptional

opaque stringCursor returned by the preceding page.

limitqueryOptional

integer · 1–200Maximum records to return.EXAMPLE50

statequeryOptional

stringOptional lifecycle-state filter.EXAMPLEREADY_TO_DEPLOY

RESPONSES

Status and payload examples

200Cursor-paginated workspace launch records.Read completed · JSON RESPONSE+

{
  "launches": [
    {
      "launchId": "9b51ed4c9c8f4aec85d1bd5520e40557",
      "slug": "treasury-settlement-v1",
      "name": "Treasury Settlement",
      "description": "Governed HybridScript settlement contract.",
      "networkId": "hybrid-devnet",
      "chainId": "hybrid-1",
      "contractKind": "HYBRIDSCRIPT",
      "packageHash": "sha256:1111111111111111111111111111111111111111111111111111111111111111",
      "sourceHash": "sha256:2222222222222222222222222222222222222222222222222222222222222222",
      "artifactHash": "sha256:3333333333333333333333333333333333333333333333333333333333333333",
      "manifestHash": "sha256:4444444444444444444444444444444444444444444444444444444444444444",
      "compilerProfile": "hybridscript-0.1",
      "factoryAddress": null,
      "constructorArgsHash": "sha256:5555555555555555555555555555555555555555555555555555555555555555",
      "initialStateHash": "sha256:6666666666666666666666666666666666666666666666666666666666666666",
      "runtimePolicyHash": "sha256:7777777777777777777777777777777777777777777777777777777777777777",
      "deploymentSalt": "treasury-settlement-001",
      "xuLimit": 100000,
      "capabilities": [
        "PAUSABLE",
        "TREASURY"
      ],
      "safeguards": {
        "upgradeTimelockSeconds": 86400,
        "mintCap": null,
        "emergencyPause": true,
        "recoveryDelaySeconds": 172800,
        "sourceVerified": true,
        "deterministicBuild": true
      },
      "authorities": {
        "DEPLOYMENT": "wallet-deploy",
        "POLICY": "wallet-policy",
        "RECOVERY": "wallet-recovery",
        "PAUSE": "wallet-pause",
        "UNPAUSE": "wallet-pause",
        "TREASURY": "wallet-treasury"
      },
      "acceptedRiskCodes": [],
      "launchIntentHash": null,
      "trustScore": null,
      "trustGrade": null,
      "state": "DRAFT",
      "expectedContractAddress": null,
      "contractAddress": null,
      "bindings": [],
      "events": [],
      "chainEvidence": [],
      "created": "2026-08-10T21:00:00Z",
      "updated": "2026-08-10T21:00:00Z"
    }
  ],
  "page": {
    "nextCursor": null,
    "limit": 50
  }
}

INTEGRATION DECISION

CALLER ACTION: Accept the returned representation or receipt, then select one canonical identifier from the response and open its detail operation when the live contract exposes one.
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 draft or launch revision, approval state, artifact commitments, authority assignments, and deployment or rejection receipt before another mutation.

400The request or required headers are malformed.Request must change · JSON RESPONSE+

{
  "code": "invalid_json",
  "message": "The request or required headers are malformed."
}

INTEGRATION DECISIONinvalid_json

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 draft or launch revision, approval state, artifact commitments, authority assignments, and deployment or rejection receipt before another mutation.
ESCALATE WHEN: Escalate when revision lineage, approvals, artifact hashes, deployment authority, or finality evidence cannot be proven consistently.

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

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

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 contract drafts, immutable revisions, reviews, approvals, launch inputs, and deployment evidence.
ESCALATE WHEN: Escalate when revision lineage, approvals, artifact hashes, deployment authority, or finality evidence cannot be proven consistently.

403The credential lacks the required contract scope.Authority or policy denied · JSON RESPONSE+

{
  "code": "insufficient_scope",
  "message": "The credential lacks the required contract scope."
}

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 contract drafts, immutable revisions, reviews, approvals, launch inputs, and deployment evidence.
ESCALATE WHEN: Escalate when revision lineage, approvals, artifact hashes, deployment authority, or finality evidence cannot be proven consistently.

404The requested launch does not exist in the caller's workspace.Resource not visible · JSON RESPONSE+

{
  "code": "contract_not_found",
  "message": "The requested launch does not exist in the caller's workspace."
}

INTEGRATION DECISIONcontract_not_found

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 draft or launch revision, approval state, artifact commitments, authority assignments, and deployment or rejection receipt before another mutation.
ESCALATE WHEN: Escalate when revision lineage, approvals, artifact hashes, deployment authority, or finality evidence cannot be proven consistently.

422The canonical contract request failed validation.Request must change · JSON RESPONSE+

{
  "code": "invalid_request",
  "message": "The canonical contract request failed validation."
}

INTEGRATION DECISIONinvalid_request

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 draft or launch revision, approval state, artifact commitments, authority assignments, and deployment or rejection receipt before another mutation.
ESCALATE WHEN: Escalate when revision lineage, approvals, artifact hashes, deployment authority, or finality evidence cannot be proven consistently.

503The authoritative contract registry is unavailable.Dependency unavailable or outcome uncertain · JSON RESPONSE+

{
  "code": "contract_registry_unavailable",
  "message": "The authoritative contract registry is unavailable."
}

INTEGRATION DECISIONcontract_registry_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 draft or launch revision, approval state, artifact commitments, authority assignments, and deployment or rejection receipt before another mutation.
ESCALATE WHEN: Escalate when revision lineage, approvals, artifact hashes, deployment authority, or finality evidence cannot be proven consistently.

OPERATIONAL NOTES

Security and lifecycle guarantees

Results are workspace-scoped by the authenticated principal.

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 ↗