What is it?
You can get a general overview of Linked Roles and Connections here.
To build an app with Connection features, you will first need an Application and Bot user configured in the Developer Portal, a target Connection, and a linked role. This article will walk you through these components.
For an example app and more detailed info on each step, visit our Developer Docs: https://discord.com/developers/docs/tutorials/configuring-app-metadata-for-linked-roles
First, ensure you have created a Bot user in the Developer Portal to interface with your Connection of choice. The Bot will also need a redirect URL for the OAuth2 flow. The redirect URL would depend on the server as well as how you are hosting your app.
You're also going to need to set a custom endpoint URL for your linked roles in the Developer Portal.
Additionally, in order to get information from something like Steam or any other API, you'll need to visit their developer docs to configure and send a HTTP request to their API.
The last thing to configure is the linked role itself. You are able to register the linked role metadata by setting them in a PUT request to our API similar to registering slash commands that are managed by the app. This metadata will be used as the requirements users must meet to get the linked role.
Note: use a Bot token for authentication and not a user token.
Finally, head to your server settings and create a role. In the Links tab, you'll be able to add requirements for the role. With that done, you're all set!
Now if users want to connect their accounts, they can click the server name at the top left and look for the linked role that is being managed by your app.