Skip to content

Introduction

clearance.rest puts three things that normally need three vendors behind one API and one API key:

Service What it does Base URL
Numbers Rent or attach phone numbers and wait for the SMS they receive. https://api.clearance.rest/numbers
Emails Wait for an inbound email and pull a code out of it. https://api.clearance.rest/emails
Captchas Solve a captcha and get the token back in the same request. https://api.clearance.rest/captchas

Every “wait” endpoint is synchronous. You send one request; it stays open until the thing you are waiting for arrives (an SMS, an email, a solved captcha) or your timeout runs out. There is no polling loop and no webhook to host.

curl -G "https://api.clearance.rest/numbers/sms/wait" \
-H "X-API-Key: $CLEARANCE_REST_API_KEY" \
-H "X-Service-Timeout: 60000" \
--data-urlencode "number=+14155550100" \
--data-urlencode "code_regex=\d{6}"

When the SMS arrives the response carries the extracted code.

Everything you do is scoped to a project. A project has its own API key, its own numbers and connected mailboxes, and its own usage statistics. You manage projects and read their API keys in the console.