Support

Get help

Before contacting support, check the basics:

• Authentication failing? Read Authentication and confirm you’re using the right environment’s credentials at the right base URL. The most common issue: sandbox key (sk_test_*) against production base URL (or vice versa).
• Validation errors? A 400 with error_code: "1110" includes a details array — each entry tells you which field failed and why.
• Rate-limited? A 429 with error_code: "1301" honours Retry-After. See Rate limits.
• Webhook missing? Check the webhook_url is set on the API key, the URL is HTTPS, and your endpoint returns 2xx within 5 seconds. See Webhooks overview.
• SMS not delivered? Check GET /status/{message_id} — if it reports failed, the recipients[] array has per-number error codes from the carrier.

Quoting a request_id

Every error envelope includes a request_id. Quote it when contacting support — the team can pull the audit record with it.

{
  "success": false,
  "error_code": "1401",
  "message": "Internal server error",
  "request_id": "req_8f3a4c2e9b1d7a6f",
  ...
}

Reporting a bug

Include:

• The full request (URL, method, headers — redact app-key).
• The full response (status, headers, body).
• The request_id from the envelope.
• A timestamp in UTC.
• Which environment (sandbox or production).
• The relevant message_id if applicable.

Feature requests

Open an issue with your Bloonio account manager. Lisoloo doesn’t have a public issue tracker; feature requests are tracked internally and prioritised against the broader Bloonio platform roadmap.

When the corresponding GitHub repo is made public, it will be linked here.

Contact

• Email: support@bloonio.com
• Dashboard: app.bloonio.com/support
• Status page: status.bloonio.com (when available)

Useful links

API reference Every endpoint with examples and schemas.

Error catalogue Every error_code with remediation.

Quickstart The fastest end-to-end path — cURL, Python, JavaScript, or PHP.

Webhooks overview Delivery semantics and the current signing caveat.