Organization | Basic operations

Name: Organization | Basic operations API
Brand: Organization | Basic operations
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceAccountingapiKey25 EndpointsREST

For Agents

Provision users, manage profiles and permissions, read bank balances and money-movement records, and fetch documents inside a BILL organisation.

Connect the Organization | Basic operations to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Organization | Basic operations, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Organization | Basic operations API.

Provision and update user accounts with profile and permission assignments

Read organisation, profile, and permission records to audit who can do what

Fetch document pages and document metadata attached to BILL transactions

Send and list internal messages tied to organisation activity

GET STARTED

Start building with Organization | Basic operations API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Organization | Basic operations, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Organization | Basic operations, keeping it validated and agent-ready. This BILL surface manages the foundational records of an organisation: the organisation itself, its users and profiles, attached documents, internal messages, bank accounts, money-movement records, and card accounts. Agents use it to provision users, read profiles and permissions, fetch documents attached to transactions, and inspect bank balances and money-movement history. It is the administrative spine that supports every AP and AR workflow.

Use Cases

Patterns agents use Organization | Basic operations API for, with concrete tasks.

★ User provisioning and offboarding

Add new finance team members to a BILL organisation, assign their profile, and soft-delete leavers. The API exposes Crud/Create/User and Crud/Update/User for individual changes, plus Bulk/Crud variants for batch onboarding. Crud/Delete/User and Crud/Undelete/User keep the audit trail intact while removing day-to-day access.

Create a new User with email finance.new@example.com assigned to the AP Approver profile, then verify by calling Crud/Read/User

Permission audit

Pull the full permission matrix to confirm who can approve bills, send invoices, or move money. List/Profile and GetProfilePermissions return profile definitions and their associated permissions, while List/User maps users to profiles. A compliance agent can run a quarterly access review without exporting CSVs from the BILL UI.

Call List/Profile, then GetProfilePermissions for each profile, and return a list of users by profile from List/User

Bank balance and money-movement reporting

Read connected bank balances and the money-movement ledger to feed cash-flow dashboards. GetBankBalance returns the current balance for a configured BankAccount, and List/MoneyMovement enumerates payments in flight. Agents use this to answer 'how much cash do we have to disburse this week?' without opening BILL.

Call GetBankBalance for each configured BankAccount and return the aggregate balance, then call List/MoneyMovement for the last 7 days

Document retrieval for AP review

Fetch invoice scans and supporting documents attached to BILL transactions. GetDocuments returns metadata for documents tied to a record, and GetDocumentPages returns the page-level images. An AP review agent can pull a vendor invoice scan into a verification pipeline before approving payment.

Call GetDocuments for a target Bill ID and then GetDocumentPages to retrieve the first page image of the linked invoice

Agent-driven org administration via Jentic

An AI agent uses Jentic to discover organisation operations from intents like 'add a user to BILL' or 'check our bank balance'. Jentic returns the matching operation, loads its schema, and executes with credentials from the vault. The agent can administer a BILL organisation without ever holding raw session tokens.

Search Jentic for 'add a user in bill.com', load the Crud/Create/User schema, and execute it for a new finance hire

Key Endpoints

25 endpoints — jentic publishes the only available openapi specification for organization | basic operations, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/Crud/Read/Organization.json

Read the organisation record

POST

/Crud/Create/User.json

Create a user account

POST

/Bulk/Crud/Create/User.json

Bulk create user accounts

POST

/List/Profile.json

List permission profiles

POST

/GetProfilePermissions.json

Get permissions on a profile

POST

/GetBankBalance.json

Get the current bank balance

POST

/List/MoneyMovement.json

List money-movement records

POST

/GetDocuments.json

Fetch documents attached to a record

POST

/Crud/Read/Organization.json

Read the organisation record

POST

/Crud/Create/User.json

Create a user account

POST

/Bulk/Crud/Create/User.json

Bulk create user accounts

POST

/List/Profile.json

List permission profiles

POST

/GetProfilePermissions.json

Get permissions on a profile

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

BILL session tokens have broad organisation-level rights, so they are higher-risk than typical API keys. Jentic keeps them encrypted in the vault and only releases a scoped reference at execution time, so a leaked agent context cannot escalate to user creation or money-movement reads.

Intent-based discovery

Agents search intents like 'add a user to bill.com' or 'check our bill.com bank balance' and Jentic returns the matching organisation operation with its input schema, so the agent does not need to read BILL's developer portal.

Time to first call

Direct BILL integration: 2-3 days to wire up user provisioning, document fetch, and bank-balance reads. Through Jentic: under 30 minutes.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

BILL Organization Accounts Tracking

Tracking dimensions live alongside organisation administration.

Use accounts-tracking when the task is GL or department setup; use basic-operations for users, documents, and bank balance.

Complementary

BILL AP Vendor Transactions

Vendor transactions consume bank balances and documents managed here.

Use vendor-transactions to pay bills after confirming bank balance via GetBankBalance and reading invoice documents via GetDocuments.

Alternative

Xero Accounting

Xero exposes a similar user, organisation, and bank-feed surface at the ledger level.

Choose Xero when the system of record is the accounting ledger; choose BILL basic-operations when administering the BILL workspace itself.

FAQs

Specific to using Organization | Basic operations API through Jentic.

Why is there no official OpenAPI spec for Organization | Basic operations?

BILL does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Organization | Basic operations via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Organization Basic Operations API use?

BILL uses an API key plus session token model. Agents log in once to obtain a session token and pass it on each call alongside the developer key. Jentic stores both encrypted in the vault and the agent only ever holds a scoped reference.

Can I provision new users with this API?

Yes. Call POST /Crud/Create/User.json to add an individual user, or POST /Bulk/Crud/Create/User.json for batch onboarding. Assign permissions by referencing a profile ID returned from POST /List/Profile.json.

How do I check our bank balance through Jentic?

Search Jentic for 'check bill.com bank balance'. Jentic returns the GetBankBalance operation, loads its schema, and your agent calls POST /GetBankBalance.json with the target BankAccount ID. Pair with POST /List/BankAccount.json to enumerate accounts first.

What rate limits apply to this API?

BILL applies per-organisation throttling. Specific quotas are not exposed in the spec, so prefer POST /Bulk/Crud/Create/User.json over looped single-create calls when onboarding multiple users.

Is the Organization Basic Operations API free?

API access is bundled with paid BILL plans rather than a separate free tier. You need an active BILL organisation and a developer key. Jentic does not add usage charges on top.