You might want to start with some basics on client-server communication before delving into networking/web-dev side of Python. As others have mentioned here, requests docs is a great place to learn about the library, but if you don't know what a 'POST' or 'GET' method is or what's a request header used for, the docs won't make much sense. There are plenty of free online resources which explains the above concepts. Listing some of them which I think should cover your case: https://www.freecodecamp.org/news/http-request-methods-explained/ https://doc.oroinc.com/api/http-methods/ https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers https://developer.mozilla.org/en-US/docs/Learn/JavaScript/Objects/JSON More on reddit.com

I am a PHP developer, tasked to write Python scripts. The script uses requests, which I found to be the easiest Python equivalent to PHP cURL. If you use cURL in PHP, cURL must be enabled on the se... More on stackoverflow.com

No one is sticking up for requests here yet, so I think I had better. If you're thinking hard about it and want to use all fancy custom features for whatever fancy performance benefit, look at the other suggestions. If you want to not have to think about it and do the least possible work to get it functional, use requests. It's unbelievably straightforward. It is the Python way. More on reddit.com

This is a pretty interesting and at times disappointing PR from both sides. At one point the decision was made to not make requests part of the standard library because it allowed the maintainers or requests to adapt to pr's much more quickly. Is it time to move from requests? I would say that just because Airflow has some strict requirements place on it by the ASF doesn't mean other developers will be rushing to replace a tried and true library. That said HTTPX is meant to be drop in place for Requests so if you feel the inclination to change out requests in a project it should be doable. More on reddit.com