Developer Integrations about linen.dev

[dannysheridan]

+1 I'm interested in helping Linen offer client libraries when the time is right! My company, Fern, auto-generated client SDKs in Node, Java, Python, etc.

[cheeseblubber]

For the first version we should set the goal of giving a developer the ability to sync conversations into Linen.

1. As a developer I can create an api key

2. The api key should only work per community

3. As a developer I can create a bot user (this is how we can limit the bot’s permission to only modify their own resources)

4. As a developer I can switch out the api key

5. When someone sends a valid api key we should allow them to post to:

   1. We should allow them to only modify and delete their own messages/channels/users
   2. Rest api for messages
   3. Rest api for threads
   4. Api for channels
      1. history for channels (list all threads and messages)
      2. list all channels
   5. Rest api for users (Should we have a field for bot created or bot owner?) I’d rather not have bot be able to delete and create all users. (In the future we want a more granular approach but for the time being we want to limit the usage)
      1. Create users
      2. List users
      3. Edit users
      4. delete users

   (Early draft looking for feedback)

[wey-gu]

I am not experienced in defining APIs, but I'll try my best to provide "wishes", which hopefully isn't silly :)

• it seems we need proper scoping/RBAC mapped to different API action permissions.

• For messages, we could refer to slack(https://api.slack.com/methods/chat.postMessage) for fields as we shared a similar design, where, for the avatar, there is the capability to enable avatar(when as_user is true) with file or emoji, on top of that, maybe when the username field is an email or(OpenID? mastodon account, gravatar), we could support corresponding avatar system, too(consider we are not leveraging user system from linen in this case)?