X

Actions

Home > Application Reference > Twitch

Jump to a Section

Overview

Authorizing an Account

Authorization for Twitch

  1. Connection Nickname - Enter a connection nickname. This is just a display name for this connection. Use clear naming conventions so that in the future it is clear which account the connection is associated with.

  2. Twitch uses Oauth2 for authentication. After entering your nickname, click the create button. An OAuth window opens asking for your Twitch username and password.

Enter your Twitch account information, then click Log In. You will be asked to allow Azuqua to access your Twitch account. Click Authorize. You should then be redirected back to Azuqua, with a successful connection to Twitch.

    Actions

    • Custom API Action

      Make a custom HTTP request to the Twitch API.

      Twitch API documentation: https://dev.twitch.tv/docs/api/. Ensure that you are using the Helix API version.

      • GET: retrieves data from a web server based on your parameters. GET requests a representation of the specified resource, and if successful will receive a 200 OK response message with the requested content. Additional documentation here.

      • POST: sends data to a web server based on your parameters. POST requests include actions like uploading a file. Multiple POST’s may result in a different outcome than a single POST, so you should be cautious about unintentionally sending multiple POST’s. Additional documentation here.

      • PUT: sends data to a location in the web server based on your parameters. PUT requests include actions like uploading a file. The difference between a PUT and POST is that PUT is idempotent, meaning that the result of a single successful PUT is the same as many identical PUT’s. Additional documentation here.

      • DELETE: deletes the specified resource from the web server based on your parameters (if the resource exists). Additional documentation here.

      Input Fields

      • Request

        • Relative URL (string) - Relative request URL. The relative URL structure for this action follows the /helix route. E.g. - If the full API URL is https://api.twitch.tv/helix/streams, then the Relative URL would be /streams.

          Example: /streams

        • Query (object) - Query parmaeters for the request.

          Example: {"game_id":"5"}

        • Headers (object) - Headers for the request.

          Example: {"Accept":"application/json"}

        • Body (object) (only for POST, PUT, and DELETE) - Body of the request.

          Example: {"foo": "automation, "bar": "integration"}

      Output Fields

      • Response
        • Status Code (number) - The status code of the HTTP response. Here is a list of all status codes.
        • Headers (object) - The response headers. A more detailed context for the response/status code that doesn’t relate to the output body. Not all headers that appear in a response header are response headers, meaning that some are unlikely to be useful to you.
        • Body (object) - The response body. Depending on the HTTP request you chose in Options, you may receive some data back. That data, such as the data from a GET request, will be contained in this Body object.