stopMessageLiveLocation — Botlify Cloud Docs

Use this method to stop updating a live location message before live_period expires. On success, if the message is not an inline message, the edited Message is returned, otherwise True is returned.

Parameters

Parameter	Type	Required	Description
`business_connection_id`	String	Optional	Unique identifier of the business connection on behalf of which the message to be edited was sent
`chat_id`	Integer or String	Optional	Required if inline_message_id is not specified. Unique identifier for the target chat or username of the target bot, supergroup or channel in the format `@username`.
`message_id`	Integer	Optional	Required if inline_message_id is not specified. Identifier of the message with live location to stop.
`inline_message_id`	String	Optional	Required if chat_id and message_id are not specified. Identifier of the inline message.
`reply_markup`	InlineKeyboardMarkup	Optional	A JSON-serialized object for a new inline keyboard

Example

PHP — Call stopMessageLiveLocation (no parameters)

<?php
// ── Botlify Cloud .env — auto-injected, never hardcode secrets ──
$BOT_TOKEN     = getenv('BOT_TOKEN');     // Telegram bot token from @BotFather
$ADMIN_CHAT_ID = getenv('ADMIN_CHAT_ID'); // Your numeric admin Telegram user ID
$BOT_USERNAME  = getenv('BOT_USERNAME');  // Bot username without @

$resp = bot('stopMessageLiveLocation');

if ($resp['ok'] ?? false) {
    $result = $resp['result']; // handle the response
}

Botlify Cloud Runtime
Credentials are auto-injected in .env — always load them with getenv(): BOT_TOKEN, ADMIN_CHAT_ID, BOT_USERNAME. Main database: database.db (SQLite, WAL mode). Runtime errors: error.log. Quick test: send to $ADMIN_CHAT_ID. Full details: Runtime Reference.