Search the Community

I am trying to use the API to generate a .conf file for wireguard. This works fine, curl -H "API-KEY:xxxxx" "https://airvpn.org/api/generator/?system=windows&protocols=wireguard_1_udp_1637&servers=america" but when I try to specify servers by country I get an error. Does anyone have it working for countries? As an aside, the API page mentions, "checking API Reference" on the generator page, but I don't see that option there nor am I able to find an API reference elsewhere.

Hello, I'm one of the Mullvad refugees. While I tried it for a few weeks now, using a peer-to-peer protocol without a forwarded port was just too slow and often it was even impossible to establish connections to peers. And although I'm very happy with your service and the general scope of the API, there are some things that are broken or that I'm missing: Setting device names and descriptions via the API. Assigning ports to devices via the API (preferable by ID and name, but most importantly by ID), maybe also claiming ports via the API. In my tests calls to the configuration generator API with "resolve=on" would only work for IPv4 endpoints, not for IPv6 endpoints. It would be great if this also worked for IPv6 addresses. It seems a bit strange to me that adding a device returns a longer ID, while the other parts of the API which use the ID seem to truncate it to 50 characters. Why isn't the truncated ID returned uniformly? It would be nice for my use-case to also have the configuration generator optionally return JSON. The current configurations are to be consumed by wg-quick and while using wg-quick (either to load them or to transform them to wg rules) or parsing them and using them with wg is easy enough, it would just be nice to have the additional option. Maybe with some nice clean key names like "public_key". Example request for the mentioned IP resolution problem: curl -H "Api-Key: <REDACTED>" "https://airvpn.org/api/generator/?protocols=wireguard_1_udp_1637&servers=europe&device=default&resolve=on&iplayer_entry=ipv6" -o AirVPN_Europe_UDP-1637.conf This will properly resolve the hostname to an IP when "iplayer_entry=ipv4" (or the empty default) is set, but just pass the hostname through when "iplayer_entry=ipv6" is specified.

Hi! API "notification" service in https://airvpn.org/apisettings/ mentions that it's possible to send yourself a notification to the AirVPN website or own email and that can be configured here: https://airvpn.org/notifications/options/. The API itself works and sends a notification to the website, but I can't find a way to switch it to email. Am I looking into the right notification settings? I see there a section called "AirVPN", but it's empty.

Hey. Would you consider adding a single server query to the status API (e.g. api/status/?server=server_name)? It seems a bit wasteful to pull the whole list if you just want stats for a single server. BR

I was wondering whether it is possible to control to which country/city to connect? Or AirVPN API does not provide any control but rather just information about current connetion?

Quality of Service post: Although it is a 10Gbit server it seems to be suffering. I'm from Europe and checking its ping shows average 344ms over 234 attempts. This puts it in range of JP and NZ servers at 350ms. This is not the first time I've seen it perform poorly. Last week I connected to se.vpn.airdns.org (and it still shows as the preferred choice in API and https://airvpn.org/status/ EDIT: not any longer as of finishing writing) and had the same problems downloading a file with speed jumping up and down. To get the ping results I filtered the API JSON into an IP list to use with Nirsoft PingInfoView: https://www.nirsoft.net/utils/multiple_ping_tool.html Current IP list: (if you read this post at a later date: it is not up to date!) sortscript.sh | sort -k2 185.9.19.106 at, Alderamin (Austria, Vienna; 1000) 37.120.155.178 at, Beemim (Austria, Vienna; 1000) 217.64.127.194 at, Caelum (Austria, Vienna; 1000) 194.187.251.90 be, Capricornus (Belgium, Brussels; 1000) 91.207.57.114 be, Castor (Belgium, Brussels; 1000) 194.187.251.114 be, Columba (Belgium, Brussels; 1000) 194.187.251.162 be, Diadema (Belgium, Brussels; 1000) 194.187.251.154 be, Mebsuta (Belgium, Brussels; 1000) 82.102.23.130 bg, Apus (Bulgaria, Sofia; 1000) 82.102.23.138 bg, Grus (Bulgaria, Sofia; 1000) 45.162.229.146 br, Lalande (Brazil, Sao Paulo; 1000) 45.162.228.170 br, Peony (Brazil, Sao Paulo; 1000) 184.75.223.210 ca, Agena (Canada, Toronto, Ontario; 1000) 162.219.176.2 ca, Alhena (Canada, Toronto, Ontario; 1000) 184.75.221.202 ca, Alkurhah (Canada, Toronto, Ontario; 1000) 104.254.90.202 ca, Aludra (Canada, Toronto, Ontario; 1000) 184.75.221.114 ca, Alwaid (Canada, Toronto, Ontario; 1000) 184.75.221.170 ca, Alya (Canada, Toronto, Ontario; 1000) 184.75.221.162 ca, Angetenar (Canada, Toronto, Ontario; 1000) 184.75.221.210 ca, Arkab (Canada, Toronto, Ontario; 1000) 184.75.223.234 ca, Avior (Canada, Toronto, Ontario; 1000) 184.75.214.162 ca, Cephei (Canada, Toronto, Ontario; 1000) 104.254.90.234 ca, Chort (Canada, Toronto, Ontario; 1000) 104.254.90.242 ca, Enif (Canada, Toronto, Ontario; 1000) 104.254.90.250 ca, Gorgonea (Canada, Toronto, Ontario; 1000) 87.101.92.170 ca, Lacerta (Canada, Montreal; 1000) 184.75.221.2 ca, Lesath (Canada, Toronto, Ontario; 1000) 184.75.223.218 ca, Mintaka (Canada, Toronto, Ontario; 1000) 192.30.89.66 ca, Nahn (Canada, Vancouver; 1000) 192.30.89.26 ca, Pisces (Canada, Vancouver; 1000) 184.75.221.34 ca, Regulus (Canada, Toronto, Ontario; 1000) 139.28.218.234 ca, Ross (Canada, Montreal; 1000) 104.254.90.186 ca, Rotanev (Canada, Toronto, Ontario; 1000) 184.75.221.178 ca, Sadalbari (Canada, Toronto, Ontario; 1000) 184.75.223.226 ca, Saiph (Canada, Toronto, Ontario; 1000) 184.75.223.194 ca, Sargas (Canada, Toronto, Ontario; 1000) 192.30.89.74 ca, Sham (Canada, Vancouver; 1000) 104.254.90.194 ca, Sharatan (Canada, Toronto, Ontario; 1000) 184.75.221.42 ca, Sualocin (Canada, Toronto, Ontario; 1000) 137.63.71.50 ca, Tegmen (Canada, Toronto, Ontario; 1000) 184.75.221.194 ca, Tejat (Canada, Toronto, Ontario; 1000) 192.30.89.50 ca, Telescopium (Canada, Vancouver; 1000) 192.30.89.58 ca, Titawin (Canada, Vancouver; 1000) 184.75.223.202 ca, Tyl (Canada, Toronto, Ontario; 1000) 184.75.221.58 ca, Ukdah (Canada, Toronto, Ontario; 1000) 185.156.175.170 ch, Achernar (Switzerland, Zurich; 1000) 185.156.175.34 ch, Achird (Switzerland, Zurich; 1000) 185.156.175.50 ch, Baiten (Switzerland, Zurich; 1000) 195.206.105.226 ch, Dorado (Switzerland, Zurich; 1000) 185.156.175.42 ch, Hamal (Switzerland, Zurich; 1000) 91.214.169.68 ch, Kitalpha (Switzerland, Zurich; 1000) 195.206.105.202 ch, Sextans (Switzerland, Zurich; 1000) 185.156.175.58 ch, Sirrah (Switzerland, Zurich; 1000) 46.19.137.114 ch, Virginis (Switzerland, Bern; 1000) 79.142.69.159 ch, Xuange (Switzerland, Zurich; 10000) 185.156.174.114 cz, Centaurus (Czech Republic, Prague; 1000) 185.156.174.26 cz, Markab (Czech Republic, Prague; 1000) 185.156.174.154 cz, Turais (Czech Republic, Prague; 1000) 89.238.166.234 cz, Zuben (Czech Republic, Prague; 1000) 185.104.184.42 de, Adhara (Germany, Frankfurt; 1000) 141.98.102.186 de, Alsephina (Germany, Frankfurt; 1000) 185.189.112.26 de, Cervantes (Germany, Frankfurt; 1000) 37.120.217.242 de, Cujam (Germany, Berlin; 1000) 141.98.102.242 de, Dubhe (Germany, Frankfurt; 1000) 185.189.112.10 de, Errai (Germany, Frankfurt; 1000) 178.162.204.227 de, Intercrus (Germany, Frankfurt; 1000) 141.98.102.226 de, Menkalinan (Germany, Frankfurt; 1000) 79.143.191.166 de, Mesarthim (Germany, Munich; 1000) 141.98.102.234 de, Mirfak (Germany, Frankfurt; 1000) 141.98.102.178 de, Mirzam (Germany, Frankfurt; 1000) 185.189.112.18 de, Ogma (Germany, Frankfurt; 1000) 178.162.209.151 de, Serpens (Germany, Frankfurt; 1000) 178.162.204.219 de, Tucana (Germany, Frankfurt; 1000) 178.162.204.222 de, Veritate (Germany, Frankfurt; 1000) 185.195.237.202 ee, Alruba (Estonia, Tallinn; 1000) 185.183.106.2 es, Eridanus (Spain, Barcelona; 1000) 185.93.182.170 es, Mekbuda (Spain, Madrid; 1000) 194.99.104.34 es, Taurus (Spain, Madrid; 1000) 185.103.96.132 gb, Alathfar (United Kingdom, Maidenhead; 1000) 217.151.98.162 gb, Alshain (United Kingdom, London; 1000) #89.238.150.42 gb, Arion (United Kingdom, London; 1000) 217.151.98.167 gb, Asterion (United Kingdom, London; 1000) 89.249.74.212 gb, Asterope (United Kingdom, Manchester; 1000) 185.103.96.134 gb, Betelgeuse (United Kingdom, Maidenhead; 1000) 94.229.74.90 gb, Carinae (United Kingdom, Maidenhead; 1000) 89.249.74.217 gb, Chow (United Kingdom, Manchester; 1000) 185.103.96.133 gb, Denebola (United Kingdom, Maidenhead; 1000) 2.58.47.202 gb, Geminorum (United Kingdom, London; 1000) 185.103.96.131 gb, Kitel (United Kingdom, Maidenhead; 1000) 185.103.96.130 gb, Minkar (United Kingdom, Maidenhead; 1000) 84.39.117.56 gb, Naos (United Kingdom, Manchester; 1000) 84.39.116.179 gb, Nashira (United Kingdom, Manchester; 1000) 192.145.126.114 gb, Orbitar (United Kingdom, Manchester; 1000) 141.98.101.132 gb, Westerlund (United Kingdom, Manchester; 1000) 37.120.210.210 jp, Biham (Japan, Tokyo; 1000) 82.102.28.106 jp, Iskandar (Japan, Tokyo; 1000) 37.120.210.218 jp, Okab (Japan, Tokyo; 1000) 193.148.16.210 jp, Taphao (Japan, Tokyo; 1000) 46.183.220.202 lv, Felis (Latvia, Riga; 1000) #159.148.186.13 lv, Meissa (Latvia, Riga; 100) 159.148.186.18 lv, Phact (Latvia, Riga; 100) 159.148.186.24 lv, Schedir (Latvia, Riga; 100) 159.148.186.31 lv, Shaula (Latvia, Riga; 100) 213.152.161.180 nl, Alchiba (Netherlands, Alblasserdam; 1000) 213.152.161.116 nl, Alcyone (Netherlands, Alblasserdam; 1000) 134.19.179.170 nl, Aljanah (Netherlands, Alblasserdam; 1000) 213.152.187.199 nl, Alphard (Netherlands, Alblasserdam; 1000) 213.152.187.194 nl, Alphecca (Netherlands, Alblasserdam; 1000) 134.19.179.242 nl, Alpheratz (Netherlands, Alblasserdam; 1000) 213.152.187.214 nl, Alphirk (Netherlands, Alblasserdam; 1000) 213.152.162.78 nl, Alrai (Netherlands, Alblasserdam; 1000) 213.152.161.4 nl, Alshat (Netherlands, Alblasserdam; 1000) 213.152.161.169 nl, Alterf (Netherlands, Alblasserdam; 1000) 213.152.187.204 nl, Alzirr (Netherlands, Alblasserdam; 1000) 213.152.162.164 nl, Ancha (Netherlands, Alblasserdam; 1000) 213.152.161.228 nl, Andromeda (Netherlands, Alblasserdam; 1000) 213.152.186.18 nl, Anser (Netherlands, Alblasserdam; 1000) 213.152.187.209 nl, Asellus (Netherlands, Alblasserdam; 1000) 134.19.179.194 nl, Aspidiske (Netherlands, Alblasserdam; 1000) 213.152.161.9 nl, Atik (Netherlands, Alblasserdam; 1000) 213.152.161.218 nl, Canis (Netherlands, Alblasserdam; 1000) 134.19.179.138 nl, Capella (Netherlands, Alblasserdam; 1000) 213.152.162.169 nl, Caph (Netherlands, Alblasserdam; 1000) 213.152.161.68 nl, Celaeno (Netherlands, Alblasserdam; 1000) 213.152.187.219 nl, Chara (Netherlands, Alblasserdam; 1000) 213.152.186.162 nl, Comae (Netherlands, Alblasserdam; 1000) 213.152.162.14 nl, Crater (Netherlands, Alblasserdam; 1000) 213.152.161.243 nl, Cygnus (Netherlands, Alblasserdam; 1000) 213.152.161.164 nl, Diphda (Netherlands, Alblasserdam; 1000) 213.152.161.210 nl, Edasich (Netherlands, Alblasserdam; 1000) 213.152.186.39 nl, Elnath (Netherlands, Alblasserdam; 1000) 134.19.179.146 nl, Eltanin (Netherlands, Alblasserdam; 1000) 213.152.162.73 nl, Garnet (Netherlands, Alblasserdam; 1000) 213.152.161.100 nl, Gianfar (Netherlands, Alblasserdam; 1000) 213.152.162.93 nl, Gienah (Netherlands, Alblasserdam; 1000) 213.152.161.39 nl, Hassaleh (Netherlands, Alblasserdam; 1000) 213.152.162.4 nl, Horologium (Netherlands, Alblasserdam; 1000) 213.152.161.34 nl, Hyadum (Netherlands, Alblasserdam; 1000) 213.152.162.9 nl, Hydrus (Netherlands, Alblasserdam; 1000) 213.152.186.23 nl, Jabbah (Netherlands, Alblasserdam; 1000) 213.152.161.84 nl, Kajam (Netherlands, Alblasserdam; 1000) 213.152.162.180 nl, Kocab (Netherlands, Alblasserdam; 1000) 134.19.179.178 nl, Larawag (Netherlands, Alblasserdam; 1000) 213.152.186.167 nl, Luhman (Netherlands, Alblasserdam; 1000) 213.152.162.103 nl, Maasym (Netherlands, Alblasserdam; 1000) 213.152.187.224 nl, Matar (Netherlands, Alblasserdam; 1000) 134.19.179.162 nl, Melnick (Netherlands, Alblasserdam; 1000) 213.152.161.29 nl, Merga (Netherlands, Alblasserdam; 1000) 213.152.162.68 nl, Mirach (Netherlands, Alblasserdam; 1000) 213.152.162.88 nl, Miram (Netherlands, Alblasserdam; 1000) 134.19.179.202 nl, Muhlifain (Netherlands, Alblasserdam; 1000) 213.152.162.153 nl, Muscida (Netherlands, Alblasserdam; 1000) 213.152.161.248 nl, Musica (Netherlands, Alblasserdam; 1000) 213.152.161.24 nl, Nash (Netherlands, Alblasserdam; 1000) 213.152.161.238 nl, Orion (Netherlands, Alblasserdam; 1000) 213.152.187.229 nl, Phaet (Netherlands, Alblasserdam; 1000) 134.19.179.130 nl, Piscium (Netherlands, Alblasserdam; 1000) 213.152.162.148 nl, Pleione (Netherlands, Alblasserdam; 1000) 213.152.161.233 nl, Pyxis (Netherlands, Alblasserdam; 1000) 213.152.162.83 nl, Rukbat (Netherlands, Alblasserdam; 1000) 213.152.161.19 nl, Salm (Netherlands, Alblasserdam; 1000) 134.19.179.154 nl, Scuti (Netherlands, Alblasserdam; 1000) 213.152.186.34 nl, Sheliak (Netherlands, Alblasserdam; 1000) 213.152.161.14 nl, Situla (Netherlands, Alblasserdam; 1000) 213.152.162.98 nl, Subra (Netherlands, Alblasserdam; 1000) 134.19.179.186 nl, Suhail (Netherlands, Alblasserdam; 1000) 213.152.161.137 nl, Talitha (Netherlands, Alblasserdam; 1000) 213.152.161.132 nl, Tarazed (Netherlands, Alblasserdam; 1000) 134.19.179.234 nl, Tiaki (Netherlands, Alblasserdam; 1000) 213.152.186.172 nl, Tianyi (Netherlands, Alblasserdam; 1000) 213.152.161.148 nl, Zibal (Netherlands, Alblasserdam; 1000) 82.102.27.194 no, Camelopardalis (Norway, Oslo; 1000) 82.102.27.170 no, Cepheus (Norway, Oslo; 1000) 185.206.225.50 no, Fomalhaut (Norway, Oslo; 1000) 82.102.27.162 no, Gemini (Norway, Oslo; 1000) 185.206.225.58 no, Ophiuchus (Norway, Oslo; 1000) 103.231.91.58 nz, Fawaris (New Zealand, Auckland; 1000) 91.207.102.162 ro, Alamak (Romania, Bucharest; 1000) 86.105.9.66 ro, Canes (Romania, Bucharest; 1000) 152.89.160.130 rs, Alnitak (Serbia, Belgrade; 1000) 128.127.104.79 se, Ain (Sweden, Stockholm; 10000) 62.102.148.149 se, Albali (Sweden, Uppsala; 1000) 62.102.148.142 se, Algieba (Sweden, Uppsala; 1000) 62.102.148.147 se, Algorab (Sweden, Uppsala; 1000) 62.102.148.145 se, Alrami (Sweden, Uppsala; 1000) 62.102.148.140 se, Altarf (Sweden, Uppsala; 1000) 62.102.148.151 se, Alula (Sweden, Uppsala; 1000) 62.102.148.150 se, Atria (Sweden, Uppsala; 1000) 62.102.148.141 se, Azmidiske (Sweden, Uppsala; 1000) 62.102.148.148 se, Benetnasch (Sweden, Uppsala; 1000) 79.142.76.243 se, Copernicus (Sweden, Stockholm; 1000) 62.102.148.144 se, Hatysa (Sweden, Uppsala; 1000) 128.127.105.183 se, Lupus (Sweden, Stockholm; 1000) 62.102.148.143 se, Menkab (Sweden, Uppsala; 1000) 62.102.148.146 se, Muphrid (Sweden, Uppsala; 1000) 31.3.152.99 se, Norma (Sweden, Stockholm; 1000) 103.254.153.68 sg, Antares (Singapore, Singapore; 1000) 185.200.116.210 sg, Auriga (Singapore, Singapore; 1000) 185.200.116.202 sg, Circinus (Singapore, Singapore; 1000) 185.200.116.218 sg, Delphinus (Singapore, Singapore; 1000) 185.200.117.130 sg, Hydra (Singapore, Singapore; 1000) 209.58.173.142 sg, Lacaille (Singapore, Singapore; 1000) 92.119.178.2 sg, Luyten (Singapore, Singapore; 1000) 209.58.183.86 sg, Struve (Singapore, Singapore; 1000) 185.200.116.130 sg, Triangulum (Singapore, Singapore; 1000) 91.231.84.39 ua, Alcor (Ukraine, Kiev; 1000) 173.44.55.154 us, Acamar (United States, Miami; 1000) 107.167.244.66 us, Alkes (United States, Los Angeles; 1000) 199.249.223.129 us, Aquila (United States, Fremont, California; 1000) 193.37.254.2 us, Bootes (United States, Phoenix, Arizona; 1000) 193.37.254.18 us, Chalawan (United States, Phoenix, Arizona; 1000) 199.249.230.41 us, Chamaeleon (United States, Dallas, Texas; 1000) 96.47.229.58 us, Cursa (United States, Miami; 1000) 185.228.19.146 us, Dimidium (United States, New York City; 1000) 199.249.230.36 us, Equuleus (United States, Dallas, Texas; 1000) 68.235.48.107 us, Fang (United States, Chicago, Illinois; 1000) 91.132.0.202 us, Gliese (United States, New York City; 1000) 37.120.132.82 us, Groombridge (United States, Los Angeles; 1000) 199.249.230.46 us, Helvetios (United States, Dallas, Texas; 1000) 64.42.179.58 us, Hercules (United States, Atlanta, Georgia; 1000) 193.37.254.26 us, Indus (United States, Phoenix, Arizona; 1000) 68.235.35.123 us, Kruger (United States, Chicago, Illinois; 1000) 199.249.230.21 us, Leo (United States, Dallas, Texas; 1000) 64.42.179.66 us, Libra (United States, Atlanta, Georgia; 1000) 194.36.111.58 us, Lich (United States, New York City; 1000) 199.249.230.6 us, Mensa (United States, Dallas, Texas; 1000) 107.167.244.50 us, Merope (United States, Los Angeles; 1000) 156.96.151.131 us, Metallah (United States, Pennsylvania; 1000) 64.42.179.42 us, Musca (United States, Atlanta, Georgia; 1000) 199.249.230.16 us, Pegasus (United States, Dallas, Texas; 1000) 193.37.254.34 us, Phoenix (United States, Phoenix, Arizona; 1000) 198.203.28.42 us, Pollux (United States, Jacksonville, Florida; 1000) 199.249.230.26 us, Ran (United States, Dallas, Texas; 1000) 107.167.244.82 us, Sabik (United States, Los Angeles; 1000) 64.42.179.34 us, Sculptor (United States, Atlanta, Georgia; 1000) 199.249.230.11 us, Scutum (United States, Dallas, Texas; 1000) 68.235.52.35 us, Sneden (United States, Chicago, Illinois; 1000) 37.120.132.90 us, Teegarden (United States, Los Angeles; 1000) 64.42.179.50 us, Ursa (United States, Atlanta, Georgia; 1000) 193.37.254.10 us, Virgo (United States, Phoenix, Arizona; 1000) 199.249.230.31 us, Volans (United States, Dallas, Texas; 1000) 199.249.230.1 us, Vulpecula (United States, Dallas, Texas; 1000) 173.44.55.178 us, Yildun (United States, Miami; 1000) I believe it doesn't affect Eddie as it can pick servers on its own by pinging. But the "preferred" server and DNS responses are still dependent on the server logic, hence Ain sometimes ends up recommended as Earth or Europe server (currently not any longer) but seems to always be the preferred choice for Sweden. To quantify that, it's 350 out of 755 users connected to Swedish servers and unnecessarily getting insane jitter and latencies. To proof it's not just me, https://lg.telia.net/ from AMS-IX showed 24ms to another Swedish server by AirVPN and approx. 340ms to Ain. Or AirVPN's own lookup: https://airvpn.org/routes/?q=128.127.104.79 PS: Is it an Intel CPU? Edit: What I meant to say with this post (not only to start investigating Ain) that the "best server" logic should be not only working based on bandwidth load, but the server's relative latency times. PS2: I do realize that it's currently listed as having issues (packet loss) but during my last week's connect afaik it wasn't. Logically, jitter/high latency begins before packet loss kicks in (networking and throughput theory) - https://airvpn.org/servers/Ain/

Hello AirVPN Staff and others. I would very much like to have an API call for creating and removing port forwardings, including requesting a random port. This would allow users to have a different port open for every session started. Setting up a port to be forwarded is already pretty simple, but it does still require having a web browser running and logging in to Air. This may be a small obstacle, but an obstacle nonetheless. I strongly suspect many people will set up a port forwarding only once, and then using the same port for all future sessions, and this has some negative implications for privacy. It is already possible to have this functionality when talking to Air's web server through a browser and clicking buttons manually, so I'm making the assumption it will not be too difficult to do the same through an official HTTP-based API. Does this make sense? I'd love to hear what you think.

For anyone who likes programming with Python, I started a project called AirPy on Github, https://github.com/Delphae/AirVPN AirPy is a Python wrapper around the AirVPN API which everybody can use, which some of you already heard of. The API is very useful to determine your connection, your server connected to and your user info Take a look at https://airvpn.org/api/ to learn more about the free to use API of AirVPN. But the output is in JSON, XML and so on. To use the output in a Python program, in a Python console or in Jupyter I have created the AirPy module. I started it, just for fun. And to get familiar with Python and Object Oriented Programming (I learned programming the old school way: procedures and functions :-)) On Github you will find the AirPy code as well as an example, in Python, how to use the AirPy module. Import the AirPy module with your personal API key and set the default country from AirPy import Airvpn APIKEY = "7de2aa122b7a42b9882d2f5b1e8ff30168ca6468" air = Airvpn(APIKEY,'nl') # when you are located in the Netherlands air = Airvpn(APIKEY,'gb') # when you are located in the UK, and so on Examples print (air.user) print (air.user.connected) print (air.user.login) print (air.connection) print (air.connection.server_name) print (air.sessions[0]) servers = air.servers() for server in servers: print (server) print (air.best()) print (air.rand()) So, if you think it is useful, use it. If you want to contribute, please do. If you have suggestions and improvements, do not hesitate to write them in this post.

"status" API service is publicly available, no API key is needed. For example: curl https://airvpn.org/api/?format=json&service=status It'd be great if a permissive CORS header would be included in a response allowing any origin to access "status" API service. For example: Access-Control-Allow-Origin: * Further down the road, it'd useful to be able to say which origins are allowed to send requests with my API key, so it could be used for more advanced services cross-origin. Background info I'm working on my own config generator and I'd like to run it in a web browser. Workaround I can use https://cors-anywhere.herokuapp.com/ and such for the time being.

I recently stumbled upon the AirVPN API. I'd like to use it but the data provided by the api seems to be lacking information about the second generation servers, i.e. additional entry IPs and ipv6 IPs (and whether those features are available). Am I missing something or - if my assumption is correct - are there any plans to update the API to include the missing data?

I searched the forums a little bit, and didn't see any mention of this, but something that would be really awesome would be to expose the ability to see what ports are currently forwarded, and add or remove ports through the API, if possible. Maybe I'm missing something, but this seems like a killer feature.

Is anyone using the API format? and how is it being used?

What is the feasibility of adding the server's status (online, offline, imminent withdrawal, etc.) as a new Attribute name in an XML formatted API call? This would be very helpful for those of us wishing to rank servers and then select one for connection via openvpn. Thank you.

What is the feasibility of adding the server's IP address as a new Attribute name in an XML formatted API call? This would be very helpful for those of us wishing to rank servers and then select one for connection via openvpn. Thank you.