Skip to main content
Creating payments and creating an organization funding account (bank account) require an MFA-trusted API session. This connection cannot establish one, because BILL creates MFA trust only when an MFA ID is supplied at sign-in and this connection does not collect one — enabling MFA in the BILL web app does not change that. Everything else is unaffected, including adding and removing vendor payout bank accounts, which have been verified to work without MFA trust. MFA is enforced in production only.

​
Sign in to BILL

BILL runs production and sandbox on completely separate hosts, each with its own credentials. Sign in to the environment you are connecting, and generate the developer key there.

1

Sign in to the BILL web app

Open the sign-in page for your environment.

BILL sign-in page

​
Generate and copy the Developer Key

The Developer Key identifies your integration to BILL.

1

Generate the key

In the left navigation, open Settings > Sync & Integrations > Manage Developer Keys. If the table already lists a key, skip this step and copy that one.

  • Click Generate developer key.
  • Tick I agree to the BILL developer terms of service.
  • Click Generate key.
  • It takes up to a minute for BILL to generate the key. Click Reload page after a few moments to see it.
  • The new key appears in the table as Placeholder Name with Status Ready. Click Rename to give it a recognizable name.
Generate developer key dialog with the terms of service checkbox and Generate key button highlighted
2

Copy the Developer Key

The key is masked in the Developer key column.

  • Click the eye icon (Show developer key).
  • Copy the Developer Key across.
Developer keys table with the masked key value, its reveal control and the Rename button highlighted

​
Retrieve the Organization ID

The Organization ID tells BILL which organization to sign in to. It is on the same page — no need to go anywhere else.

1

Copy the Organization ID

Scroll to the bottom of the Manage Developer Keys page. The value after Organization ID: is your organization identifier. Copy it across.

  • Format: 008 followed by 17 alphanumeric characters
Bottom of the Manage Developer Keys page with the Organization ID line highlighted

​
Enter your Email and Password

The last two values are simply your BILL sign-in credentials.

1

Find your BILL sign-in credentials

The Email is the address you sign in with, and the Password is its password. Use the same pair you signed in to BILL with.

  • Actions run with the permissions of this BILL user, so make sure it can see the bills, vendors, invoices, and customers you want to sync.
  • Need help with developer keys? See the BILL developer documentation.
1

Connect

  • Click Connect.
  • If applicable, the provider will redirect you to a sign-in or authorization page. Complete the provider’s authorization flow.
  • Once authorization is successful, you will see a confirmation popup.
2

Use Actions

Connect an AI platform to the linked account’s actions. See AI Platforms.Other ways to call actions are listed in Protocols & SDKs.