> For the complete documentation index, see [llms.txt](https://docs.violetlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.violetlabs.com/apps/b/bill.md).
# BILL
### **Connect BILL in Violet**
1. In [Violet](https://app.violetlabs.com/) (or [VioletGov](https://app.violetgov.com/)), navigate to **Integrations** and click to add a new integration.
2. Select **BILL**
3. Select your BILL instance type from the dropdown (**Sandbox** or **Production**).
4. Enter your **Organization ID**. To find this in BILL:
1. Navigate to [Settings >> Sync & Integrations >> Manage Developer Tokens](https://app02.us.bill.com/neo3/settings/sync-and-integrations/manage-developer-keys)
2. You should see your Organization ID, which will be a unique alphanumeric value that starts with `008`.
5. Enter your BILL username and password, then click **Connect.**
\[Optional] You can also provide a unique name for the connection based on the credentials you're using, and you can create **restricted permissions** to users or groups:
6. Once connected, you can configure which types of data to ingest, how frequently data should be refreshed, etc.
7. Last, click **Create** to begin fetching data. You're done!
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.violetlabs.com/apps/b/bill.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.