> For the complete documentation index, see [llms.txt](https://docs.bugbug.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugbug.io/public-api-reference/config.md).

# Config

Config

## IP addresses list

> Returns List of Bugbug infrastructure IP addresses.

```json
{"openapi":"3.1.0","info":{"title":"BugBug.io Public API","version":"v2"},"tags":[{"name":"Config","description":"Config"}],"security":[{"Bearer":[]},{}],"components":{"securitySchemes":{},"schemas":{"IPAddressList":{"type":"object","properties":{"ips":{"type":"array","items":{"type":"string"}}},"required":["ips"]}}},"paths":{"/api/v2/config/ips/":{"get":{"operationId":"v2_config_ips_retrieve","description":"Returns List of Bugbug infrastructure IP addresses.","summary":"IP addresses list","tags":["Config"],"responses":{"200":{"content":{"application/json":{"schema":{"$ref":"#/components/schemas/IPAddressList"}}},"description":""},"401":{"description":"Authentication credentials were missing or invalid."}}}}}}
```

## API status probe

> Lightweight liveness probe. Always returns 200 when the API is reachable. If an \`Authorization: Token \<key>\` header is sent it is validated and the result is reported via the \`authenticated\` flag, but neither a missing nor an invalid token causes a 401. Intended for client-side connection indicators and uptime monitors.

```json
{"openapi":"3.1.0","info":{"title":"BugBug.io Public API","version":"v2"},"tags":[{"name":"Config","description":"Config"}],"security":[{"Bearer":[]},{}],"components":{"securitySchemes":{},"schemas":{"ApiStatus":{"type":"object","properties":{"status":{"type":"string"},"authenticated":{"type":"boolean"}},"required":["authenticated","status"]}}},"paths":{"/api/v2/config/status/":{"get":{"operationId":"v2_config_status_retrieve","description":"Lightweight liveness probe. Always returns 200 when the API is reachable. If an `Authorization: Token <key>` header is sent it is validated and the result is reported via the `authenticated` flag, but neither a missing nor an invalid token causes a 401. Intended for client-side connection indicators and uptime monitors.","summary":"API status probe","tags":["Config"],"responses":{"200":{"content":{"application/json":{"schema":{"$ref":"#/components/schemas/ApiStatus"}}},"description":""},"401":{"description":"Authentication credentials were missing or invalid."}}}}}}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bugbug.io/public-api-reference/config.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.