title: Hyperledger Fabric - How to create Channels via API and dynamically
body: <p>As far as I have seen most Hyperledger Fabric examples deal with the idea to create channels and thus private ledgers to apply view and data restrictions between parties. (e.g. <a href="https://courses.edx.org/courses/course-v1:LinuxFoundationX+LFS171x+3T2017/courseware/f0db5224eb0e4bbb8cc1e93a6819012c/8a27d35a4ae34e2ea5d2c43e8b3cb71c/?activate_block_id=block-v1%3ALinuxFoundationX%2BLFS171x%2B3T2017%2Btype%40sequential%2Bblock%408a27d35a4ae34e2ea5d2c43e8b3cb71c" rel="nofollow noreferrer">https://courses.edx.org/courses/course-v1:LinuxFoundationX+LFS171x+3T2017/courseware/f0db5224eb0e4bbb8cc1e93a6819012c/8a27d35a4ae34e2ea5d2c43e8b3cb71c/?activate_block_id=block-v1%3ALinuxFoundationX%2BLFS171x%2B3T2017%2Btype%40sequential%2Bblock%408a27d35a4ae34e2ea5d2c43e8b3cb71c</a>) </p>
  
  <p>But as far as I know these channels can't be created/bootstrapped via API, only via scripting. </p>
  
  <p>Two questions - If you have a lot of different parties like insurers and customers </p>
  
  <ol>
  <li>How should one handle this situation without a Client API and </li>
  <li>How to deal with these many channels/ledgers then in the future? </li>
  </ol>
  
  <p>Thanks
  Oliver </p>