# Documentation Page **Page:** kit/agent/bot-urls/status [Download Raw Markdown](./kit/agent/bot-urls/status.md) --- # Bot URL status, access log and lifecycle This page is for the owner of a Bot URL. It covers the status a URL shows, the access log of calls, and what happens to the URL when its computer or Bot changes. It is part of [Bot URLs](/kit/agent/bot-urls/). The Hub shows each URL's status with a reason on the Bot's **Link and keys** tab. The API returns them as `status` and `status_reason`; the Hub's **Off** is `disabled` in the API. | Status | What callers get | Why | |---|---|---| | **Active** | Answers if the Bot is available. | The URL is on and attached to a computer, with no freeze, suspension or Bot URL switch blocking it. Active does not confirm that the Bot exists or is running. | | **Off** (`disabled`) | `bot_disabled` | See the reason: you turned it off, a suspension applies, or Bot URLs are switched off for now. | | **Detached** | `bot_disabled` for a caller with a valid key, then `bot_not_found` | The computer was deleted, or the server it was on ended or is no longer yours. The label and keys are kept. | | **Frozen** | `bot_disabled` | Hoody froze the URL. The reason is shown. | ## Why is my URL off? | `status_reason` | Meaning | What you can do | |---|---|---| | `owner_disabled` | You turned the URL off, or pressed panic. | Turn it on: **Turn link on** in the **Addresses** menu of the Bot's **Link and keys** tab, or `PATCH /api/v1/bot-urls/{id}` with `{"enabled": true}`. With session authentication, when your account requires 2FA for API keys, send an unused current or backup code as `otp_code`. Password-form HTTP Basic uses the code supplied at authentication. API-token authentication needs no additional code. After panic, also create new keys. | | `suspended` | A suspension on your account, the computer or its server applies. | When the suspension is lifted, the status is worked out again: the URL answers if nothing else, such as your own switch, keeps it off. | | `host_off`, `global_off` | Bot URLs are switched off on the computer's server, or everywhere, for now. | Nothing. When the switch is back on, the URL answers if nothing else keeps it off. | | any other text | The reason Hoody gave when freezing the URL. | Contact Hoody support. You cannot turn a frozen URL on or re-point it. | When several apply, the Hub shows the strongest: Frozen, then Detached, then a suspension, then your own switch, then a server-wide switch. Callers see none of these reasons; what each caller gets is on the [lookup page](/kit/agent/bot-urls/status/reference/#what-callers-see). ## Read the access log Calls that reach the URL's computer write a line to the computer's existing proxy logs, refused calls included. A line holds metadata only. The log never holds what was said, the key itself, its prefix, headers or the caller's software. To read what a caller asked, open the Bot's conversation in the agent. The log is best effort: some refusals leave no line, and a line can occasionally be lost on its way. Use it to follow who calls and how it goes, not as a complete record. The [lookup page](/kit/agent/bot-urls/status/reference/#access-log-lines) lists the fields, the gaps and the retention. Open the Bot's menu and choose **Logs**. The Logs page opens on the **Bots** source: the calls of every Bot URL on that computer, newest first. The Hub reads the log straight from the computer in your browser; it never passes through the Hoody API. ```bash # Bot calls of this computer, newest first curl "https://$PROJECT_ID-$COMPUTER_ID-logs-1.$SERVER.computers.hoody.com/_logs?serviceName=bots" # One call, by the request id a caller quoted curl "https://$PROJECT_ID-$COMPUTER_ID-logs-1.$SERVER.computers.hoody.com/_logs?serviceName=bots&traceId=3f9a0c1b7e2d4a5f8b6c9d0e1f2a3b4c" ``` If a password group protects the computer's logs, send its username and password with HTTP Basic auth. Query rules are on the [lookup page](/kit/agent/bot-urls/status/reference/#log-queries). See [Proxy Logs](/api/proxy-logs/) for the other filters and the live stream. ## Move a URL to another computer Re-pointing keeps the label, the address and every key. Callers change nothing. Use it after copying a computer, or to give a detached URL a new home. On the Bot's **Link and keys** tab, open the **Addresses** menu and choose **Re-point…**. Pick the computer, then choose **Re-point**. The Hub keeps the Bot's unique id: pick a computer that runs this same Bot, such as a copy. ```bash curl -X POST "https://api.hoody.com/api/v1/bot-urls/$BOT_URL_ID/repoint" \ -H "Authorization: Bearer $HOODY_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "computer_id": "'"$NEW_COMPUTER_ID"'", "bot": { "realm": "global", "id": "chief", "uid": "'"$BOT_UID"'" } }' ``` You must own the destination computer's project too. When moving from another server or reattaching a detached URL, the destination server must have room for another URL (`SERVER_BOT_URL_LIMIT`). Moving an attached URL between computers on the same server keeps its existing slot. With session authentication, when your account requires 2FA for API keys, send an unused current or backup code as `otp_code`. Password-form HTTP Basic uses the code supplied at authentication. API-token authentication needs no additional code. The old computer stops answering before the new one starts. While the switch is in progress, callers may get `bot_unavailable` for a moment, which they retry. `bot.uid` is the Bot's unique id; [Create a Bot URL](/kit/agent/bot-urls/create/) shows where to read it. A detached URL shows on no Bot in the Hub, so the Hub cannot re-point or delete it. Find it with `hoody boturls list`, then use the cURL tab, `hoody boturls repoint` or `hoody boturls delete`. If the former server is down, the move can remain blocked indefinitely. `propagation.state` can be `pending` or `failed`; `failed` does not mean the move was cancelled. If the former server will not return, contact Hoody support. [Moves that wait](/kit/agent/bot-urls/status/reference/#moves-that-wait) has the details. A Bot URL is tied to one Bot by its unique id, not by its name. Deleting a Bot in the Hub also deletes its URL and keys. If you delete the Bot through the agent API while keeping its URL, recreating the same name gives the Bot a new unique id: callers get `bot_disabled` until you re-point the URL to the new Bot. ## Delete a URL On the Bot's **Link and keys** tab, choose **Limits and websites**. Under **Delete the link**, choose **Delete link** and confirm. ```bash curl -X DELETE "https://api.hoody.com/api/v1/bot-urls/$BOT_URL_ID" \ -H "Authorization: Bearer $HOODY_TOKEN" ``` Deleting a URL removes its keys and its address. The label is never given out again, to anyone, you included. Work the Bot was doing for callers keeps going in the agent; the Bot and its conversation are not touched. To pause instead, turn the URL off: everything is kept. ## Advanced - **Read the status from the API.** `GET /api/v1/bot-urls/{id}` (`hoody boturls get`) returns `status`, `status_reason` and the `propagation` of the last change. After any change except a delete, poll it until `propagation.state` is `applied`. A delete's reply carries the removal's `propagation`; a later read answers 404 `BOT_URL_NOT_FOUND`, which does not mean the removal is applied. See [Bot URLs](/api/bot-urls/) in the API reference. - **Calls of one URL only.** When a computer serves several Bot URLs, add `botUrl=` with the URL's `bu_…` id to a `serviceName=bots` query. See [Proxy Logs](/api/proxy-logs/). ## Reference The [Bot URL status reference](/kit/agent/bot-urls/status/reference/) has what callers see, the log's fields, gaps and query rules, and the [lifecycle table](/kit/agent/bot-urls/status/reference/#lifecycle): what each event, such as panic or a freeze, does to the URL and its callers. ## What's Next - [Create a URL and keys](/kit/agent/bot-urls/create/): keys, limits and the panic button. - [Errors and limits](/kit/agent/bot-urls/errors/): every code in the access log. - [Security](/kit/agent/bot-urls/security/): what to watch in the log.