BigchainDB本地安装完成后访问localhost:9984获响应的技术咨询

Hey there! Great to hear you've got BigchainDB up and running locally successfully—your response from http://localhost:9984/ confirms your node is working as expected. Let's break down the details you're asking about:

First, let's recap your node's status response #

Here's the truncated response you received, formatted for readability:

{
  "api": {
    "v1": {
      "assets": "/api/v1/assets/",
      "docs": "https://docs.bigchaindb.com/projects/server/en/v1.3.0/http-client-server-api.html",
      "outputs": "/api/v1/outputs/",
      "statuses": "/api/v1/statuses/",
      "streams": "ws://localhost:9985/api/v1/streams/valid_transactions",
      "transactions": "/api/v1/transactions/"
    }
  },
  "docs": "https://docs.bigchaindb.com/projects/server/en/v1.3.0/",
  "keyring": [],
  "public_k..."
}

About app_id and app_key #

• Local single-node deployments don't require these parameters by default. These credentials are built for managed BigchainDB services or deployments that include an API gateway for authentication, rate-limiting, or access control.
• For development or testing on your local machine, you can interact directly with the BigchainDB API without providing an app_id or app_key—no authentication is enforced out of the box.
• If you later set up a multi-node cluster with an API gateway, you'd configure these values in your node settings and use them to authenticate API requests.

About api_path #

From your node's root response, you can see the official v1 API base path is /api/v1/. When making requests to your local node, your full API endpoints will take this structure:

• Assets: http://localhost:9984/api/v1/assets/
• Transactions: http://localhost:9984/api/v1/transactions/
• Outputs: http://localhost:9984/api/v1/outputs/

So the api_path you'll use for local calls is simply /api/v1/ (or the full base URL http://localhost:9984/api/v1/, depending on your client tool's configuration).

内容的提问来源于stack exchange，提问作者zSynopsis