Skip to content
    hazBasehazBaseDocs
    API accessGitHub
    GuidesQuickstartMCPSDKHTTP APIPatternsBUILD WITH hazBase

    API ACCESS

    Start using the API

    Explore asset issuance, transfers and operations with the sample, then choose the APIs and SDKs for your application. For production integration, confirm the assets, features, authentication and operating requirements of your service.

    Run the sampleDiscuss API integration

    Choose where to start

    GoalWhat you can doGuide
    Explore the workflowUse the Day 0 kit to explore asset registration, issuance, transfers and history without applying for API access.Quickstart
    Plan an implementationReview architectures, data models and SDK examples for each use case.Implementation patterns
    Integrate a production serviceDiscuss required APIs, chains, user authentication and expected usage.Integration consultation

    Connect to a public information API

    Retrieve the supported-chain list with the following request. This read-only endpoint can be called without credentials.

    bash
    curl --fail --show-error https://api.hazbase.com/api/meta/chains

    Check for an HTTP 200 response containing JSON. This request does not issue or transfer assets. Check each endpoint’s specification for its authentication and permission requirements.

    Read the HTTP API reference

    User authentication and asset operations

    Wallet and asset APIs require the user session, signatures and permissions specified for each operation. Verify connectivity separately from authorization to operate on a particular asset.

    The Day 0 kit and distributed MCP sample operate a sample environment. Setting an API endpoint alone does not connect their issuance and transfers to a production service. Production integration includes authentication, approvals, result reconciliation and audit records.

    Authentication and walletsDeployment and operations

    What to cover in an integration discussion

    Tell us about your assets, service, required features and existing systems. Expected usage and timing help us discuss connection and operating requirements. You can contact us before all details are decided.

    Discuss your integration