Title here
Summary here
Send Network Request
Send a HTTPS request to a URL.
Network Requests require coding skills and falls outside the scope of our support.
This means we’re unable to help further with setup or troubleshooting. Additionally, with a code-based solution, we can’t guarantee its functionality or full compatibility with Inventor. This includes how it functions with our responsive design or future platform updates.
Some websites are currently not supported. Requests are logged for 14 days to prevent abuse.
Inputs
URL
URL to send the request to.
This is the URL that Inventor will send your network request to. This is usually an API endpoint, like https://discord.com/api/users/@me. Consult the documentation of the API you are using for the URL.
Requests to Inventor webhooks are currently not supported. Make sure that the URL is correct and uses HTTPS. Inventor does not support HTTP requests.
Example: https://api.inventor.gg/test
Method
HTTP method to use when sending the request.
This is the HTTP method that Inventor will use when sending your network request. Methods typically represent the type of data exchange that the request causes. For example, the most common methods are GET and POST (for GETting/retrieving data and POSTing/sending data), although other methods are used for other purposes. Consult the documentation of the API you are using for the request method.
Using the wrong method will usually cause the request to fail or return an error.
Example: GET
Content Type
Provide a value like application/json, application/x-www-form-urlencoded, etc.
This is the content type that Inventor will use when sending your network request. The content type is a header that tells the server what type of data is being sent in the request body. For example, if you are sending JSON data, you would use application/json. Consult the documentation of the API you are using for the content type.
Most APIs will accept either application/json or application/x-www-form-urlencoded as the content type, for a JSON object body or form-encoded body respectively.
Example: application/json
Body
Raw request body to send.
This is the raw request body that Inventor will send with your network request. The request body is the data that is sent to the server in the request. The body is usually only used for POST, PUT, and PATCH requests, where data is sent to the server. Consult the documentation of the API you are using for the correct format of the request body.
Example: {"key": "value"}
Headers
Header=Value pairs separated by newlines.
This is the headers that Inventor will send with your network request. Headers are key-value pairs that are sent to the server in the request. Headers are used to send additional information to the server, such as authentication tokens, content types, and more. Consult the documentation of the API you are using to see if any headers are needed.
All requests include a header indicating an Inventor bot as the source of the request (no details about your bot are provided, only a randomized request ID). Requests to Discord will automatically include a customized User-Agent header. These headers cannot be overridden.
Example: Authorization=Bearer KEY
Cookies
Cookie=Value pairs separated by newlines.
This is the cookies that Inventor will send with your network request. Cookies are key-value pairs that are sent to the server in the request. Cookies are used to store information on the client side, such as session tokens, authentication tokens, and more. Cookies are typically not used for APIs (as headers are generally preferred), but some APIs may require cookies.
Example: Cookie=Value
Outputs
Status Code
The status code the status of your request. For example, 200 means the request was successfull, and 403 means you aren’t allowed execute that action, most likely because you didn’t authorize the request properly.
Example: 200
Response Body
The data the server returned.
If the data type is JSON, you can retrieve the values by using the Parse JSON block.
Example: {"key": "value"}
Headers
The headers the server returned. Can be used for additional information about the server.
Example: User-Agent=Server
Cookies
The cookies the server returned.
Example: Cookie=Value
Prev
Int to Hex