PHLO APIs use HTTP verbs and standard HTTP status codes to make it easier for you to integrate communications into your code. To secure your requests to our servers, we serve our API over HTTPS. You may also want to learn about our client SDKs: iOS SDK, Android SDK, and Browser SDK.Documentation Index
Fetch the complete documentation index at: https://plivo.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
API Endpoint
v1.
Authentication
All requests to PHLO API are authenticated withBasicAuth using your AUTH ID and AUTH TOKEN. Find your credentials on the Plivo console.
cURL
HTTP Status Codes
| Code | Description |
|---|---|
200 | Request executed successfully |
201 | Resource created |
400 | Parameter missing or invalid |
401 | Authentication failed |
403 | Forbidden |
404 | Resource not found |
429 | Too many requests (rate limited) |
500 | Server error |
Troubleshooting Common Errors
| Code | Common Causes | Solution |
|---|---|---|
400 | Missing required parameter, invalid payload format | Check all required parameters in request body |
401 | Invalid Auth ID or Auth Token | Verify credentials at Console → API Keys |
403 | PHLO not enabled, account not verified | Complete account verification. Contact support |
404 | Invalid PHLO ID, PHLO not deployed | Verify PHLO ID. Ensure PHLO is deployed and active |
429 | Rate limit exceeded | Implement exponential backoff |
500 | Temporary server issue | Retry after a few seconds. Check status.plivo.com |