### Querying Documentation Dynamically Source: https://docs.dataimpulse.com/proxies/parameters/city This example illustrates how to dynamically query the documentation using an HTTP GET request with the 'ask' query parameter. This is useful for retrieving specific information or clarification not explicitly present on the page. ```http GET https://docs.dataimpulse.com/proxies/parameters/city.md?ask= ``` -------------------------------- ### SOCKS5 Rotating Proxy Example Source: https://docs.dataimpulse.com/proxies/protocols Example of using a rotating SOCKS5 proxy. Replace 'login' and 'password' with your credentials. ```bash curl -x "socks5://login:password@gw.dataimpulse.com:824" https://api.ipify.org/ ``` -------------------------------- ### Query Documentation via HTTP GET Source: https://docs.dataimpulse.com/proxies/connection-hosts Perform an HTTP GET request to query the documentation dynamically. Use the 'ask' query parameter for specific questions. ```http GET https://docs.dataimpulse.com/proxies/connection-hosts.md?ask= ``` -------------------------------- ### SOCKS5 Sticky Proxy Example Source: https://docs.dataimpulse.com/proxies/protocols Connect to a sticky SOCKS5 proxy. Ports from 10000 to 20000 are available for sticky connections. ```bash curl -x "socks5://login:password@gw.dataimpulse.com:10000" https://api.ipify.org/ ``` -------------------------------- ### HTTP Rotating Proxy Example Source: https://docs.dataimpulse.com/proxies/protocols Use this command to connect to a rotating HTTP proxy. Ensure you replace 'login' and 'password' with your actual credentials. ```bash curl -x "http://login:password@gw.dataimpulse.com:823" https://api.ipify.org/ ``` -------------------------------- ### Query Documentation Dynamically Source: https://docs.dataimpulse.com/authentication-methods Use this HTTP GET request to ask questions about the documentation. The response includes direct answers and relevant excerpts. ```http GET https://docs.dataimpulse.com/authentication-methods.md?ask= ``` -------------------------------- ### Query Documentation via HTTP GET Source: https://docs.dataimpulse.com/dashboard/telegram-notifications To get information not explicitly present on a page, make an HTTP GET request to the page URL with an 'ask' query parameter containing your question. ```http GET https://docs.dataimpulse.com/dashboard/telegram-notifications.md?ask= ``` -------------------------------- ### Query Documentation Dynamically Source: https://docs.dataimpulse.com/proxies/udp Use this GET request to ask questions about the documentation. Include your question as the 'ask' query parameter. KYC verification is required for UDP requests. ```http GET https://docs.dataimpulse.com/proxies/udp.md?ask= ``` -------------------------------- ### Querying Documentation Dynamically Source: https://docs.dataimpulse.com/proxies/parameters/asn To get additional information not present on the page, perform an HTTP GET request with the `ask` query parameter. The question should be specific and self-contained. ```http GET https://docs.dataimpulse.com/proxies/parameters/asn.md?ask= ``` -------------------------------- ### Query Documentation Dynamically Source: https://docs.dataimpulse.com/resellers/deposit-calculation-update To get information not directly on the page, make an HTTP GET request to the current URL with an 'ask' query parameter containing your question. ```HTTP GET https://docs.dataimpulse.com/resellers/deposit-calculation-update.md?ask= ``` -------------------------------- ### Query Documentation Dynamically Source: https://docs.dataimpulse.com/affiliate-program Perform an HTTP GET request to query the documentation. Use this when the answer is not explicitly present or for additional context. ```http GET https://docs.dataimpulse.com/affiliate-program.md?ask= ``` -------------------------------- ### Query Documentation Dynamically Source: https://docs.dataimpulse.com/authentication-methods/user-pass-authentication Perform an HTTP GET request on the current page URL with the `ask` query parameter to get specific information not explicitly present in the documentation. The question should be specific, self-contained, and in natural language. ```HTTP GET https://docs.dataimpulse.com/authentication-methods/user-pass-authentication.md?ask= ``` -------------------------------- ### Anonymous Proxy Curl Example Source: https://docs.dataimpulse.com/proxies/parameters/anonymous Use this example to test anonymous proxy access. Ensure you replace placeholder credentials and host with your actual details. ```bash curl -x "http://login__anon.1:password@gw.dataimpulse.com:823" https://api.ipify.org/ ``` -------------------------------- ### HTTP Sticky Proxy Example Source: https://docs.dataimpulse.com/proxies/protocols Connect to a sticky HTTP proxy using the specified port. Sticky connections maintain the same IP for the duration of the session. ```bash curl -x "http://login:password@gw.dataimpulse.com:10000" https://api.ipify.org/ ``` -------------------------------- ### Query Documentation Dynamically Source: https://docs.dataimpulse.com/billing/payment-methods To get additional information not directly present on a page, make an HTTP GET request with the 'ask' query parameter. The question should be specific and in natural language. ```http GET https://docs.dataimpulse.com/billing/payment-methods.md?ask= ``` -------------------------------- ### Query Documentation Dynamically Source: https://docs.dataimpulse.com/proxies/parameters Perform an HTTP GET request with the 'ask' query parameter to retrieve specific information from the documentation. Use this when the answer is not explicitly present or requires clarification. ```http GET https://docs.dataimpulse.com/proxies/parameters.md?ask= ``` -------------------------------- ### Dynamic Documentation Query Source: https://docs.dataimpulse.com/proxies/types-of-connections To get information not directly present on the page, make an HTTP GET request to the page URL with an 'ask' query parameter containing your question. ```http GET https://docs.dataimpulse.com/proxies/types-of-connections.md?ask= ``` -------------------------------- ### Querying Documentation Dynamically Source: https://docs.dataimpulse.com/proxies/parameters/state To get information not directly present on the page, make an HTTP GET request to the page URL with the 'ask' query parameter. The question should be in natural language. ```http GET https://docs.dataimpulse.com/proxies/parameters/state.md?ask= ``` -------------------------------- ### Query Documentation Dynamically Source: https://docs.dataimpulse.com/proxies/threads To get specific information not readily available on the page, make an HTTP GET request to the current page URL with an 'ask' query parameter. The question should be clear and in natural language. ```http GET https://docs.dataimpulse.com/proxies/threads.md?ask= ``` -------------------------------- ### Example cURL Request with Session Interval and Country Source: https://docs.dataimpulse.com/proxies/parameters/session-interval This cURL command demonstrates how to use the 'cr.fr' (France) and 'sessttl.60' (60 minutes) parameters in a sticky proxy configuration. ```shell curl -x "http://login__cr.fr;sessttl.60:password@gw.dataimpulse.com:10000" https://api.ipify.org/ ``` -------------------------------- ### Dynamic Documentation Query Source: https://docs.dataimpulse.com/proxies/parameters/zip You can query this documentation dynamically by performing an HTTP GET request on the page URL with the 'ask' query parameter. This is useful for retrieving specific information or clarification not explicitly present on the page. ```http GET https://docs.dataimpulse.com/proxies/parameters/zip.md?ask= ``` -------------------------------- ### Targeting Germany and Berlin Source: https://docs.dataimpulse.com/proxies/parameters/city This example demonstrates how to use the 'city' parameter to target proxies in Berlin, Germany. A country selection is mandatory when specifying city targeting. ```bash curl -x "http://login__cr.de;city.berlin:password@gw.dataimpulse.com:823" https://api.ipify.org/ ``` -------------------------------- ### Excluding Berlin from Germany Targeting Source: https://docs.dataimpulse.com/proxies/parameters/city This example shows how to use the 'nocity' parameter to exclude proxies from Berlin while still targeting Germany. Traffic routed through 'nocity' is billed at double the standard rate. ```bash cr.de;nocity.berlin ``` -------------------------------- ### Select Multiple Countries for Proxy Request Source: https://docs.dataimpulse.com/proxies/parameters/country To route requests through multiple countries, separate the country codes with commas after the 'cr' parameter. This example selects Germany and Australia. ```bash curl -x "http://login__cr.de,au:password@gw.dataimpulse.com:823" https://api.ipify.org/ ``` -------------------------------- ### Select Single Country for Proxy Request Source: https://docs.dataimpulse.com/proxies/parameters/country Use the 'cr' parameter followed by the country code (e.g., 'de' for Germany) to route your request through a specific country. This example demonstrates selecting Germany. ```bash curl -x "http://login__cr.de:password@gw.dataimpulse.com:823" https://api.ipify.org/ ``` -------------------------------- ### Query Documentation Dynamically Source: https://docs.dataimpulse.com/proxies/targeting/target-filters Use this method to ask questions about the documentation. The response includes direct answers and relevant excerpts. ```HTTP GET https://docs.dataimpulse.com/proxies/targeting/target-filters.md?ask= ``` -------------------------------- ### Querying Documentation Dynamically Source: https://docs.dataimpulse.com/proxies/parameters/anonymous This method allows you to ask questions about the documentation and receive direct answers. The question should be specific and self-contained. ```http GET https://docs.dataimpulse.com/proxies/parameters/anonymous.md?ask= ``` -------------------------------- ### Set Session Interval to 60 Minutes Source: https://docs.dataimpulse.com/proxies/parameters/session-interval Use 'sessttl.60' to set the IP rotation interval to 60 minutes (1 hour) for sticky proxies. ```text sessttl.60 ``` -------------------------------- ### Connect using DNS Hostname Source: https://docs.dataimpulse.com/proxies/connection-hosts Use the DNS hostname for automatic routing to the closest host. Recommended for stability. ```text gw.dataimpulse.com ``` -------------------------------- ### Connect using IP Hostname Source: https://docs.dataimpulse.com/proxies/connection-hosts Connect using the IP address for routing through the best available server based on your selected country. ```text 74.81.81.81 ``` -------------------------------- ### Set Session Interval to 1 Minute Source: https://docs.dataimpulse.com/proxies/parameters/session-interval Use 'sessttl.1' to set the IP rotation interval to 1 minute for sticky proxies. ```text sessttl.1 ``` -------------------------------- ### Set Country and Session Interval Source: https://docs.dataimpulse.com/proxies/parameters/session-interval Combine country code 'cr.fr' (France) with session interval 'sessttl.60' (60 minutes) for sticky proxies. ```text cr.fr;sessttl.60 ``` -------------------------------- ### Connect to a Specific IP Address with Session ID Source: https://docs.dataimpulse.com/proxies/parameters/session-id Use the 'sessid' parameter in the proxy username to connect to a specific IP address for approximately 30 minutes. The value following 'sessid.' identifies the target IP. ```curl curl -x "http://login__cr.au;sessid.123:password@gw.dataimpulse.com:823" https://api.ipify.org/ ``` ```curl curl -x "http://login__cr.au;sessid.45:password@gw.dataimpulse.com:823" https://api.ipify.org/ ``` -------------------------------- ### Targeting a Specific ZIP Code Source: https://docs.dataimpulse.com/proxies/parameters/zip Use the 'zip' parameter with a five-digit ZIP code in the username, combined with the 'cr' country code parameter, to target a specific geographic location. ```curl curl -x "http://login__cr.us;zip.10001:password@gw.dataimpulse.com:823" https://api.ipify.org/ ``` -------------------------------- ### Targeting Proxies by ASN and Country Source: https://docs.dataimpulse.com/proxies/parameters/asn Use the `asn` parameter combined with the `cr` country code parameter to select proxies from specific carriers. Targeting a country is mandatory when specifying city, state, ZIP code, or ASN. ```text cr.pl;asn.39603 ``` ```bash curl -x "http://login__cr.pl;asn.39603:password@gw.dataimpulse.com:823" https://api.ipify.org/ ``` -------------------------------- ### Excluding a Specific ZIP Code Source: https://docs.dataimpulse.com/proxies/parameters/zip Use the 'nozip' parameter to exclude specific ZIP codes from your proxy targeting. This is useful for targeting a broader region while avoiding certain areas within it. ```text cr.de;nozip.10115 ``` -------------------------------- ### Targeting a Specific US State Source: https://docs.dataimpulse.com/proxies/parameters/state Use this format to route traffic through a proxy located in a specific US state. Ensure the state name is correctly appended after 'state.'. ```bash curl -x "http://login__cr.us;state.arizona:password@gw.dataimpulse.com:823" https://api.ipify.org/ ``` -------------------------------- ### Excluding a Specific US State Source: https://docs.dataimpulse.com/proxies/parameters/state Use this format to route traffic through US proxies while excluding a particular state. The state name is appended after 'nostate.'. ```bash cr.us;nostate.california ``` -------------------------------- ### Exclude Germany from Proxy Requests Source: https://docs.dataimpulse.com/proxies/parameters/exclude-country Use this curl command to exclude Germany from your proxy requests when 'All Countries' is selected. Replace 'login__nocr.de' with your actual login and 'password' with your password. ```bash curl -x "http://login__nocr.de:password@gw.dataimpulse.com:823" https://api.ipify.org/ ``` -------------------------------- ### Exclude Specific ASN from Proxy IPs Source: https://docs.dataimpulse.com/proxies/parameters/exclude-asn Use the 'noasn' parameter in the proxy hostname to exclude IPs from a particular ASN. This is useful for targeting specific network ranges. ```bash curl -x "http://login__noasn.as20947:password@gw.dataimpulse.com:823" https://api.ipify.org/ ``` === COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.