Make a custom HTTP Request to the Github API.

Github API Docs: https://developer.github.com/v3/

Options

  • Request Type (dropdown) - Available HTTP Request Methods. Choose from GET, POST, and DELETE. Refer to API docs in order to determine which request type to use.

    • 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.

    • PATCH: applies partial modifications to a resource on a web server based on your parameters. PATCH is not idempotent, meaning that the result of multiple PATCH’s could have unintended consequences. If a PUT is successful, you will receive a 200 response message (usually 204). 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 .com. in the Github API url. E.g. - If the full API URL is https://api.github.com/issues, then the Relative URL would be /issues.

      Example: /issues
    • Query (object) - Query parmaeters for the request.

      Example: {"state":"open"}
    • Headers (object) - Headers for the request.

      Example: {"Accept":"application/json"}
    • Body (object) (only for POST 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.