Get Videos with Twitch API on New Requests from HTTP / Webhook API

Pipedream makes it easy to connect APIs for Twitch, HTTP / Webhook and 2,900+ other apps remarkably fast.

Trigger workflow on

New Requests from the HTTP / Webhook API

Next, do this

Get Videos with the Twitch API

No credit card required

▶

Watch us build a workflow

8 min

Watch now ➜

Trusted by 1,000,000+ developers from startups to Fortune 500 companies

Developers ♥ Pipedream

Getting Started#

This integration creates a workflow with a HTTP / Webhook trigger and Twitch action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Requests trigger
1. Optional- Configure Body Only
2. Optional- Configure Response Status Code
3. Optional- Configure Response Content-Type
4. Optional- Configure Response Body
5. Connect your HTTP / Webhook account
Configure the Get Videos action
1. Connect your Twitch account
2. Optional- Configure Video ID
3. Optional- Configure User ID
4. Optional- Configure Game ID
5. Optional- Configure Stream Language
6. Optional- Select a Period
7. Optional- Select a Sort
8. Optional- Select a Type
9. Configure Max Items
Deploy the workflow
Send a test event to validate your setup
Turn on the trigger

Details#

This integration uses pre-built, source-available components from Pipedream's GitHub repo. These components are developed by Pipedream and the community, and verified and maintained by Pipedream.

To contribute an update to an existing component or create a new component, create a PR on GitHub. If you're new to Pipedream component development, you can start with quickstarts for trigger span and action development, and then review the component API reference.

Trigger#

New Requests on HTTP / Webhook

Description:Get a URL and emit the full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.

Version:0.1.1

Key:http-new-requests

View on GitHub

HTTP / Webhook Overview#

Build, test, and send HTTP requests without code using your Pipedream workflows. The HTTP / Webhook action is a tool to build HTTP requests with a Postman-like graphical interface.

Point and click HTTP requests

Define the target URL, HTTP verb, headers, query parameters, and payload body without writing custom code.

$A screenshot of Pipedream's HTTP Request Configuration interface with a GET request type selected. The request URL is set to 'https://api.openai.com/v1/models'. The 'Auth' tab is highlighted, indicating that authentication is required for this request. In the headers section, there are two headers configured: 'User-Agent' is set to 'pipedream/1', and 'Authorization' is set to 'Bearer {{openai_api_key}}', showing how the OpenAI account's API key is dynamically inserted into the headers to handle authentication automatically.$

Here's an example workflow that uses the HTTP / Webhook action to send an authenticated API request to OpenAI.

Focus on integrating, not authenticating

This action can also use your connected accounts with third-party APIs. Selecting an integrated app will automatically update the request’s headers to authenticate with the app properly, and even inject your token dynamically.

Pipedream integrates with thousands of APIs, but if you can’t find a Pipedream integration simply use Environment Variables in your request headers to authenticate with.

Compatible with no code actions or Node.js and Python

The HTTP/Webhook action exports HTTP response data for use in subsequent workflow steps, enabling easy data transformation, further API calls, database storage, and more.

Response data is available for both coded (Node.js, Python) and no-code steps within your workflow.

Trigger Code#

import http from "../../http.app.mjs";

// Core HTTP component
export default {
  key: "http-new-requests",
  name: "New Requests",
  description: "Get a URL and emit the full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.",
  version: "0.1.1",
  type: "source",
  props: {
    httpInterface: {
      type: "$.interface.http",
      customResponse: true,
    },
    emitBodyOnly: {
      type: "boolean",
      label: "Body Only",
      description: "This source emits an event representing the full HTTP request by default. Select `true` to emit the body only.",
      optional: true,
      default: false,
    },
    resStatusCode: {
      type: "string",
      label: "Response Status Code",
      description: "The status code to return in the HTTP response",
      optional: true,
      default: "200",
    },
    resContentType: {
      type: "string",
      label: "Response Content-Type",
      description: "The `Content-Type` of the body returned in the HTTP response",
      optional: true,
      default: "application/json",
    },
    resBody: {
      type: "string",
      label: "Response Body",
      description: "The body to return in the HTTP response",
      optional: true,
      default: "{ \"success\": true }",
    },
    http,
  },
  async run(event) {
    const summary = `${event.method} ${event.path}`;

    this.httpInterface.respond({
      status: this.resStatusCode,
      body: this.resBody,
      headers: {
        "content-type": this.resContentType,
      },
    });

    if (this.emitBodyOnly) {
      this.$emit(event.body, {
        summary,
      });
    } else {
      this.$emit(event, {
        summary,
      });
    }
  },
};

Trigger Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI and CLI.

Label	Prop	Type	Description
N/A	`httpInterface`	`$.interface.http`	This component uses `$.interface.http` to generate a unique URL when the component is first instantiated. Each request to the URL will trigger the `run()` method of the component.
Body Only	`emitBodyOnly`	`boolean`	This source emits an event representing the full HTTP request by default. Select `true` to emit the body only.
Response Status Code	`resStatusCode`	`string`	The status code to return in the HTTP response
Response Content-Type	`resContentType`	`string`	The `Content-Type` of the body returned in the HTTP response
Response Body	`resBody`	`string`	The body to return in the HTTP response
HTTP / Webhook	`http`	`app`	This component uses the HTTP / Webhook app.

Trigger Authentication#

The HTTP / Webhook API does not require authentication.

About HTTP / Webhook#

Get a unique URL where you can send HTTP or webhook requests

Action#

Get Videos on Twitch

Description:Gets video information by video ID, user ID, or game ID

Version:0.1.3

Key:twitch-get-videos

View on GitHub

Twitch Overview#

The Twitch API unlocks a world of possibilities for engaging with live streaming communities and understanding audience behaviors. With Pipedream, you can harness this API to automate many aspects of Twitch interaction and analysis. From tracking stream stats to automating chat messages, the Twitch API lets you create workflows that interact with Twitch's vast live streaming ecosystem. Pipedream's serverless platform streamlines these tasks, making it simple to connect Twitch with other services for enhanced functionalities.

Action Code#

import common from "../common.mjs";

export default {
  ...common,
  name: "Get Videos",
  key: "twitch-get-videos",
  description: "Gets video information by video ID, user ID, or game ID",
  version: "0.1.3",
  annotations: {
    destructiveHint: false,
    openWorldHint: true,
    readOnlyHint: true,
  },
  type: "action",
  props: {
    ...common.props,
    id: {
      type: "string",
      label: "Video ID",
      description: `ID of the video being queried. If this is specified, you cannot use any of the optional query parameters below.
        Each request must specify one video id, one user_id, or one game_id.`,
      optional: true,
    },
    userId: {
      propDefinition: [
        common.props.twitch,
        "user",
      ],
      description: "ID of the user who owns the video. Each request must specify one video id, one user_id, or one game_id",
      optional: true,
    },
    gameId: {
      type: "string",
      label: "Game ID",
      description: "ID of the game the video is of. Each request must specify one video id, one user_id, or one game_id.",
      optional: true,
    },
    language: {
      propDefinition: [
        common.props.twitch,
        "language",
      ],
      description: "Language of the video being queried. A language value must be either the ISO 639-1 two-letter code for a supported stream language or “other”.",
      optional: true,
    },
    period: {
      type: "string",
      label: "Period",
      description: "Period during which the video was created. Defaults to “all” if left blank",
      options: [
        "all",
        "day",
        "week",
        "month",
      ],
      optional: true,
    },
    sort: {
      type: "string",
      label: "Sort",
      description: "Sort order of the videos. Defaults to “time” if left blank",
      options: [
        "time",
        "trending",
        "views",
      ],
      optional: true,
    },
    type: {
      type: "string",
      label: "Type",
      description: "Type of video. Defaults to “all” if left blank",
      options: [
        "all",
        "upload",
        "archive",
        "highlight",
      ],
      optional: true,
    },
    max: {
      propDefinition: [
        common.props.twitch,
        "max",
      ],
      description: "Maximum number of videos to return",
    },
  },
  async run() {
    let params = {
      id: this.id,
      user_id: this.userId,
      game_id: this.gameId,
      language: this.language,
      period: this.period,
      sort: this.sort,
      type: this.type,
    };
    // remove empty values from params
    Object.keys(params).forEach((k) => (params[k] == null || params[k] == "") && delete params[k]);
    const videos = await this.paginate(
      this.twitch.getVideos.bind(this),
      params,
      this.max,
    );
    return await this.getPaginatedResults(videos);
  },
};

Action Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI.

Label	Prop	Type	Description
Twitch	`twitch`	`app`	This component uses the Twitch app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Video ID	`id`	`string`	ID of the video being queried. If this is specified, you cannot use any of the optional query parameters below. Each request must specify one video id, one user_id, or one game_id.
User ID	`userId`	`string`	ID of the user who owns the video. Each request must specify one video id, one user_id, or one game_id
Game ID	`gameId`	`string`	ID of the game the video is of. Each request must specify one video id, one user_id, or one game_id.
Stream Language	`language`	`string`	Language of the video being queried. A language value must be either the ISO 639-1 two-letter code for a supported stream language or “other”.
Period	`period`	`string`	Select a value from the drop down menu:`alldayweekmonth`
Sort	`sort`	`string`	Select a value from the drop down menu:`timetrendingviews`
Type	`type`	`string`	Select a value from the drop down menu:`alluploadarchivehighlight`
Max Items	`max`	`integer`	Maximum number of videos to return

Action Authentication#

Twitch uses OAuth authentication. When you connect your Twitch account, Pipedream will open a popup window where you can sign into Twitch and grant Pipedream permission to connect to your account. Pipedream securely stores and automatically refreshes the OAuth tokens so you can easily authenticate any Twitch API.

Pipedream requests the following authorization scopes when you connect your account:

analytics:read:extensionsanalytics:read:gamesbits:readchannel:read:subscriptionsclips:edituser:edituser:edit:broadcastuser:read:broadcastuser:read:emailuser:read:followsuser:read:blocked_usersuser:manage:blocked_usersmoderator:read:followerschannel:read:editorschannel:manage:videosuser:read:subscriptions

About Twitch#

Twitch is an interactive livestreaming service for content spanning gaming, entertainment, sports, music, and more.

More Ways to Connect Twitch + HTTP / Webhook#

Other Popular Integrations#

Custom Request with HTTP / Webhook API on New Clips from Twitch API

Twitch + HTTP / Webhook