HTTP

10 min

HTTP is the fundamental component of data transfer for the World Wide Web.

With the HTTP app in Make, you can connect to API services and applications that don't have an integration with Make.

HTTP Version 4 is a new version of the HTTP app that simplifies the setup, ensures more secure keychain storage, and provides native pagination.

If you're still using the HTTP (legacy) app, choose Version 3 from the drop-down.

HTTP modules

You can use the following modules to build your scenarios:

Make a request

Download a fileDownload a file

Resolve URLResolve URL

Both modules support authenticated and unauthenticated requests.

When authentication is required, choose one of the following methods as required by the target service's API documentation:

Basic Auth

API key

OAuth 2.0

For security reasons, define the authentication details in the dedicated Credentials field rather than passing them through headers or query parameters. This approach provides the following benefits:

Prevents exposure of keys in your requests

Centralizes control over authentication credentials

Allows easy and safe key rotation

Make a request

Makes an HTTP request to any server.

Standard module settings

Read below how to configure the standard module settings.

Field	Description
Authentication type	Select the authentication type: No authentication: Use when no credentials are required for the request (e.g., web scraping). API key: Use when the service provider requires an API key (token). Basic Auth: Use when the service provider requires a username and a password. OAuth 2.0: Use when the service provider requires client credentials (Client ID and Client Secret)
Credentials	Add the required credentials based on the selected authentication type: Create a keychain for the API key authentication type Create a keychain for the Basic Auth authentication type Create a connection for the OAuth 2.0 authentication type
URL	Enter the URL of an API endpoint (including the base URL), webhook, or webpage, beginning with https://. For example: https://api.example-service.com/v1/users https://your-company.com/webhooks/listener https://www.global-news.com/ Make allows only secure HTTPS. Connections that are using unverified (self-signed) certificates are rejected.
Method	Select the HTTP method you want to use: GET: to retrieve information for an entry. HEAD: to retrieve the status line and headers, without the response body. POST: to create a new entry. PUT: to update/replace an existing entry. PATCH: to make a partial entry update. DELETE: to delete an entry. OPTIONS: to request information about the operations available for the specified resource or server.
Headers	Add headers to provide additional metadata or instructions for the request. For example, User-Agent to identify the client, Cache-Control for caching instructions, etc. You don't need to use this field to define the authentication credentials and content type, as there are specific module fields for that (i.e., Credentials and Content type).
Query parameters	Enter the query key-value pairs to specify or customize your request. This is mostly relevant for GET and DELETE methods. For example, you can specify which contacts or files you want to retrieve or delete. You can find the query parameters in the service's API documentation.
Body content type	HTTP body contains the data transferred in an HTTP request. Select the body content type: application/JSON: Enter data in a JSON format. You can enter data as a JSON string or use a Data structure. multipart/form-data (supports file uploads): Enter files and form data as key-value pairs. You can use this body content type to send files in the HTTP request, and you can also add text fields to the request. application/x-www-form-urlencoded: Enter form fields as key-value pairs encoded in the URL style. With this body content type, the body of the HTTP request sent to the server is one query string. Custom: enter data using a custom content type, e.g., text/plain.
Body input method (for JSON Body content type)	Select the input method: Data structure: define the JSON body with a data structure to map or enter values for each key. JSON reserved characters placed within values will be escaped automatically. This helps to avoid errors related to invalid JSON. JSON string: enter the JSON body as a raw text string. If values contain JSON reserved values, you must escape them manually.
Body content (for other Body content types)	If you selected multipart/form-data (supports file uploads) Body content type: Text: enter data as key-value pairs. File: map the file you want to upload from the previous module, or enter the file name and file data manually. If you selected application/x-www-form-urlencoded body content type: Enter data as key-value pairs encoded in the URL style. The keys and values will be encoded in key-value pairs separated by & and with a = between the key and the value. Example of the resulting HTTP request format: field1=value1&field2=value2 If you selected Custom body content type, enter the body content based on the selected Content type value.
Content type value (for Custom Body content type)	Specify the content type value, e.g., XML, HTML.
Parse response	Select Yes to structure the output data so that it’s easy to map. All mappable items will be available after you run the module once.
Pagination lets you retrieve large data sets in smaller, more manageable parts. Refer to the service's API documentation to see if they allow pagination and which type, and what's needed to configure it. This information is usually provided in the description of a particular endpoint.
Pagination type	If you need to make a paginated HTTP request, select the type of pagination; otherwise, leave the field empty. Available pagination types in Make: Offset-based: you need to use two parameters: offset and limit. The offset is the starting point or position in the dataset. The limit is the maximum number of records that should be included on each page, e.g., ?offset=10&limit=10 Page-based: you need to define which page to retrieve, using the value of the current page number plus 1, and sometimes the page limit, e.g., ?page=3&limit=20 URL or link-based: the server provides the specific, pre-built URL to define the next page. Token or cursor-based: you define the last item ID in the current page or map the next page's starting point (depends on the API implementation), e.g., ?cursor=zwJkYXI3MX0
Pagination response configuration
Items path	Enter the path to the array of items. For example, results or result.users.
Next page URL/link path (for URL or link-based pagination)	Enter the path to the full URL for the next page. For example, links.next or meta.next_page_url.
Next page token/cursor path (for Token or cursor-based pagination)	Enter the path to the token or cursor value for the next page. For example, next_cursor or meta.next.
Pagination request configuration
Offset parameter name (for Offset-based pagination)	Enter the query parameter name that defines the number of items to skip. For example, offset or skip.
Initial offset value (for Offset-based pagination)	Enter the number to start the request at. This is typically 0 or 1. You can also use this field to return items beyond Make’s 3200 limit.
Page parameter name (for Page-based pagination)	Enter the query parameter name that defines the page number. For example, page or page_number.
Initial page value (for Page-based pagination	Enter the page number to start the request at. This is typically 0 or 1. You can also use this field to return items beyond Make’s 3200 limit.
Page token/cursor parameter name (for Token or cursor-based pagination)	Enter the query parameter name that defines the last item in the current page or the next page’s starting point. For example, pageToken or cursor.
Initial page token value (for Token or cursor-based pagination)	This is typically used when working with items beyond Make’s 3200 limit.
Page size parameter name	Enter the query parameter name that defines the page size. For example, limit or per_page.
Page size parameter value	Enter the maximum number of items to retrieve per page.
Output format	Select the output format: Array of items Array of pages
Limit	Enter the maximum number of items to return. Must be a number between 1 and 10000.

Advanced settings

Read below how to configure advanced settings.

Field	Description
Transport layer security (TLS)	Select the TLS handshake method if required by the API's security settings: Mutual TLS: Both the client and server authenticate each other using certificates. Requires uploading a CA certificate and a Client identity certificate. TLS: Only the server is required to present a certificate for its authentication
CA certificate	Click Create a keychain and add a CA certificate.
Client identity (for Mutual TLS)	Choose a key or click Add to add a Certificate and a Private Key.
Proxy	Click Create a keychain if your network requires routing requests through an intermediary server. In the pop-up window, configure the following fields: Host: Enter the domain name or IP address of the proxy server. Port: Enter the port number used by the proxy server. Must be between 1 and 65535. Username: Enter the login name if the proxy requires authentication. Password: Enter the password for the proxy user
Return error if HTTP request fails	Select Yes if you want the scenario to stop if the request returns a 4xx or 5xx error.
Timeout	Enter the maximum time to wait for the response, in seconds. Must be a number between 1 and 300.
Allow redirects	Select Yes to automatically follow HTTP redirection responses, with a maximum of 10. Expand this section to see how the redirection works.
Share cookies with other HTTP modules	Select Yes to enable the sharing of cookies with other HTTP modules.
Request compressed content	Select Yes to request compression of the response data. Adds the Accept-Encoding header.

Download a file

Downloads a file from a specified URL.

Standard module settings

Read below how to configure the standard module settings.

Field	Description
Authentication type	Select the authentication type: No authentication: Use when no credentials are required for the request (e.g., web scraping). API key: Use when the service provider requires an API key (token). Basic Auth: Use when the service provider requires a username and a password. OAuth 2.0: Use when the service provider requires client credentials (Client ID and Client Secret)
Credentials	Add the required credentials based on the selected authentication type: Create a keychain for the API key authentication type Create a keychain for the Basic Auth authentication type Create a connection for the OAuth 2.0 authentication type
URL	Enter the URL of the file you want to download. You can use the file (map the file data) in other modules in the scenario. Make only allows secure HTTPS. Connections that are using unverified (self-signed) certificates are rejected.

Advanced settings

Read below how to configure advanced settings.

Field	Description
Return error if HTTP request fails	Select Yes if you want the scenario to stop if the request returns a 4xx or 5xx error.
Share cookies with other HTTP modules	Select Yes to enable the sharing of cookies with other HTTP modules.
Headers	Add headers to provide additional metadata or instructions for the request. For example, User-Agent to identify the client, Cache-Control for caching instructions, etc.
Query parameters	Enter the query key-value pairs to specify or customize your request. For example, you can specify the file name, file ID, or format. You can find the query parameters in the service's API documentation.

Resolve URL

Follows all redirects and returns the final resolved URL.

Standard module settings

Field	Description
URL	Enter the URL of an API endpoint (including the base URL), webhook, or webpage, beginning with https://.

Advanced module settings

Field	Description
Method	Select the HTTP method you want to use: HEAD: to retrieve the headers without the body. This method is faster, but it might not be supported by some servers. GET: to retrieve the body data.

HTTP

HTTP modules

Make a request

Standard module settings

Pagination

Advanced settings

Redirection in HTTP requests

Download a file

Standard module settings

Advanced settings

Resolve URL

Standard module settings

Advanced module settings