Assets

Adapters and sync jobs push domain assets onto the peer’s configured chaincode through /api/assets.

Requires X-Api-Key when configured. Machine-readable shapes: API reference.

Sync

POST /api/assets
X-Api-Key: <key>
Content-Type: application/json

{
  "assets": [
    {
      "id": "user-123",
      "type": "user",
      "data": { "email": "a@example.com" }
    }
  ],
  "options": {
    "batchSize": 10,
    "continueOnError": false
  }
}

Response summarizes succeeded / failed asset IDs and ledger transaction IDs. Unknown chaincode mappings return UNKNOWN_CHAINCODE.

Query

POST /api/assets/query
X-Api-Key: <key>
Content-Type: application/json

{
  "type": "user",
  "limit": 50
}

Query semantics are chaincode-specific (resolved from peer config / mapping). Prefer documented type values for your installed contract.

Read by id

GET /api/assets/{id}
X-Api-Key: <key>

Returns the asset payload for the peer’s configured read query.