Skip to main content

Technical FAQ

Technical questions and answers about Lineserve's messaging platform and APIs.

API Integration​

What programming languages do you support?​

Our REST APIs can be integrated with any programming language that can make HTTP requests. We provide official client libraries for:

  • Node.js
  • Python
  • PHP
  • Java
  • .NET (C#)
  • Ruby
  • Go

For other languages, you can use our REST API directly with your preferred HTTP client.

How do I handle webhooks securely?​

To ensure your webhooks are secure:

  1. Verify the signature included in webhook headers
  2. Only accept HTTPS connections
  3. Implement proper error handling
  4. Use IP whitelisting when possible
tip

Sample code for webhook signature verification is available in our GitHub repository.

What's the maximum message size?​

  • SMS: 160 characters per segment (up to 1600 characters using concatenation)
  • WhatsApp: 4,096 characters
  • Rich Media: Varies by channel (see our API Reference)

How do I handle message delivery receipts?​

Delivery receipts (DLRs) are sent to your webhook endpoint. To process them:

  1. Configure your webhook URL in the dashboard
  2. Implement an endpoint to receive the callbacks
  3. Process the delivery status updates in your application

See our Webhooks documentation for detailed implementation guidelines.

Performance & Reliability​

What's your system uptime?​

Our platform maintains 99.95% uptime, with real-time status updates available at status.lineserve.com.

What are the API rate limits?​

Rate limits vary by plan:

  • Basic: 10 requests/second
  • Professional: 50 requests/second
  • Enterprise: 200+ requests/second (customizable)
caution

Exceeding rate limits results in HTTP 429 responses. Implement exponential backoff in your code to handle these gracefully.

How do I optimize for high-volume messaging?​

For high-volume scenarios:

  1. Use batch APIs to send multiple messages in one request
  2. Implement proper error handling and retry logic
  3. Consider using queues in your architecture
  4. Distribute sending over time for very large campaigns
  5. Contact us for dedicated throughput if sending millions of messages

How do you handle failover and disaster recovery?​

Our infrastructure is deployed across multiple geographic regions with automatic failover. Data is replicated in real-time, and we maintain a Recovery Time Objective (RTO) of less than 4 hours for critical systems.

Troubleshooting​

Why are my messages not being delivered?​

Common reasons include:

  1. Invalid phone numbers (check formatting)
  2. Insufficient credits
  3. Content filtered as spam
  4. Recipient has opted out
  5. Network issues in the destination country

Check the delivery status codes in our API Reference for specific error information.

How do I debug webhook issues?​

To troubleshoot webhook problems:

  1. Check your logs for incoming requests
  2. Verify your server is accessible from the internet
  3. Ensure your endpoint responds with HTTP 200
  4. Use tools like Webhook.site for testing
  5. Check for firewall or security restrictions

What should I do if I receive an API error?​

  1. Check the HTTP status code and error message
  2. Refer to our Error Handling documentation
  3. Ensure your API key has the required permissions
  4. Check your account status and credit balance
  5. If the issue persists, contact support with the request ID
tip

Include the X-Request-ID header from the response when contacting support about API errors.

Development Best Practices​

Should I use a dedicated library or direct API calls?​

We recommend using our official client libraries when available for your language. They provide:

  • Automatic request signing
  • Error handling
  • Retry logic
  • Type safety (in typed languages)

For simple integrations or unsupported languages, direct API calls are perfectly acceptable.