Skip to content
    hazBasehazBaseDocs
    Open consoleGitHub
    GuidesQuickstartMCPSDKHTTP APIPatternsBUILD WITH hazBase

    API ACCESS

    Start using the API

    Register your application in the Developer Console and create credentials for the API and SDK. Sign in with your email, then configure access for your browser application or server.

    Register an applicationRun the sample first

    Get started in the console

    1. Verify your email and complete your profile

      Enter your email address and sign in with the six-digit code. Complete your profile on your first visit. Company name is optional for individuals and sole proprietors.

    2. Register your application

      Select “Register application” and enter a name that identifies your service. Manage Test and Live connections within the same application.

    3. Add a connection

      Choose Test or Live at the top right of the application page, then select “Add connection”. Enter a connection name and choose “Browser / web application” or “Server”. Add separate connections for each use as needed.

    Start with the free Developer plan allowance. Check your current limits and monthly request count under “Usage” in the console. Select “View requests by key” for a breakdown by connection and key.

    Configure access for your application

    Access methodWhat to configure
    Browser / web applicationRegister your application origins and use the generated publishable key in your API or SDK configuration. This key identifies the application; it does not authenticate a user.
    ServerCreate server credentials for the connection and store them securely on your server. Use the code example on the connection page to configure API or SDK access. Keep the private key out of browser code.
    User authenticationWhen you need per-user authentication, select “Configure user authentication” on the connection to add hazBase login or integrate an existing identity provider.

    Use https://api.hazbase.com as the API endpoint. The console is where you manage applications, credentials and usage.

    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
    Connect to the API or SDKRegister your application and connections in the console to obtain credentials and connection code examples.Register an application

    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