Support
Support is an address, a status page and documentation. There is no ticket portal and we are not going to build one — a queue you cannot see into is worse than a mailbox with an owner.
Support
Answered within one business day. Include the key prefix — never the key itself.
Security
Vulnerability reports. Kept off the support queue so they are not read behind a week of billing questions.
Three things account for nearly every question
Each is answerable from the documentation, and each is linked to the page that answers it.
| What you see | What it usually is | Where it is answered |
|---|---|---|
ERROR_KEY_DOES_NOT_EXIST, or every task rejected |
The key is wrong, revoked, or from another environment. Keys are shown once at issue and never again, so a key copied from a screenshot is often truncated. | Troubleshooting → invalid API key |
PHP: an empty body, or true where you expected HTML |
CURLOPT_RETURNTRANSFER
is off, so cURL wrote the response to output instead of returning it. The SDK cannot detect a challenge in a body it never received.
|
Troubleshooting → RETURNTRANSFER |
| A challenge is detected but the request still fails | The token was solved but could not be injected — the page posts the field under a name the SDK did not expect, or the form is built by script. | Troubleshooting → detected but unhandled |
Before you write
- Check status. It is served by this site, not by the gateway, so it stays up when the gateway does not.
- Check the error reference — every typed SDK error maps to a documented corrective action.
-
Send the key prefix
(
lgbl_live_…), the target domain, and a timestamp. That is enough to find the traffic.
We cannot read your key out of our own database — only a SHA-256 of it is stored — and we will never ask for it. A mail containing one should be treated as a key that needs rotating, which you can do yourself from the keys page with an overlap window so nothing breaks mid-deploy.