Responses & errors

Check result on every response: OK means it worked, anything else means it didn't and resulttext (or message) says why.

Success

With dataType=json

{
  "success": true,
  "result": "OK",
  "resulttext": "IM sent",
  "action": "im"
}

Failure

HTTP 200

{
  "success": false,
  "result": "FAIL",
  "resulttext": "Unable to locate SL Name",
  "action": "im"
}

A command the bot couldn't carry out still answers HTTP 200 — always check result, not just the status code.

Without dataType=json

URL-encoded

result=OK&resulttext=IM%20sent&action=im

Nested values (arrays, objects) don't survive this format — use dataType=json for any command that returns lists.

Errors before the command runs

HTTP	result	message	Fix
400	ERROR	Missing action / botname / secret parameter	Send all of them.
401	ERROR	Missing API key / Invalid API key	Copy the key from the Developer Hub again.
401	ERROR	Invalid bot credentials	Check the bot name and its Access Code.
400	ERROR	Invalid JSON format in request body	Fix the JSON; from LSL, send form-encoded instead.
500	FAIL	Internal server error	Try again later.

Common failures from the bot

resulttext	Meaning
Bot not connected on this channel	The bot is offline. Log it in first.
Bot is not connected to a channel	The bot has no hosting slot. Contact support.
Failed to complete command, timed out.	The bot didn't answer within 60 seconds.
Request timed out	Second Life didn't answer a lookup in time. Try again.
Bot is at Safe Hub	You sent `nosafehub=1` and the bot is in a Safe Hub.
Unknown apiType: …	The `action` name is misspelled.
Item not found	The inventory item UUID is wrong, or the bot hasn't loaded that folder yet.

OK doesn't always mean done

Some Second Life actions are fire-and-forget — the bot sends them and Second Life never confirms. For those, OK means "sent". Each command's Good to know section says when this applies (for example group invites without the right power, payments, and role changes).