Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.otpedge.com/llms.txt

Use this file to discover all available pages before exploring further.

OTP Edge uses standard HTTP response codes to indicate the success or failure of an API request.

​
HTTP Status Codes

CodeTypeDescription
200SuccessThe request was successful.
400Bad RequestMissing required fields or invalid phone format.
401UnauthorizedMissing or invalid API Key.
402Payment RequiredSubscription is inactive or past due.
403ForbiddenKey found but revoked or lacks permissions.
429Too Many RequestsRate limit exceeded or quota exhausted.
500Server ErrorAn unexpected error occurred on our side.

​
Error Object Structure

When an error occurs, the response body will contain a JSON object describing the problem. 
{
  "error": "Short description of the error",
  "code": "ERROR_CODE_STRING",
  "details": "Optional extended debugging information"
}

​
Common Error Codes

CodeDescription
INVALID_PHONE_NUMBERThe phone_number provided is not a valid E.164 string.
QUOTA_EXCEEDEDYou have reached your monthly limit for the current tier.
SPAM_COOLDOWNYou are sending too many messages to the same number too quickly.
MISSING_TEMPLATEThe template_name provided does not exist in your account.