Find a section & browse all pages
api reference · v1

Turnstile solver API reference.

SolveGate handles Cloudflare Turnstile widgets and Cloudflare challenge pages through one REST endpoint. Request a Turnstile token or a WAF clearance payload, then submit it in the format your target expects.

base url · https://api.solvegate.io/v1auth · Bearer sk_live_•••avg. solve · 24h · —

Last 24h · managed-proxy/direct production requests only. Customer-proxy, sandbox and historical records with unknown proxy attribution are excluded. Success rate is solved ÷ (solved + failed); pending requests are excluded. Latency is recorded successful solve time, not end-to-end wall-clock time. Performance reports refresh every 5 minutes. View methodology →

Introduction

// what the API does and how it's shaped

The SolveGate API is organized around a single resource: the solve. You create a solve by telling us which gate stands in your way and where it lives; we return a Turnstile token or a WAF clearance payload. Your client must apply it to the target, which can perform additional checks.

Every endpoint is HTTPS-only, accepts form or JSON bodies, and returns JSON. Requests are authenticated with a secret key. The API is versioned in the path — this reference covers v1.

Before you start

Create an account and keep the issued sk_test_ sandbox key from API keys. You need a key, a gate, a public sitekey and a complete target URL. Sandbox calls validate the integration without contacting a real target or consuming credits.

Make your first sandbox request

Set SOLVEGATE_KEY to your sandbox key, then send the Quickstart request in cURL, Node or Python. Prefer a form? Open the Playground to send, retrieve and inspect the same request.

Choose your gate, then use its result

→

Two supported gates. Use turnstile for an embedded widget and waf for a Cloudflare challenge page. The request fields and returned credentials are explained in Supported gates.

Ready to pour through the gate?

// free sandbox keys · no card required to start