All the examples in this document are based on
|Compatibility||Compatible with most versions of Visual Studio, recommend to use
|Data communication flow chart||Data communication flow chart|
Use command line to get from Github
git clone https://github.com/GeeTeam/gt3-dotnet-sdk.git
Download SDK manually
Get the latest SDK from Github: gt3-dotnet-sdk (in
To import SDK, please firstly open the
.sln file in SDK with VS.
Then, add the following code.
Configure key pair
Get your key pair from GeeTest Dashboard. The key pair consists of a public key(captcha ID) and a private key (KEY). Then, configure the key pair through the following path.
Modify the request (optional)
|user_id||User identification. If you concern about the risk of user information, you can preprocess (e.g. hashed) it.|
|client_type||Type of client. Web (web browser for computers)，h5 (mobile browser，include webview)，native(native mobile app)，unknown (unknow client type)|
|ip_address||Client request for your server IP address, unknow means unknow IP address|
Initiate captcha via
challenge and set the
statusindicates captcha initialization. Status=1 refers to successful initialization, status=0 refers to downtime. Please store the
status, since it will be needed in secondary verification. In the demo above, session has been used to store
How to simulate the Failback mode? Please fill in an incorrect string (e.g. 123456789) for the captcha ID. Then, it will enter the Failback mode.
To run the demo, please open the Solution Explorer and right click the demo
To view the demo, please visit
http://localhost:2343/index.aspx in your browser.
- SDK internal logic errors. Please check: a) whether
sessionis stored and read successfully, b) whether the code could successfully process to the module which send a request to GeeTest server, c) check the return value of GeeTest server.
- Multiple submission. The API which initiates the secondary verification is only available for one time.
challengeis inconsistent. Please ensure the consistency of
challengeduring the whole verification process.
- Check if
keyin the code are correct in SDK. Please check if the parameters has been passed correctly.
- Please provide
challengeto our service team. They could help you to check the log.