Friendly Captcha Python SDK
A Python client for the Friendly Captcha service. This client allows for easy integration and verification of captcha responses with the Friendly Captcha API.
This library is for Friendly Captcha V2 only. If you are looking for V1, look here
Installation
pip install friendly-captcha-client
Usage
Below are some basic examples of how to use the client.
For a more detailed example, take a look at the example directory.
Initialization
To start using the client:
from friendly_captcha_client.client import FriendlyCaptchaClient
client = FriendlyCaptchaClient(
api_key="YOUR_API_KEY",
sitekey="YOUR_SITEKEY"
)
Verifying a Captcha Response
After calling verify_captcha_response with the captcha response there are two functions on the result object that you should check:
was_able_to_verifyindicates whether we were able to verify the captcha response. This will beFalsein case there was an issue with the network/our service or if there was a mistake in the configuration.should_acceptindicates whether the captcha response was correct. If the client is running in non-strict mode (default) andwas_able_to_verifyreturnedFalse, this will beTrue.
Below are some examples of this behaviour.
Verifying a correct captcha response without issues when veryfing:
result = client.verify_captcha_response("CORRECT?CAPTCHA_RESPONSE_HERE")
print(result.was_able_to_verify) # True
print(result.should_accept) # True
Verifying an incorrect captcha response without issues when veryfing:
result = client.verify_captcha_response("INCORRECT_CAPTCHA_RESPONSE_HERE")
print(result.was_able_to_verify) # True
print(result.should_accept) # False
Verifying an incorrect captcha response with issues (network issues or bad configuration) when veryfing in non-strict mode (default):
result = client.verify_captcha_response("INCORRECT_CAPTCHA_RESPONSE_HERE")
print(result.was_able_to_verify) # False
print(result.should_accept) # True
Verifying an incorrect captcha response with issues (network/service issues or bad configuration) when veryfing in strict mode:
client.strict = True
result = client.verify_captcha_response("INCORRECT_CAPTCHA_RESPONSE_HERE")
print(result.should_accept) # False
print(result.was_able_to_verify) # False
Risk Intelligence Data Retrieval
Use retrieve_risk_intelligence to retrieve risk intelligence data from a token.
result = client.retrieve_risk_intelligence("RISK_INTELLIGENCE_TOKEN_HERE")
if not result.was_able_to_retrieve:
# handle request/client error, inspect result.error
return
if not result.is_valid:
# handle invalid token, inspect result.error
return
print(result.data.risk_intelligence) # The risk intelligence data
Configuration
The client offers several configuration options:
- api_key: Your Friendly Captcha API key.
- sitekey: (Optional) Your Friendly Captcha sitekey. Configure this if you want to ensure that a captcha solution or risk intelligence token was generated from a specific sitekey.
- strict: (Optional) In case the client was not able to verify the captcha response at all (for example if there is a network failure or a mistake in configuration), by default the
verify_captcha_responsereturnsTrueregardless. By passingstrict=True, it will returnFalseinstead: every response needs to be strictly verified. - api_endpoint: (Optional) Base API endpoint (for example
https://eu.frcapi.com). Shorthandseuorglobalare also accepted. Default isglobal. - siteverify_endpoint: (Optional,Deprecated) Kept for backwards compatibility, use
api_endpointinstead. Accepts a full siteverify URL or shorthandseu/global; path is stripped and converted toapi_endpoint. - verbose: (Optional) Default is False. Turn on basic logging.
- Error Handling: The client has built-in error handling mechanisms. In case of unexpected responses or errors from the Friendly Captcha API, the client will log the error and provide a default response.
Development
To install it locally:
pip install -e .
pip install -r requirements-dev.txt
Run the tests:
# Run the unit tests
python -m pytest
# Run the SDK integration tests (requires that you have the SDK test mock server running)
docker run -p 1090:1090 friendlycaptcha/sdk-testserver:latest
python -m pytest integration_tests
License
Open source under MIT.
Release files for friendly-captcha-client 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| friendly_captcha_client-0.2.1.tar.gz | 11.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| friendly_captcha_client-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.6 kB
Release files / friendly_captcha_client-0.2.1.tar.gz
| Download URL | friendly_captcha_client-0.2.1.tar.gz |
|---|---|
| Size | 11.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
81245bfc556f85d9808bedb4921880fbdaa840f0eff4a60a0fa53030b6cec9aa
|
|
BLAKE2b-256 checksum How to use checksums |
54041de491f6aa6067eada38a6cdb4ec1d4b47449d029e149e5b45bc009403de
|
| 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 24, 2026.
Transparency logRelease files / friendly_captcha_client-0.2.1-py3-none-any.whl
| Download URL | friendly_captcha_client-0.2.1-py3-none-any.whl |
|---|---|
| Size | 12.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4b9d89ee35f07670d88076f852d18acfd6b570e0c6e5a61d4ab146fd30522f8d
|
|
BLAKE2b-256 checksum How to use checksums |
1bbd4b4b46f28221ebe6c021e02e732afb9add3c35f27fd27fd628089a7dc340
|
| 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 24, 2026.
Transparency log