> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/bill.md).

# BILL

Look up vendors in a BILL (bill.com) accounts payable organization.

### Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector | Authentication |
| --------- | -------------- |
| BILL      | Credentials    |

#### BILL

Connect to BILL (bill.com) to look up vendors in your accounts payable organization. Requires a BILL developer key plus the username, password, and organization ID of a BILL user with vendor permissions.

**Set up in BILL**

1. Prepare the BILL account or service that the workflow will access. Grant access to the required resources and operations.
2. **Organization ID:** BILL organization to sign in to. Find it in BILL under Settings > Your Company > Profile, or with GET /v3/organizations.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **BILL**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field   | Required                 | What to enter                                                                                                                                                                                       |
| --------------- | ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Username        | Yes                      | Email address used to sign in to BILL. Use a dedicated API user rather than a person's account; if the user has multi-factor authentication enforced, complete MFA setup in BILL before connecting. |
| Password        | Yes                      | Password for the BILL user above.                                                                                                                                                                   |
| Organization ID | Yes                      | BILL organization to sign in to. Find it in BILL under Settings > Your Company > Profile, or with GET /v3/organizations. [Provider instructions](https://developer.bill.com/docs/bill-keys-tokens). |
| Developer Key   | Yes                      | Developer key issued with your BILL developer account. [Provider instructions](https://developer.bill.com/docs/bill-keys-tokens).                                                                   |
| Environment     | Optional / as applicable | 'production' for live BILL data, or 'sandbox' for the BILL developer sandbox. Sandbox credentials are separate and do not work against production.                                                  |

#### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

### Use an action

1. Add the required **BILL** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

### Actions

#### Get Vendor

Get one BILL vendor by ID.

**Inputs**

| Field  | Type            | Required | Description                                                     |
| ------ | --------------- | -------- | --------------------------------------------------------------- |
| Vendor | select (string) | Yes      | The vendor to fetch. Options load from the selected connection. |

**Outputs**

| Field       | Type   | Description             |
| ----------- | ------ | ----------------------- |
| Vendor      | object | The BILL vendor record. |
| Vendor Name | string | The vendor's name.      |

#### List Vendors

List vendors in a BILL organization.

**Inputs**

| Field            | Type            | Required | Description                                                                                                     |
| ---------------- | --------------- | -------- | --------------------------------------------------------------------------------------------------------------- |
| Name Starts With | string          | No       | Only return vendors whose name starts with this text.                                                           |
| Account Type     | select (string) | No       | Only return vendors of this account type. Available values: Business, Person.                                   |
| Vendor Status    | select (string) | No       | Return active vendors or archived ones. Available values: Active, Archived. Default: active.                    |
| Updated After    | datetime        | No       | Only return vendors changed at or after this time.                                                              |
| Sort             | select (string) | No       | Order the results. Available values: Name (A-Z), Name (Z-A), Newest first, Recently updated. Default: name:asc. |
| Maximum Results  | integer         | No       | Maximum vendors to return. Minimum: 1. Maximum: 1000. Default: 25.                                              |
| Page Cursor      | string          | No       | Continue from a previous page.                                                                                  |

**Outputs**

| Field       | Type          | Description                       |
| ----------- | ------------- | --------------------------------- |
| Vendors     | object\_array | The matching BILL vendors.        |
| Next Cursor | string        | Cursor for the next page, if any. |

### Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# 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.stackai.com/integrations/catalog/bill.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.
