Zero-Registration SMS Verification API for Rapid Prototyping
Access Credentials
Generate an API key by completing the daily authentication process within the distribution channel. This lightweight onboarding eliminates formal registration requirements while providing immediate accesss credentials.
API Endpoint
POST https://gateway.temp-sms.io/v1/transmit/{access_key}
Request Specification
Headers:
Content-Type: application/json
Payload Parameters:
| Field | Type | Required | Constraints |
|---|---|---|---|
api_key |
string | Yes | Active access token |
recipient |
string | Yes | Validated mobile number |
verification_pin |
string | Yes | Six-digit numeric code |
validity_window |
integer | Yes | TTL in minutes (minimum 1) |
Sample Requesst:
{
"api_key": "live_8f3j2k9m1n",
"recipient": "13900139000",
"verification_pin": "582947",
"validity_window": 5
}
Response Format
| Property | Type | Description |
|---|---|---|
status_code |
enteger | HTTP-style result indicator (200 for success) |
status_text |
string | Verbal outcome description |
details |
null/object | Supplementary information |
Successful Response:
{
"status_code": 200,
"status_text": "Accepted",
"details": null
}
Integration Example
curl -X POST https://gateway.temp-sms.io/v1/transmit/live_8f3j2k9m1n \
-H "Content-Type: application/json" \
-d '{
"api_key": "live_8f3j2k9m1n",
"recipient": "13900139000",
"verification_pin": "582947",
"validity_window": 5
}'
Operational Constraints
- Usage-based pricing deducted per successful invocation
- Default sender signature applied; branded customization available for prepaid accounts exceeding threshold balances
- Credential confidentiality required to prevent quota exhaustion
- Intended for staging environments and emergency production failover scenarios