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 — a key from one environment will not work in the other.

1

Sign in to the BILL web app

Open the sign-in page for your environment, enter your address under Email, click Continue, and complete your password and any verification prompts.

BILL Sign in page with the Email field and Continue button highlighted

​
Open Manage Developer Keys

The Developer Key and the Organization ID both live on one page in the BILL app.

1

Open Settings

In the left navigation, click Settings.

BILL left navigation with Settings highlighted
2

Open Manage Developer Keys

In the settings navigation, expand Sync & Integrations and click Manage Developer Keys.

  • Direct link: /neo/settings/sync-and-integrations/manage-developer-keys
Expanded Sync and Integrations section showing App Center, Manage Developer Keys and Tokens

​
Generate and copy the Developer Key

The Developer Key identifies your integration to BILL. Generate one if the table on this page is empty.

1

Generate a developer key

On the Manage Developer Keys page, click Generate developer key.

Manage Developer Keys page with the Generate developer key button highlighted
2

Generate the key

Tick I agree to the BILL developer terms of service., then 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 recognisable name.
Generate developer key dialog with the terms of service checkbox and Generate key button highlighted
3

Copy the Developer Key

In the Developer key column, click the eye icon (Show developer key) to reveal the value, then copy it. Paste it into the Developer Key field in StackOne Hub.

  • Keep the key somewhere safe, such as a password manager.
Developer keys table with the masked key value, its reveal control and the Rename button highlighted

​
Copy 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 and paste it into the Organization ID field in StackOne Hub.

  • Format: 008 followed by 17 alphanumeric characters
  • Example: 00801ABCDEFGHIJKLMNO
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

Enter your BILL sign-in credentials

In StackOne Hub, enter the address you sign in with under Email and its password under Password — the same pair you used in the first step. StackOne exchanges them for a session ID and never re-shares them.

  • 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.
  • An API session expires after 35 minutes of inactivity. StackOne signs back in automatically, so no action is needed from you.
  • Need help with developer keys? See the BILL developer documentation.

​
Linking the Account from the Hub

1

Navigate to the Hub

Use one of the three Linking Account Methods to access the Hub.
2

Fill out the fields

Fill out the following fields using details from your provider:
  • Developer Key
  • Email
  • Password
  • Organization ID
3

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

If the account linking is successful, you will see the newly linked account in your Accounts page.