# Query and Create Exercise as multiple parties

**URL:** <https://forum.canton.network/t/query-and-create-exercise-as-multiple-parties/409>\
**Category:** Outreach\
**Tags:** daml, json-api\
**Created:** [May 8, 2020, 6:12pm UTC](https://forum.canton.network/t/query-and-create-exercise-as-multiple-parties/409 "2020-05-08T18:12:12Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Leonid\_Shlyapnikov](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.canton.network/leonid_shlyapnikov/32/241_2.png) [@Leonid\_Shlyapnikov](https://forum.canton.network/u/Leonid_Shlyapnikov)\
**Post date:** [May 8, 2020, 8:31pm UTC](https://forum.canton.network/t/query-and-create-exercise-as-multiple-parties/409/6 "2020-05-08T20:31:32Z")

</div>

Ledger API supports multi-party reads, JSON API does not.

JSON API authentication/authorization was designed a bit a head of Ledger API and we did not have a use case for multi-party reads in JSON API.

Our take on multi-party authentication in JSON API:

- 1 party - 1 authentication token (JWT), no super users
- if participant needs to act as multi-party, this participant needs multiple authentication tokens (one per party)

---

_[View the full topic](https://forum.canton.network/t/query-and-create-exercise-as-multiple-parties/409)._