Skip to main content
Niquests Logo

Niquests is a simple, yet elegant, HTTP library. It is a drop-in replacement for Requests, which is under feature freeze. ✨ Were you used to betamax, requests-mock, responses, ...? See how they still work! We got you covered.

Niquests, is the “Safest, Fastest1, Easiest, and Most advanced” Python HTTP Client. Production Ready!

Live Benchmark

Target: https://httpbingo.org/get
Conditions: All default parameters, one shared session, everything simultaneously.
HTTP/2 when supported.
Niquests Benchmark
👆 Look at the feature table comparison against requests, httpx and aiohttp!
Feature niquests requests httpx aiohttp
HTTP/1.1 ✅ ✅ ✅ ✅
HTTP/2 ✅ ❌ ✅2 ❌
HTTP/3 over QUIC ✅ ❌ ❌ ❌
Synchronous ✅ ✅ ✅ N/A3
Asynchronous ✅ ❌ ✅ ✅
Thread Safe ✅ ✅ ❌4 N/A3
Task Safe ✅ N/A5 ✅ ✅
OS Trust Store ✅ ❌ ❌ ❌
Multiplexing ✅ ❌ Limited6 ❌
DNSSEC ✅7 ❌ ❌ ❌
Customizable DNS Resolution ✅ ❌ ❌ ✅
DNS over HTTPS ✅ ❌ ❌ ❌
DNS over QUIC ✅ ❌ ❌ ❌
DNS over TLS ✅ ❌ ❌ ❌
Multiple DNS Resolver ✅ ❌ ❌ ❌
Network Fine Tuning & Inspect ✅ ❌ Limited8 Limited8
Certificate Revocation Protection ✅ ❌ ❌ ❌
Session Persistence ✅ ✅ ✅ ✅
In-memory Certificate CA & mTLS ✅ ❌ Limited9 Limited9
SOCKS 4/5 Proxies ✅ ✅ ✅ ❌
HTTP/HTTPS Proxies ✅ ✅ ✅ ✅
TLS-in-TLS Support ✅ ✅ ✅ ✅
Direct HTTP/3 Negotiation ✅10 N/A11 N/A11 N/A11
Happy Eyeballs ✅ ❌ ❌ ✅
Package / SLSA Signed ✅ ❌ ❌ ✅
HTTP/2 with prior knowledge (h2c) ✅ ❌ ✅ ❌
Post-Quantum Security Limited12 ❌ ❌ ❌
HTTP Trailers ✅ ❌ ❌ ❌
Early Responses ✅ ❌ ❌ ❌
WebSocket over HTTP/1 ✅ ❌13 ❌13 ✅
WebSocket over HTTP/2 and HTTP/3 ✅14 ❌ ❌ ❌
Automatic Ping for HTTP/2+ ✅ N/A ❌ N/A
Automatic Connection Upgrade / Downgrade ✅ N/A ❌ N/A
Server Side Event (SSE) ✅ ❌ ❌ ❌
WASM / Pyodide ✅ ✅ ❌ ❌
📈 Look at the performance comparison against them!

Given the script hosted at https://gist.github.com/Ousret/9e99b07e66eec48ccea5811775ec116d that simply send 1000 requests. We deliberately use a real remote endpoint, disabled Niquests manual multiplexing (for fairness), to showcase how the client behave in a real life usage.

GET https://httpbingo.org/get

Client Average Delay to Complete Notes
httpx 2.087s HTTP/2
aiohttp 1.351s HTTP/1.1
niquests 0.551s HTTP/2

:tada: Niquests can easily bring you twice the throughput if you migrated today. Join us today!

>>> import niquests
>>> r = niquests.get('https://one.one.one.one')
>>> r.status_code
200
>>> r.headers['content-type']
'application/json; charset=utf-8'
>>> r.oheaders.content_type.charset
'utf-8'
>>> r.encoding
'utf-8'
>>> r.text
'{"authenticated": true, ...'
>>> r.json()
{'authenticated': True, ...}
>>> r
<Response HTTP/2 [200]>
>>> r.ocsp_verified
True
>>> r.conn_info.established_latency
datetime.timedelta(microseconds=38)

or using async/await!

import niquests
import asyncio

async def main() -> None:
    r = await niquests.aget('https://one.one.one.one', stream=True)
    print(r)  # Output: <Response HTTP/2 [200]>
    payload = await r.text  # we await text because we set `stream=True`!
    print(payload)  # Output: <html>...
    # or... without stream=True
    r = await niquests.aget('https://one.one.one.one')
    print(r)  # Output: <Response HTTP/3 [200]>
    payload = r.text  # we don't need to away anything, it's already loaded!
    print(payload)  # Output: <html>...

asyncio.run(main())

Niquests allows you to send HTTP requests extremely easily. There’s no need to manually add query strings to your URLs, or to form-encode your PUT & POST data — just use the json method!

PyPI Downloads Supported Versions OpenSSF Best Practices

This project does not require any compilation toolchain. The HTTP/3 support is not enforced and installed if your platform can support it natively (e.g. pre-built wheel available).

✨ Installing Niquests and Supported Versions

Niquests is available on PyPI:

$ python -m pip install niquests

Niquests officially supports Python or PyPy 3.7+.

🚀 Supported Features & Best–Practices

Niquests is ready for the demands of building scalable, robust and reliable HTTP–speaking applications.

  • DNS over HTTPS, DNS over QUIC, DNS over TLS, and DNS over UDP
  • Automatic Content Decompression and Decoding
  • OS truststore by default, no more certifi!
  • OCSP Certificate Revocation Verification
  • Advanced connection timings inspection
  • In-memory certificates (CAs, and mTLS)
  • Browser-style TLS/SSL Verification
  • Certificate Revocation List (CRL)
  • Sessions with Cookie Persistence
  • Keep-Alive & Connection Pooling
  • International Domains and URLs
  • Automatic honoring of .netrc
  • Basic & Digest Authentication
  • Familiar dict–like Cookies
  • Network settings fine-tuning
  • HTTP/2 with prior knowledge
  • Object-oriented headers
  • Multi-part File Uploads
  • Post-Quantum Security
  • Chunked HTTP Requests
  • Fully type-annotated!
  • Run in the Browser!
  • SOCKS Proxy Support
  • Connection Timeouts
  • Streaming Downloads
  • HTTP/2 by default
  • HTTP/3 over QUIC
  • Early Responses
  • Happy Eyeballs
  • Multiplexed!
  • Thread-safe!
  • WebSocket!
  • Trailers!
  • DNSSEC!
  • Async!
  • SSE!

Need something more? Create an issue, we actively listen.

📝 Why did we pursue this?

For many years now, Requests has been frozen. Being left in a vegetative state and not evolving, this blocked millions of developers from using more advanced features.

We don't have to reinvent the wheel all over again, HTTP client Requests is well established and really pleasant in its usage. We believe that Requests has the most inclusive and developer friendly interfaces. We intend to keep it that way. As long as we can, long live Niquests!

How about a nice refresher with a mere CTRL+H import requests to import niquests as requests ?

💼 For Enterprise

Professional support for Niquests is available as part of the Tidelift Subscription. Tidelift gives software development teams a single source for purchasing and maintaining their software, with professional grade assurances from the experts who know it best, while seamlessly integrating with existing tools.

You may also be interested in unlocking specific advantages (like access to a private issue tracker) by looking at our GitHub sponsor tiers.


Niquests is a highly improved HTTP client that is based (forked) on Requests. The previous project original author is Kenneth Reitz and actually left the maintenance of Requests years ago.

  1. performance measured when leveraging a multiplexed connection with or without uses of any form of concurrency as of Mars 2026. The research compared httpx, requests, aiohttp against niquests. See https://gist.github.com/Ousret/9e99b07e66eec48ccea5811775ec116d ↩

  2. while advertised as possible, they refuse to make it the default due to performance and stability issues. as of December 2025 an extra is required to enable it manually. ↩

  3. aiohttp was conceived solely for an asynchronous context. ↩ ↩2

  4. httpx officially claim to be thread safe but recent tests demonstrate otherwise as of Mars 2026. https://github.com/jawah/niquests/issues/83#issuecomment-1956065258 https://github.com/encode/httpx/issues/3072 https://github.com/encode/httpx/issues/3002 and only recently acknowledged the issue in https://github.com/encode/httpx/issues/3324 (one year after getting valid reports). ↩

  5. requests has no support for asynchronous request. ↩

  6. while the HTTP/2 connection object can handle concurrent requests, you cannot leverage its true potential. ↩

  7. enabled when using a custom DNS resolver. ↩

  8. they do not expose anything to control network aspects such as IPv4/IPv6 toggles, and timings (e.g. DNS response time, established delay, TLS handshake delay, etc...) and such. ↩ ↩2

  9. loading client certificate without file can't be done. ↩ ↩2

  10. you must use a custom DNS resolver so that it can preemptively connect using HTTP/3 over QUIC when remote is compatible. ↩

  11. they don't support HTTP/3 at all. ↩ ↩2 ↩3

  12. available only when using HTTP/3 over QUIC and that the remote server support also the same post-quantum key-exchange algorithm. Also, the qh3 installed version must be >= 1.1. ↩

  13. they don't offer any built-in to speak with a WebSocket server. ↩ ↩2

  14. most servers out there are not ready for this feature, but Niquests is already compliant and future-proof! Caddy server and HAProxy support this! ↩

Metadata

Release files for niquests 3.18.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for niquests 3.18.1
File Size Uploaded Provenance Actions
niquests-3.18.1.tar.gz 1.0 MB With provenance Details for niquests-3.18.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for niquests 3.18.1
File Interpreter ABI Platform Actions
niquests-3.18.1-py3-none-any.whl Python 3 none any Details for niquests-3.18.1-py3-none-any.whl

Total release size: 1.2 MB

Release files / niquests-3.18.1.tar.gz

Download URL niquests-3.18.1.tar.gz
Size 1.0 MB
Tags Source
SHA-256 checksum
How to use checksums
cc5e8c719ca537dae7e86c4c7349b0a85f7a4364db2e62816872ad94d88c3437
BLAKE2b-256 checksum
How to use checksums
dce74fae122d213e6aa15a0caa6ea73dd8e1ffd4a3b54cd723cee42f0f452432
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Mar 9, 2026.

Transparency log

Release files / niquests-3.18.1-py3-none-any.whl

Download URL niquests-3.18.1-py3-none-any.whl
Size 207.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
83cda6c0025f63f014745b0f3d7c76802437e091becfe6416a5cfc7992c80ad0
BLAKE2b-256 checksum
How to use checksums
0e9e7191a39d05894bf2b7ab645bbc598da77f189b7ebc04bfd6d37c259e0f24
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Mar 9, 2026.

Transparency log

Security for niquests 3.18.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for niquests-3.18.1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Mar 9, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

3.18.1 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page