channel_order_set
Set the order of the requester's own channel list: the order of their pinned channels, the order of every channel, or both. It changes nothing for anybody else. `workspace_write` · v1
Authorization
memberToken The tools internkim uses inside a company, callable from outside it. A token belongs to a person, and every call runs as that person, so a token can never do more than its owner can.
The first token is made signed in, from the settings screen. After that a token makes its own
successors: POST /token for a new one, DELETE /token for the old one, so a script rotates
without a browser. A token can neither mint a rung above its own nor revoke itself.
Send Authorization: Bearer <token> on every request.
In: header
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
text/plain
text/plain
text/plain
text/plain
text/plain
text/plain
text/plain
curl -X POST "https://example.com/tools/channel_order_set/invoke" \ -H "Content-Type: application/json" \ -d '{ "input": {} }'{ "toolName": "channel_order_set", "outcome": "succeeded", "selectedBackend": "device", "effects": [ { "objectType": "channel", "effect": "created", "id": "7a93de11-…" } ], "result": { "…": "the tool's own document" }}channel_order_get POST
Get how the requester orders their own channel list: the channels they pinned, in order, and the order of every channel. It is the requester's own and the same on every device they sign in on. `read` · v1
channel_owner_add POST
Make a member of a channel a co-owner beside the requester. Only an owner of the channel may do this. It is done as the requester, exactly as their messenger screen does it, and refused for the same reasons. `external_write` · v1