Документация API для получения прокси

body.site-preloading { overflow: auto; } body.site-preloading .page-fade-shell1 { opacity: 1; transform: none; } body.site-preloading .site-loader-overlay { display: none; }

API Documentation for Retrieving Proxies

Description

This API provides access to a list of proxy servers with customizable filters. Working with the API requires a valid access key, which is verified for authenticity and compliance with usage limits. In response to a request, the user receives data depending on the get parameter in the form of text, JSON, or a downloadable file. The API is available at https://api.good-proxies.ru/api.

Main Request Parameters

Parameter	Description	Required	Example Value
key	Access key required for request authentication.	Yes	abc123
type	Type of proxy servers (http, https, socks4, socks5). Multiple types can be specified separated by commas.	No	http,https
anon	Proxy anonymity level (transparent, anonymous, elite).	No	elite
ping	Maximum allowed proxy response time in milliseconds.	No	500
time	Maximum time (in seconds) since the last proxy check. Default: `600` (last 10 minutes).	No	600
works	Percentage of successful proxy tests out of total attempts. Available values: from 0 to 100. Example usage: `works=50` - this means that proxies with at least 50% successful checks out of the total number of tests will be returned. The value is displayed if the `json` format is selected.	No	50
country	Proxy country code (ISO Alpha-2). Multiple codes can be specified separated by commas.	No	us,ca
city	Proxy city name. Multiple cities can be specified separated by commas. Names can be in Russian or English.	No	Paris,Moscow
count	Number of proxies requested.	No	10
lang	Language for city names in the response and when filtering by city. `ru` (default) - Russian city names. `en` - English city names. With `lang=en` the `city` parameter accepts English city names.	No	ru, en
get	Data output format. By default, `txt` is used, which means output as text in the browser. For JSON format output use `get=json`. To download a file use `get=txt.file` or `get=json.file`.	No	txt, json, txt.file, json.file
timecheck	Time of the last successful proxy functionality check. Displayed only if `json` format is selected. Time is indicated in GMT+2 timezone.	No	Cannot be specified
ip_out	Outgoing resulting proxy IP address. May differ from the main proxy IP address. This parameter is displayed only in JSON format.	No	Cannot be specified

TXT Format Parameters

The following parameter controls the line format for get=txt and get=txt.file.

Parameter	Description	Required	Example Value
type_prefix	Adds the protocol prefix to each TXT output line: `type://ip:port`. Value `1` enables the mode. Example line: `http://127.0.0.1:3128`.	No	1

JSON Format Parameters

The following parameters control the response structure for get=json and get=json.file. They do not affect TXT output.

Parameter	Description	Required	Example Value
ip	Proxy server address in `ip:port` format (e.g. `192.168.1.1:8080`). To split into separate `ip` and `port` fields, use the `split_ip=1` parameter.	No	192.168.1.1:8080
fields	Comma-separated list of fields to include in the JSON response. Allowed: `ip, port, ip_out, type, anon, ping, timecheck, country, city, works`. By default all fields are returned. The `port` field only appears with `split_ip=1`.	No	ip,type,country
split_ip	Splits the `ip` field in `ip:port` format into two separate fields: `ip` and `port`. Value `1` enables splitting.	No	1
format	JSON response structure. `array` (default) - array of proxy objects. `object` - object where keys are proxy addresses (`ip:port`) and values are field objects.	No	array, object
wrap	Wraps the response in a metadata envelope: `{status, count, timestamp, filters, data}`. Value `1` enables wrapping.	No	1
pretty	JSON response formatting. `1` (default) - human-readable format with indentation. `0` - compact JSON without indentation (less traffic).	No	0, 1

Request Examples

Example 1: 5 proxies with HTTP type and "elite" anonymity in JSON format

GET https://api.good-proxies.ru/api?key=abc123&type=http&anon=elite&count=5&get=json

Example 2: 10 proxies with HTTPS type and maximum ping 500 ms in TXT file format for download

GET https://api.good-proxies.ru/api?key=abc123&type=https&ping=500&count=10&get=txt.file

Example 3: 2 proxies from USA and Canada in list format (displayed as text in browser)

GET https://api.good-proxies.ru/api?key=abc123&country=us,ca&count=2

Example 4: TXT with protocol prefix type://ip:port

GET https://api.good-proxies.ru/api?key=abc123&type=http&count=5&type_prefix=1

Output:

http://192.168.1.1:8080
http://192.168.1.2:3128
http://192.168.1.3:8118

Example 5: JSON - selected fields only, IP and port split

GET https://api.good-proxies.ru/api?key=abc123&type=socks5&count=2&get=json&fields=ip,port,type,country&split_ip=1

Output:

[
    {
        "ip": "192.168.1.1",
        "port": "1080",
        "type": "socks5",
        "country": "US"
    },
    {
        "ip": "192.168.1.2",
        "port": "1080",
        "type": "socks5",
        "country": "DE"
    }
]

Example 6: JSON with metadata envelope (wrap=1)

GET https://api.good-proxies.ru/api?key=abc123&type=http&count=2&get=json&wrap=1

Output:

{
    "status": "ok",
    "count": 2,
    "timestamp": "2026-03-01T12:00:00+00:00",
    "filters": {
        "type": "http",
        "time": 600
    },
    "data": [
        {
            "ip": "192.168.1.1:8080",
            "type": "http",
            ...
        }
    ]
}

Example 7: Filter by city in English

GET https://api.good-proxies.ru/api?key=abc123&city=Paris,London&count=5&get=json&lang=en

The lang=en parameter allows specifying cities in English and receiving English city names in the response.

Example 8: Compact JSON without indentation (for automated processing)

GET https://api.good-proxies.ru/api?key=abc123&type=http&count=10&get=json&pretty=0

Response Format

Successful JSON Response

Upon a successful request with the get=json parameter, the API returns a list of proxy servers in structured JSON format. Includes the timecheck parameter, which shows the time of the last successful check in GMT+2 timezone. The ip_out parameter indicates the resulting proxy IP address, which may differ from the main one.

[
    {
        "ip": "15.162.126.1:919",
        "ip_out": "15.162.126.1:919",
        "type": "http",
        "anon": "transparent",
        "ping": 5.07786,
        "timecheck": "2024-11-25 20:09:25",
        "country": "CO",
        "city": "Медельин",
        "works": "66"
    }
]

Successful TXT Response

If the parameter get=txt (default), data is returned as a plain text file displayed in the browser:

192.168.1.1:8080
192.168.1.2:8080
192.168.1.3:8080

Successful TXT Response for Download

If the parameter get=txt.file, data will be offered for download in text format:

192.168.1.1:8080
192.168.1.2:8080
192.168.1.3:8080

Successful JSON Response for Download

If the parameter get=json.file, data will be offered for download in JSON format:

[
    {
        "ip": "112.63.11.8:180",
        "ip_out": "122.63.41.1:380",
        "type": "http",
        "anon": "elite",
        "ping": 3.83659,
        "timecheck": "2024-11-25 20:09:26",
        "country": "SN",
        "city": "",
        "works": "100"
    }
]

Errors

If the request fails, the API returns a text message describing the error.

Error: Access key not provided

Limits

Request frequency: no more than two requests every 5 seconds.
Daily request limit: up to 34,560 requests. When the limit is exceeded, the API returns an error message.
Subnet restriction: no more than 10 IP subnets in "a.b.0.0/16" format. The limit resets every 24 hours. If the limit is exceeded, the API returns an error.

Notes

All parameters except key are optional.
If the count parameter is not specified, the API returns the maximum number of available proxies.
If the time parameter is not specified, the default value 600 is used (proxies checked within the last 10 minutes).
When using the parameter get=txt.file or get=json.file, data will be offered for download as a file.
The time in the timecheck field, returned in JSON format, is specified in GMT+2 timezone.
JSON parameters (fields, split_ip, format, wrap, pretty) only affect JSON responses and are ignored for TXT output.
The type_prefix parameter only affects TXT output (get=txt and get=txt.file) and is ignored for JSON output.
The lang=en parameter allows specifying city names in the city filter in English and returns them in English in the JSON response.

PHP Usage Example

$key = 'abc123';
$type = 'http';
$anon = 'elite';
$count = 5;
$get = 'json';

$url = "https://api.good-proxies.ru/api?key=$key&type=$type&anon=$anon&count=$count&get=$get";

$response = file_get_contents($url);

if ($response) {
    $proxies = json_decode($response, true);
    print_r($proxies);
} else {
    echo "Error retrieving proxies.";
}

Conclusion

The API provides a convenient tool for retrieving proxy servers with extensive filtering capabilities. Make sure you have a valid access key and observe the limits for uninterrupted service operation.

Условия использования

Good-proxies.ru Terms of Use

Terms and definitions
Service description
Getting started
System workflow and proxy sources
API description
Proxy types
Rules for using this Resource
Privacy policy
Other terms
Changes to the terms of use
Rights of the administration
Refunds
Feedback

Last updated: November 19, 2024.

Before using the Good-proxies.ru web service (hereinafter - the "Resource"), carefully read these Terms. Your use of the service automatically signifies your full agreement with every provision herein. If you disagree with any clause of these Terms, you are forbidden from using the Resource.

Access keys are sold through an external platform located at digiseller.ru. Technical support email for payment gateway issues: [email protected].

Premium access keys can be purchased through the WebMoney electronic payment system at webmoney.ru. Technical support for this payment system: webmoney.ru/rus/support/index.shtml.

Premium access keys are also sold via the cardlink.link payment system at cardlink.link. Technical support email: [email protected].

Terms and definitions

User - an individual who accesses the Resource.

The Resource - the web service located at https://good-proxies.ru.

Cookie - a small data file sent by the web server to your computer. It is used to identify the user, store preferences, collect statistics, and track the session.

Premium access key - a key sent to the user's email immediately after payment. By entering this key, which consists of digits and Latin letters, the user receives access to the Resource.

Service description

The Resource provides users with an information service - access to a list of open IPv4 proxy servers that do not require authorization and are neither owned nor controlled by the Resource. All open IPv4 proxy servers are collected from publicly available Internet sources and are checked and classified with the Resource's software. The service is provided for a fee for personal use at your own risk, on an "as is" and "as available" basis.

Proxy servers are updated continuously. A full check of the entire proxy list takes no longer than 5–10 minutes. The timeout for checking each proxy server is 8 seconds.

To gain full access to the Resource, a user must purchase a Premium access key. The key grants full access for 7, 30, 60, or 180 days. To activate the key, you must log in through the Resource interface. Once activated, the key cannot be paused. The key can be activated within 10 months from the purchase date; after that period, it becomes invalid. Payments for expired keys are non-refundable.

Getting started

To access the API, you must authorize once in the web interface. Within one minute you will receive API access.

The proxy list service is paid. Pricing is available on the home page. After purchasing a key, you will gain entry to the paid section where you can constantly view proxy lists. Log in by entering the key in the top-right corner of the page. Each key has a validity period (from 7 to 180 days). During that time you can use the Resource without unreasonable limits (up to 34,560 requests to the proxy list per day). If you exceed this limit, the key will be blocked until the end of the current server day. You may request proxy lists via the API no more than twice within five seconds (API endpoint: https://api.good-proxies.ru/api). You may retrieve proxy lists from only ten different IP subnets per day in the "a.b.0.0/16" format (for example, 123.123.*.* where "*" can be any number between 0 and 255).

The validity period of the key starts from the moment you log in on the main page with the key or after the first API request. Once the key expires, access to proxy lists is revoked.

To receive proxy lists, you must purchase a Premium access key. Purchase links are available on the home page. Payments are processed through digiseller.market. After buying and receiving the key, log into your account. The account always shows how much time remains before the key expires. Trial keys may have different parameters.

System workflow and proxy sources on this website

The system runs two proxy-harvesting robots that collect and check thousands of public web resources each day to find working proxies. Every proxy quickly undergoes tests for connection speed, country, anonymity level, proxy type, and the ability to pass POST requests, REFERER, and COOKIE. Two test pages sized 961 bytes and 800–1200 bytes are used for verification. All proxies that pass the checks are immediately added to the site's database. The database is updated continuously. Non-working proxies are not added because it is inefficient. Working proxies are automatically re-tested in queue. When a proxy stops working it is automatically removed. This algorithm keeps proxy lists up to date.

The maximum response time for HTTP/S checks is 8 seconds, and up to 8 seconds for SOCKS4/5.

API description

Proxy check timeout - 8 seconds.

You may send up to 2 requests within 5 seconds.

The API returns a proxy list sorted by the ascending date of the last check. The freshest proxies appear at the top of the list.

The API endpoint is https://api.good-proxies.ru/api. Both HTTP and HTTPS requests are supported.

Limit: 34,560 API requests per day and no more than ten IP subnets in the "a.b.0.0/16" format (for example, 123.123.*.* where "*" can be any number from 0 to 255).

Parameter descriptions

key - Premium access key. This parameter is required. Example: key=ACCESS_KEY.

type - Proxy type. Available values: http, https, socks4, socks5. If omitted, proxies of all types are returned. Example: type=http.

anon - Proxy anonymity level. Available values: transparent, anonymous, elite. If omitted, proxies of all anonymity levels are returned. Example: anon=elite.

count - Number of proxies to retrieve. Sets the maximum number of proxies. If you set 0 or leave it empty, the entire available list is returned. Example: count=0.

ping - Proxy response time in milliseconds. Maximum value: 8000. Example: ping=8000.

works - Percentage of successful proxy tests out of total attempts. Allowed values: 0 to 100. Example: works=50 returns proxies with at least 50% successful checks.

time - Returns proxies tested within the specified number of seconds. Example: time=10 returns proxies checked within the last 10 seconds.

country - Country codes for the proxies. Provide a two-letter country code. Example: country=ru.

city - Cities for the proxies. Provide the full city name in Russian; for some locations an English name may be used. Example: city=Париж.

A more detailed API description is available at https://good-proxies.ru/api-docs.

Proxy types

- SOCKS4/SOCKS5 proxies can be used for any TCP/IP connections: HTTP, HTTPS, FTP, and others. These proxies work in browsers, download managers, FTP clients, instant messengers, and other applications. SOCKS typically provides an elite level of anonymity, sometimes anonymous.

- SSL proxies never pass through your IP address; they forward requests as-is, providing an elite level of anonymity.

- For SSL/HTTP proxies the anonymity level is determined by the lowest level. If an SSL connection offers elite anonymity but HTTP is transparent, the overall anonymity level is considered transparent.

- HTTP, SSL/HTTP, SSL proxies are mainly used for browsing websites (HTTP and/or HTTPS).

Rules for using this Resource

1. It is prohibited for multiple people to use the same Premium access key.

2. Using proxies for illegal purposes that violate the laws of the Russian Federation or other countries is prohibited.

3. Collecting proxies from this Resource for further distribution on the Internet is forbidden.

4. The administration does not guarantee and cannot guarantee that every proxy will be operational at the time it is provided.

5. The administration is not responsible for any damage you may incur as a result of using the Resource.

6. The administration is not liable for any financial losses caused by a person using a Premium access key to obtain proxy lists, nor in the event of unforeseen force majeure or the Resource's bankruptcy. The administration is not obligated to compensate such losses.

7. The administration may amend these rules at any time without notice. Changes take effect immediately upon publication.

8. The administration is not and cannot be responsible for the actions of the Resource's users.

9. The administration is not responsible for incorrect country determination for certain proxies because the geolocation database may become outdated and updates may appear unpredictably.

10. The administration cannot guarantee that the proxies will meet your needs.

11. Users access proxy lists at their own risk and responsibility under the "as is" and "as available" conditions.

12. The administration does not guarantee that the provided proxies do not log traffic.

13. The administration bears no responsibility for any use of the proxies provided by the Resource.

14. Users agree to use the provided proxies for personal purposes only and accept all risks and liability arising from such use.

15. Reselling keys obtained from the Resource is prohibited.

16. If there is any suspicion that a key is used by more than one person, the key will be blocked until the situation is clarified.

17. The administration cannot guarantee high proxy speed.

18. The administration cannot guarantee that proxies are not banned on any websites.

19. The administration cannot guarantee proxy availability to specific websites.

20. Using the Resource through proxy servers, VPN servers, or remote desktops is prohibited.

21. The administration cannot guarantee any specific ping (response time) to the proxies.

22. Users must keep their key confidential.

23. The cost of a Premium key may exceed the stated price by the amount of the payment system's commission, depending on the payment method.

24. Using the Resource's proxies in ways that violate the terms of the websites accessed via those proxies is prohibited.

25. The Resource is provided for user convenience on an "as is" and "as available" basis. The administration does not guarantee uninterrupted, complete, or error-free operation and may change the Resource or discontinue access at any time.

26. Proxy lists obtained from the Resource must not be checked on public websites.

27. Any abuse involving proxies, including boosting counters, votes, or site rankings, is forbidden.

28. Using Resource proxies for spam or other unlawful mass messaging (forums, guestbooks, blogs, social networks, classifieds, or mass registrations) is prohibited.

29. Most proxies may be slow, though faster ones are occasionally available.

30. If one access key is blocked for violating these Terms, all other keys (old or new) belonging to the same user may also be blocked for repeated violations.

31. You may not use the Resource if any clause of these Terms violates the laws of the country from which you access the site.

32. The administration reserves the right to provide proxy lists containing partially or fully non-working proxies to users suspected of violating these Terms.

33. Simultaneous use of a Premium key on more than one computer is prohibited.

34. The administration does not and cannot guarantee that every proxy obtained from the Resource will be operational.

35. Any information about the number of proxies on the Resource may be inaccurate.

36. Accessing the Resource requires a browser with JavaScript and cookies enabled, and browser extensions that restrict the Resource must be disabled. Otherwise the Resource's functionality is not guaranteed.

37. All discovered public IPv4 proxies do not require authorization by IP or login.

38. If the administration determines that too many requests originate from an IP address, that IP may be blocked.

39. Users must keep their Premium key confidential (including API links that contain the key) as well as the proxy lists obtained from the Resource.

40. Under no circumstances shall the administration or any parties involved in creating, producing, or distributing the Resource be liable for direct, indirect, incidental, special, consequential, or exemplary damages, lost profits, or business interruptions resulting from the use or inability to use the Resource or its materials, even if the administration has been advised of the possibility of such damages.

41. An unused Premium key may be applied to extend another Premium key if the extended key has not expired. A Premium key used for extension cannot be used to log into the interface or make API requests.

42. Using proxies to bypass security systems or website blocks is prohibited.

43. Using the Resource to bypass authentication on paid or restricted services without the owners' permission is prohibited.

44. Users agree not to use obtained proxies for unauthorized testing, including but not limited to load testing, infrastructure attacks, or abusing web systems.

45. The administration may request additional information from a user to confirm the legality of their actions and proxy usage if violations are suspected.

46. Users agree not to use the Resource to bypass access restrictions on pages that require acceptance of user agreements or privacy policies.

47. The administration reserves the right to block access to the site or services for users whose actions may damage the server infrastructure or disrupt other users.

48. All proxy lists obtained from the Resource are for personal use only. Transferring or distributing them to third parties without administrative approval is prohibited.

49. Using proxies obtained from the Resource to circumvent geographic or other restrictions imposed by target websites is prohibited.

50. The administration is not responsible for potential copyright infringements or other legal issues arising from the use of the proxies.

51. If proxies from the Resource are used for actions that may trigger legal consequences, users agree to compensate for any losses incurred by the administration or other parties.

52. Users agree to use proxies only in countries where such actions are legal and must not violate local cybersecurity or privacy laws.

53. The administration may change or supplement these rules at any time, and changes take effect immediately after publication on the site.

Privacy policy

Collection and use of information

By continuing to use this site, you consent to the processing of your user data (username, email address, cookies, location data, IP address, OS type and version, browser type and version, device type and screen resolution, referral source, advertising source, OS and browser language, pages visited, and buttons clicked). Good-proxies.ru collects this information to understand site visitors better and improve the site's functionality. If you do not want your data to be processed, please leave the site.

Disclosure of information

We do not disclose user information to companies, organizations, or individuals unrelated to us, except in the cases described below:

As required by law. Information may be disclosed to prevent fraud or other illegal activity, to comply with legislation, and in other cases provided by law.

For service delivery and fulfillment of obligations. Users agree that personal information may be transferred to third parties to provide services ordered on the site or fulfill other obligations to the user. Such parties include courier services, postal services, freight companies, and others.

What personal information is processed when users contact support by email or live chat?

We process all correspondence received from clients, including textual content and metadata. To do so we store users' email addresses. Our site or mail servers generate metadata related to our communications using the SMTP protocol. Our goal is to deliver the most efficient support and improve the service.

Correspondence is handled via a third-party platform: Zendesk (for real-time communication and email support). When you contact us, your data - including name and email address - is recorded on this platform. Please review that service's privacy policy:

Zendesk: https://www.zendesk.com/company/policies-procedures/

Privacy policy of the external service Digiseller.ru

Digiseller: https://digiseller.ru/privacy

Analytics

Good-proxies.ru uses Yandex.Metrica (web analytics) and Cloudflare to analyze site traffic. When a user's browser loads a page on our site, a script runs that collects various data (screen resolution, device, language, related sites, etc.) for analytics. Web analytics may store cookies to identify returning visitors.

Security

We implement appropriate security measures for collecting, storing, and processing data to protect it from unauthorized access, alteration, disclosure, or destruction. We limit access to personal data for our employees, contractors, and agents, and continuously improve our data collection, storage, and processing methods, including physical safeguards, to prevent unauthorized access to our systems.

However, we cannot guarantee 100% that our security measures will prevent third-party "hackers" from unlawfully obtaining this information, even though we take all reasonable steps to avoid such breaches. You accept the risk of such incidents to the extent that they may occur despite our reasonable security measures.

Disclaimer

This privacy policy does not apply to other sites and does not cover third-party websites that may reference our site or link to it, as well as sites that we link to. We are not responsible for the actions of other websites.

Enforcement of the privacy policy and changes

We may revise this policy from time to time. You can review the current version at any time at https://good-proxies.ru/toc.

By using this site, you agree to this privacy policy. If you do not agree, please do not use our site. Your continued use after changes are made will be deemed acceptance of those changes.

How to refuse cookies

You can withdraw your consent to cookies in your browser at any time. If you do not want to use cookies, configure your browser to automatically block them or to notify you whenever a site requests to store cookies. To set up your preferences, use one of the links below:

Other terms

By purchasing a Premium access key, the user agrees to receive informational newsletters from the Resource at the email address provided during purchase.

PHP example script for retrieving proxies via the API

Download here: https://good-proxies.ru/test.tgz

Changes to the terms of use of this Resource

The current version of the Terms is always available at https://good-proxies.ru/toc. The administration may change this document without prior notice, and changes take effect immediately after publication.

Rights of the Resource administration

If a user is found or suspected to be violating these Terms, the administration reserves the right to block access without prior notice or refund. Access is blocked by disabling the user's keys, IP addresses, email addresses, and payment details.

The administration reserves the right to change any parameters of the Resource without prior notice.

Tariff plans

7-day premium access - limit: 34,560 API requests per day and API access from 10 IP subnets a.b.0.0/16.

30-day premium access - limit: 34,560 API requests per day and API access from 10 IP subnets a.b.0.0/16.

60-day premium access - limit: 34,560 API requests per day and API access from 10 IP subnets a.b.0.0/16.

180-day premium access - limit: 34,560 API requests per day and API access from 10 IP subnets a.b.0.0/16.

Proxies for services (detailed description)

Verification speed: 50 threads, returning proxies tested within the last 10 minutes.

Refunds

Because the proxies provided are open and not controlled by the Resource, and no guaranteed proxy characteristics are promised, users may request a refund for a key only if defects not described by the seller are found. Refunds are granted only if the Resource downtime lasts for half the key's validity period, but at least 24 hours. In all other cases - including the permanent or temporary absence of proxies with specific characteristics (for example, HTTP proxies from Russia that work with both Yandex and Google without captchas) - refunds are not provided.

Refunds are issued minus the full or partial days of Premium access already used.

Refunds through DigiSeller and WebMoney are possible only to a WebMoney Transfer wallet or by crediting the account of a Russian mobile operator, regardless of the initial payment method. If necessary, register with WebMoney Transfer. Additional costs related to currency conversion are not reimbursed. The exception is refunds for purchases made via PayPal; such refunds follow PayPal's user agreement (section 11 "PayPal Buyer Protection Programs").

To request a refund via cardlink.link, visit https://cardlink.link and follow the refund section. Additional costs related to currency conversion or payment system commissions are not reimbursed.

Once a refund is processed, the corresponding Premium key is blocked immediately.

Feedback

Support service [email protected]

В данном продукте используются данные GeoLite2, созданные компанией MaxMind, доступные по адресу https://www.maxmind.com.

Good-Proxies.ru использует базу IP2Location LITE для определения геолокации IP-адресов.

Я полностью прочитал и принимаю условия использования данного ресурса

API Documentation for Retrieving Proxies

Description

Main Request Parameters

TXT Format Parameters

JSON Format Parameters

Request Examples

Example 1: 5 proxies with HTTP type and "elite" anonymity in JSON format

Example 2: 10 proxies with HTTPS type and maximum ping 500 ms in TXT file format for download

Example 3: 2 proxies from USA and Canada in list format (displayed as text in browser)

Example 4: TXT with protocol prefix type://ip:port

Example 5: JSON - selected fields only, IP and port split

Example 6: JSON with metadata envelope (wrap=1)

Example 7: Filter by city in English

Example 8: Compact JSON without indentation (for automated processing)

Response Format

Successful JSON Response

Successful TXT Response

Successful TXT Response for Download

Successful JSON Response for Download

Errors

Limits

Notes

PHP Usage Example

Conclusion

Информация об IP-адресе

Условия использования

Terms and definitions

Service description

Getting started

System workflow and proxy sources on this website

API description

Parameter descriptions

Proxy types

Rules for using this Resource

Privacy policy

Collection and use of information

Disclosure of information

What personal information is processed when users contact support by email or live chat?

Privacy policy of the external service Digiseller.ru

Analytics

Security

Disclaimer

Enforcement of the privacy policy and changes

How to refuse cookies

Other terms

PHP example script for retrieving proxies via the API

Changes to the terms of use of this Resource

Rights of the Resource administration

Tariff plans

Proxies for services (detailed description)

Refunds

Feedback